257 Matching Annotations
  1. Dec 2021
    1. If you made embed-able forums for web pages and sites, you could inadvertently boost signups, and boost plugin downloads. It'd be awesome to have a third party host for user profiles linkable to my site and forum. Even if you linked facebook or something, for fast signup, server data, etc...

    1. Once we introduce evaluation into our learning spaces, we change the way we interact with student work.

      Evaluation is not the same as feedback. Evaluation is almost always directed at unsolicited advice. Feedback may praise or criticize, but usually seeks value in something.

  2. Nov 2021
    1. In addition to the daily limits, there are follow ratios that go into effect once you’re following a certain number of accounts:Every Twitter account can follow up to 5,000 accounts. Once you reach that number, you may need to wait until your account has more followers before you can follow additional accounts. This number is different for each account and is automatically calculated based on your unique ratio of followers to following.

      Hello. I am a paying subscriber, now, after all these years… I may or may not have become a paying subscriber just to justify this particular feedback after all this time.

      Ultimately, though, I’m giving you a real substantial bullet point to put on that very wispy-looking full features list of Twitter Blue!

    1. Twitter Blue Publisher network

      Hey Twitter,

      I love that you chose to show support for Lists by sharing the list of Blue publishers, this way. This is a decision I want to celebrate!

      However, this hyperlink isn’t particularly useful in that the user has no ability to actually follow the list. Aside from manually bookmarking it on a browser (since you can’t if you let the deeplink open the native app,) there is no way to save it!

    1. This is actively being worked on - for those interested you can follow the progress in https://github.com/snapcore/snapd/pull/10836
    2. After 5 years there's still no fix. This is so annoying. I'm now getting rid of all snap packages and installing deb variants instead. Finally I'll purge snap and if these weird decisions keep on going I'll also move to another distro. Common Canonical. Seriously?
    1. During the time between becoming a DisCONaut and full (legal) membership, it's assumed that the DisCONaut is there for the long run. The new DisCOnaut has become part of an established collective with its unique group culture and, while new members will change that culture, all changes have to fit in well with what has already been built. If no major or unsolved issues arise, the nine-month mark means that the new DisCONaut becomes a full member and the appropriate legal and/or contractual procedures are undertaken.

      I feel like this paragraph addresses my earlier concern about not being able to be paid during that period! Maybe surface this way earlier. I'd say, always lead with the care! It's what brought me in at least :)

    2. marriage

      I do wince a bit at this "marriage" metaphor, I guess also because it immediately brings monogamy to top of mind for me, but I do like the idea of positioning this (this love and commitment to the other people in the coop) in opposition to the super icky "baby" startup metaphor.

    3. In DisCO.coop we recommend that full membership is only awarded after nine continued months of working and being in the collective. This means nine months from the moment the new DisCONaut started dating, independent of their timeline options.

      I understand and agree with the sentiment of putting in the time to grow relationships to the point where everyone feels comfortable. I also think that it is important when we talk about growing communities to move "at the speed of trust."

      But at the same time, I do worry about the feasibility of a 9 month mostly unpaid work period for much of the world's work force. Being able to work for 9 months without getting compensated isn't a luxury most can take (and thats in addition to having likely been a contributor for an amount of time), and will require many to either work a second job while doing this or come from a background that gives them enough of a financial cushion to ride on during this period.

      I guess my suggestion would be that we should think about how this dating process can happen simultaneously to the earlier contributor stages so that certain lessons or learnings can be gleaned without extending the process out too long.

    4. Into the Dating Phase! click to enlarge and animate

      Formatting is kind of weird here and some text appears next to the image.

    5. The Commitment Statement

      Vibe with this idea, but wondering if it could be taken a step further to make it like a recommitment process. Like, resigning the document comes after some calls with other members where we talk through things and adjust the document to fit how needs/commitment has changed, rather than default to renewing the already established statement. Just a thought.

    6. It is also important to have a second, more thorough interview prior to signing the Commitment Statement.

      There are a few places in this document where I can't quite tell if the text is bolded or if I'm just seeing things. Something to keep in mind! We should probably test if DisCO sites in general meet web accessibility standards.

    7. need

      feels a little harsh, not particularly consent drive, maybe "are asked"

    8. Clarity that vibe trumps all other considerations, meaning, if there's a bad fit evident from things like poor or indirect communication, or evident discomfort with the style and rhythms of the existing group, that usually signals a weird vibe. Weird vibe = no DisCO Dating [39].

      I don't think this needs to be elucidated in this doc, but I think it might be a good idea to create a "dating pool" where folks that are interested in working with a DisCO are added and shared (as they're comfortable) with the DisCO community at large. One person may not vibe with a specific DisCO or meet the conditions needed at that time, but may be a great fit for another DisCO.

    9. co-dependent

      I feel like codependency has a bad rap and may raise some eyebrows. Interdependent?

    10. A DisCO Ley Line is, basically, an agreed-on transfer of invested credits between one DisCO and another.

      This concept is brought up many times before here, but this is the first time we have it explained direct and succinctly. I would move this up higher in the doc.

      Also important to note here, if this is a wiki that is hosted on multiple pages, you're probably going to want to repeat certain phrases/sentences so that people reading individual pages can get the gist without having to hunt through.

      Finally, the "basically" here feels a little casual in a way that I think makes the tone inconsistent.

    11. unlike value tracking for contributors, it's not expected to be either latent or unfulfilled.

      I think this sentence helps convince people that are interested in DisCOlarships, but may disuade people interested in contributing. the "expectation" for the credits to be unfulfilled. Question that pops to mind, why track my hours if there is an expectation that nothing will ever come of it?

    12. Similarly, this work is initially considered to be Invested Lovework. You can read more about those terms in this section. For now "invested" means "unpaid" and "Lovework" means "voluntary work".

      This particular phrasing makes this paragraph sound like doublespeak.

    13. Whether it's a DisCO worker-coop, DisCO.NP or any other type of DisCO application, DisCOlarships are announced by the hosting DisCO through its social media channels, newsletters or community calls. Before entering into DisCOlarship, the hosting DisCO needs to ensure it has the human and conceptual capacity.

      One of the places where it feels like we need to explicitly address audience: is this a tool for other DisCOs to learn how to define their relationships, or for people interested in working within the existing DisCO ecosystem. If the former, this feels too prescriptive.

    14. DisCOlarships are one way to advanced from a Casual to Committed DisCO relation. As such, they are considered a Casual Relationship leaning towards committed relationships with DisCOs in general (if not to the particular DisCO hosting the DisCOlarship).

      Idk what it is, but I get a weird feeling about how explicit the lines are being drawn around casual and committed relationships. I think it's related to the earlier comment about feeling like the text is overemphasizing the DisCOs agency in defining the relationship.

      I think part of it is also the fact that the casualization of labor is a really sore point for a lot of workers right now, as we emerge as a new "precariat" class. While its understandable that a lot of this work may be considered volunteer work and thus unpaid, continually noting that this is a casual relationship with no obligation for pay definitely makes me recall toxic work relationships in my past and I imagine will do the same for other workers.

    15. A DisCOlarship involves regular "visits" to a DisCO to learn its practices and get to know DisCONauts in the real world.

      How necessary is this "in the real world" part of the training? If it feels like an absolute must, it could be helpful to elucidate why.

    16. In other DisCOs, contributors can help with whatever productive work is taken by the particular DisCO. So, for example, in a worker-owned DisCO community garden, contributors could drop in to help with the gardening when convenient and that value will be tracked for future inclusion, should they want to become dating members and, eventually, committed. In a DisCO.NP dedicated to creating mesh networks for community WiFi, the contributors can help set up the infrastructure for their own Internet connections and, having learned in the process, can apply that knowledge (and attendant credits) toward future work in that particular DisCO.NP.

      In this section, we have three examples of potential "contributor relationships." While I think exploring different possibilities is important, this is quite a lengthy document and I think we need prioritize word efficiency.

      This isn't to say "don't include these examples," it's to say: if we're including all these examples, we should make it immediately clear to the reader why that example is being given and why that use case is so different from the others provided that it deserves to be included

    17. Why do we track the value of casual contributions?

      I definitely agree in the reasoning behind tracking casual contributions, but when you get to the part about DisCO Ley Lines, I think and underlying problem becomes way more salient:

      value tracking, especially in the case of tracking for the purposes of some sort of recognition by a large third party is a sure fire way of "abstracting" an individuals labor. How do we address this feeling of "heaven is high, emperor is far away" when talking about value tracking, especially in relation to DisCOs unrelated to the DisCO Mothership? That line in particular makes this document less transferrable as a tool for teaching people interested in starting their own DisCOs because it is specifically addressing people's labor in relation to the Mothership.

      TL;DR maybe remove the Ley Lines bullet

    18. (these terms are further explained in this section: Ways to Account for Work).

      I think it's important to provide at least a quick summation of what people will find in that section here so that people don't feel obligated to hunt and peck at sections to understand what you mean.

    19. it is much easier to record contributions according to grade and measure. If you're not familiar with those terms, it basically means "quantity and quality".

      why not just say "quantity and quality" here?

    20. The DisCO.NP may contract services when lacking the capacity - See Undercapacity and contracting outside the DisCO.NP. The DisCO.NP may also choose to engange with other DisCOs in work relationships and value transactions - see DisCOverses and Intra-DisCO Value Flows.

      On this read, I'm putting myself in the shoes of someone that is interested in working as a contributor. These sentences feel way more relevant to the DisCO itself. Not to say this doesn't belong in this page, but I think we may need to work on shaping the tone of this document to more clearly delineate who. the audience is at each point of the text.

    21. Contributors must know that they don't have priority over Committed or Dating members of the DisCO.NP, and that they won't be compensated (whether immediately or ever) for any of their contributions.

      This paragraph paired with the above paragraphs about DisCO.NPs not having any obligation to use the contributions of the contributors feels like we may be going a little too hard in emphasizing the casualness of the relationship, and the current framing makes it feel like the DisCO has way more say in the relationship than the contributor. Frankly, these paragraphs read a little bit like a contract saying "the DisCO is under no obligation to x, y, or z" which I don't think is the tone that you want to strike. Obviously, we don't want to mislead people into thinking "ah, I'm interested in working with this org, so I'm entitled to x, y, and z" but I think a balance can be struck that shows people that they indeed have agency within this relationship, but that the DisCO also reserves the same amount of agency. I think the "Applying the dating metaphor..." paragraph does this really well, so maybe it's about taking these "precautionary" sections and bundling them down lower in the page and working hard to strike a caring town within that section.

    22. they are value tracked.

      I think this needs more elaboration.

    23. The DisCO.NP, however, is not in any way obliged to accept the contribution. Using two of the examples above, if the contributed artwork or code isn't up to standard, the DisCO.NP will not use it. Quality Control and Post-Hoc evaluation is very important in DisCO — if we are to provide viable alternatives to the mainstream economy, we need to ensure we do stuff right, according to the individual criteria of each DisCO LAB.[24] Applying the dating metaphor, if "we’re really not made for each other", we'll move on with no hard feelings. Casual relationships are consent-based and depend on clear communication. A casual contributor doesn't really have to do anything for the DisCO.NP, in terms of building our support structure and using the DisCO's workflow tools, for instance. Contributors can get in touch whenever they feel like it and vice versa. The bulk of the care work for the collective, including all admin and project management tasks, is undertaken by the DisCONauts.

      I would move this final paragraph to be the second paragraph as it feels more directly related to the first, where as the other two feel like they touch on a very specific facet of the contributor-NP relationship.

    24. This one possible DisCO Journey. In others people may remain in one circle, or go through a DisCOlarship and start their own separate DisCO, etc.

      I think that the fact that there is no "one true way" for this process to go makes it hard to visualize this with a single graphic and including this, may give people the wrong impression if they're just scrolling through. At the same time, visualizing infinite paths will definitely confuse people.

      Maybe something less representational/more abstract rather than "informative."

    25. To recap: We have distinguished two main states: Casual and Committed. "Casual" means little responsibility. These are no-strings-attached relationships for mutual benefit. There are two types of Casual Relationship: Supporters (Very casual interactions) and Contributors (More active interactions and actual contributions to the DisCO.NP and its mission). "Committed" signifies a stated commitment of responsibility to the DisCO.NP and its members. Those wanting to progress from Casual to Committed have two options: DisCOLarships (practical DisCO training with no firm expectation of joining the DisCO). DisCO Dating: Intense mentoring program for applicants to join the DisCO in which they are being mentored.

      High level, I think it may make more sense to lead with "TL;DR"s rather then ending with them so that as people are browsing through the wiki, they can quickly decide if they're on the right page or not.

    26. 1 DisCOLarships: Where individuals regularly "visit" the DisCO.NP to learn about DisCO culture and structure in the real world, get to know the people, etc. There are minimal responsibilities and the DisCOLar is free to start their own DisCO afterward or join the same DisCO they have trained in. 2 The DisCO Dating Phase: Where potential members make a firm commitment to go through the DisCO.NP's mentoring and training program in order to become committed members or DisCONauts. There are considerable, consented-upon responsibilities on the part of the DisCO Dating Member and the DisCO-NP itself during this process.

      The difference between these two options is not immediately clear.

      Is it that the DisCOLar path is oriented towards creating new DisCOs and the dating is oriented towards joining the mothership?

    27. Beyond Contributors, there is another type of casual relationship with a lesser level of responsibility: Supporters.

      This sentence feels too specific in a section that is talking about "casual relationships" in a more general sense.

    28. There are two additional "bridging states" between the Casual/Committed poles, which we will also discuss.

      I don't know that this sentence is necessary, as all of the types of relationships will fall on this spectrum.

    29. within a DisCO Non-Profit

      I feel like this may be too prescriptive. IMO, these roles and responsibilities feel like they'd apply to basically any DisCO.

    30. On the downside, DisCOs are also more complex in the initial stages, although once their learning curve has been overcome, we'd argue that they function more smoothly and are more resilient organizations.

      I don't know that this is inherent to DisCOs as individual organizations! I think that this might appear to be the case given that we're still building out the core of the philosophy while also trying to create organizations that work by these ideals while existing as an explicitly counter-hegemonic endeavor. All that to say, I think you may be selling DisCOs short by including this in there, but understand why it's included right now. My main reason for bringing it up is, we don't want to give people the impression that this is the hardest path possible because it will likely result in slower adoption of these principles.

    31. first, as a description of a legal entity that holds the ability to maintain tangible functions like contracts and agreements, and more intangible ones like commonly held values. Secondly, “trust” is used in the sense of the ability for team members to operate with a specific relationship to one another, according to defined principles and common goals.

      Personally, given your mission, I think it would make more sense to flip these two. You all are human/community first, tech+contractual obligation second and I think this sentence could better reflect that.

  3. Oct 2021
    1. Ruthlessly seek negative feedback. When getting feedback, @tferriss requests the reader highlight: • Anywhere boring • Anything confusing • Anywhere your mind starts to wander Then he asks two questions - what is the: • 10% I must keep • 20% I should cut immediately
  4. Sep 2021
    1. Recent studies found when teachers gave trainee pharmacists frequent low-stakes questions with feedback, students performed better on tests and were more satisfied with the course.  

      references for this?

  5. Aug 2021
    1. There are two ways for someone to be in this quadrant. The unhealthy way, as a people pleaser, with associated resentment and chaos. In a healthy way, everything feels very clear. It’s easy to fit feedback into their mental model, and adjustments feel natural and build on what they are currently working on. This comes from having a good idea themselves about what is happening and how they think they can improve.

      good point on the people-pleaser mindset, also worth considering with ADHD/ASD employees - try and foster more curiosity than chaos

    2. Coachability is made up of two factors: someone’s receptiveness to feedback, and how highly actionable they are (what they do with it).
    3. How do your reports respond to feedback? As managers, it’s our job to grow the people we work with. This is how we build a bench, and scale ourselves and the organization. Of course, this is easy to say and hard to do, and we’ve all encountered a spectrum of people: those with whom it’s easy to accelerate and have a real and lasting impact on, and those where the lasting impact is the relief we feel once we no longer work with them.

      this is also why it is important to have a good culture of frequent feedback. Since it is key to growing the organization, feedback can't be saved for quarterly reviews only.

  6. Jun 2021
    1. We just cannot know all that life will throw at us, and if we want our grading contract to be fair and equitable for everyone, we need to reexamine it, reflect on how it has been working for each of us, and perhaps adjust it. 

      This idea of re-evaluating at regular time points can be a very useful and powerful tool in more areas than just writing.

      Society as a whole needs to look carefully at where it is do do this same sort of readjustment as well.

      It's the same sort of negative feedback mechanism which is at work in the scientific method and constantly improving the state-of-the art.

    2. your goal cannot be to follow orders in order to get a higher grade, instead you are free to listen, consider things, ignore ideas, or ask more honest questions of your readers. You are now free to make your own decisions on your writing. 

      Labor-based grading in writing allows students to listen and adjust to comments which gives them greater freedom and autonomy in both their learning process as well as their writing.

      Ideally, in a system like this, a shorter feedback loop of commentary and readjustment may also help to more carefully hone their skills versus potentially hitting a plateau after which it's more difficult to improve.

    1. He notes that authors of such projects should consider the return on investment. It take time to go through community feedback, so one needs to determine whether the pay off will be worthwhile. Nevertheless, if his next work is suitable for community review, he’d like to do it again.

      This is an apropos question. It is also somewhat contingent on what sort of platform the author "owns" to be able to do outreach and drive readers and participation.

    1. @dwhly bug? cannot annotate this video which has caption but in Greek?

  7. May 2021
    1. No it doesn't. I've simply told SvelteKit to ignore the type error from credentials missing. If there's some other issue or missing feature it's not blocked by this. That being said, I wouldn't mind getting this change in
    1. სარგებელი

      • დროის ეკონომია — უფრო მარტივია და სწრაფია ჩანაწერის გაკეთება, ვიდრე უკუკავშირის დაწერა;
      • თვალსაჩინო — ვიდეო-უკუკავშირში შეგიძლიათ მარტივად მიუთითოთ მოსწავლეს დავალების კონკრეტულ მონაკვეთზე, დაწერილი უკუკავშირი მოსწავლემ შეიძლება არასწორად გაიგოს/ ვერ გაიგოს;
      • დემონსტრაცია — შეგიძლიათ თავიდან აუხსნათ თემის ნაწილი, რომელიც მოსწავლემ ვერ გაიგო;
      • გამეორება — პირისპირ, ზეპირ უკუკავშირთან შედარებით, ვიდეო-უკუკავშირს მოსმენა მოსწავლეს რამდენჯერმა შეუძლია, როცა უნდა და რამდენ ჯერაც უნდა, არა მარტო გაკვეთილზე;
      • კომფორტული — სავარაუდოდ, მეტი შანსია მოსწავლეებმა უყურონ ვიდეო-უკავშირს, ვიდრე დაწერილ უკუკავშირს;
  8. Apr 2021
    1. This idea that plants become desirable or aversive depending on their digestive consequences is simple. But, how do grazing animals figure out exactly which plants made them fee l good or ill? One way herbivores apparently accomplish this task is by regarding unfamiliar plants with caution. Animals associate positive or negative effects of nutrients or toxins with novel foods when offered meals that contain novel and familiar foods. When foraging bouts include several novel plants, plants that dominate the diet are probably 'weighted' more than less-consumed plants, even if the minor foods were primarily responsible for the positive or negative feedback. Furthermore, digestive feedback begins within 10 to 15 minutes of consumption which could help animals attribute digestive benefits or liabilities to specific plants. Finally, livestock grazing on rangelands usually become familiar with the forage resource and may seldom encounter truly novel plants. This allows greater opportunity to 'sort out' feedback from individual or similar groups of plants
    2. When a grazing animal smells and tastes a plant, the flavor is either pleasing or distasteful depending on the animal's previous grazing experiences. When a plant is eaten, it provides feedback during digestion. If consumption of a plant improves the nutrient or energy status of the animal, the plant flavor becomes more desirable or pleasing. If eating of the plant yields illness, the flavor becomes aversive and distasteful (Fig. 2). These flavor-consequence relationships form the basis for dietary likes and dislikes, and the animal then seeks highly palatable foods and avoids aversive foods. The resulting behavior patterns generally lead to increased consump- tion of nutritious foods and limited consumption of toxic or low quality plants.
    3. The digestive consequences of forage consumption are determined by plant forage quality and animal digestive and detoxification abilities. This interaction, in turn, affects the nutrients and energy available for animal growth and maintenance.
    1. When an animal eats a plant, it receives digestive feedback in the form of energy, nutrients, illness, or toxicosis. If the feedback is positive, preferences are formed to the plant and if the feedback is negative, aversions are formed. The strength of the preference or aversion is determined by the magnitude, nature, and timing of digestive feedback
    1. Ich finde die Absicht des Autors für Chronik hier etwas unvollständig. Die beschriebene Absichts ist mE die Absicht Gottes. Für die Absicht des menschlichen Autors dieses Buches müsste man noch etwas mehr Hintergrundinformationen sammeln: Wann und Wer verfasst die Chroniken? An welche Zuhörerschaft? Ich weiß nicht, ob das das Potential hat, in die (zu) textkritische Betrachtung einzusteigen oder ob es für den Einstieg zu viel wird, aber sind meine spontanten Gedanken dazu. Bei einem Brief im NT ist es oft klarer bzgl. Autor und Absicht.

  9. Mar 2021
    1. Use the button to get a sharable link to the page with annotations.

      so super dope that you can toggle highlights & annotations to be private or public, and then can share a hypothesis link for a page, and then people can see your highlights on the page that are public, and dont see the ones you set as private, oh wow!!!

    1. See this post's corresponding GitHub Issue for related media, aggregated links, and other minutia.

      It didn't occur to me until just this moment that GitHub might also make for the ideal commenting integration. And the... second-most ideal annotation integration, naturally.

      Basically, leave comments there!

  10. Feb 2021
    1. It is important to acknowledge that education is essentially a political activity.

      Re-reading this week's chapter, I keep getting hung-up on this line. While I agree that education is affected by political views, I don't know that it is necessarily appropriate to state that education is a political activity. By design (or perhaps, by hope), education should be decidedly non-political. The reality of education, perhaps, is very politically driven, but something about the wording of calling education itself a political activity doesn't feel truly accurate.

  11. Jan 2021
    1. While this tutorial has content that we believe is of great benefit to our community, we have not yet tested or edited it to ensure you have an error-free learning experience. It's on our list, and we're working on it! You can help us out by using the "report an issue" button at the bottom of the tutorial.
  12. Dec 2020
    1. please feel free to open an issue here on GitHub with questions/comments/improvements/etc
    2. Discuss this post on the web:
    3. These are valid comments. I think it is worth noting that svelte didn’t choose a non-javascript method for fun or because we think we should redesign the language. The additional constructs, for the most part, are there to allow svelte to more clearly work out exactly what is going on in the code in order to optimise. In short svelte needs a certain amount of information to do what it does and pure javascript is often difficult to analyse in this way. But I appreciate your concerns and comments and we try to take all feedback on board where we can. So thank you!
    1. The exact form of the platform is yet to be finalized, and we want to involve you, the community, in helping to provide ideas and test the new contribution workflow!
    2. Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.
  13. Nov 2020
    1. It is hard to appreciate how important really fast (and reliable) hot reload can be during development, unless you have experienced it yourself. Developers report that it changes the way they create their apps, describing it as being like painting their app to life.
    1. In fact, it’s at the core of the learning process and how the human brain learns.
    2. In everyday life, feedback loops for each of us occur naturally–usually in the form, ‘When I do X, Y happens.’ That’s a kind of feedback loop in the learning process.
    3. A feedback loop in learning is a cause-effect sequence where data (often in the form of an ‘event’) is responded to based on recognition of an outcome and that data is used to inform future decisions in similar or analogous situations.
    1. What vaults this well past SNCF for me (setup time aside), is the limited company choice; it prevents a feedback loop of sorts where a game devolves into running each company in the ground.
    1. Second, you have more frequent opportunities to get feedback. Instead of spending weeks hammering away in isolation, only to discover that you made some mistaken assumptions, you can get feedback at each intermediate stage. You become more adaptable and more accountable, because you are performing your work in public.

      Intermediate Packets give you more opportunities to get feedback

    1. If you have further thoughts here, please participate in the discussion on the issue tracker: #256.
    1. In Rust, we use the "No New Rationale" rule, which says that the decision to merge (or not merge) an RFC is based only on rationale that was presented and debated in public. This avoids accidents where the community feels blindsided by a decision.
    2. I'd like to go with an RFC-based governance model (similar to Rust, Ember or Swift) that looks something like this: new features go through a public RFC that describes the motivation for the change, a detailed implementation description, a description on how to document or teach the change (for kpm, that would roughly be focused around how it affected the usual workflows), any drawbacks or alternatives, and any open questions that should be addressed before merging. the change is discussed until all of the relevant arguments have been debated and the arguments are starting to become repetitive (they "reach a steady state") the RFC goes into "final comment period", allowing people who weren't paying close attention to every proposal to have a chance to weigh in with new arguments. assuming no new arguments are presented, the RFC is merged by consensus of the core team and the feature is implemented. All changes, regardless of their source, go through this process, giving active community members who aren't on the core team an opportunity to participate directly in the future direction of the project. (both because of proposals they submit and ones from the core team that they contribute to)
    1. Please don’t be shy to submit your project if you’re just starting out!
  14. Oct 2020
    1. The authors noted that instructive or process feedback types were rarely observed in the instructors’ messages to students.

      Why?

      • time-consuming
      • the sense-making of students' learning
      • the ways to provide formative feedback
      • the sense-making of feedback by students What kind of feedback would be most useful to students? How can we make sure that students interpret the feedback correctly?

    Tags

    Annotators

    1. When giving negative feedback, teachers can use the positive sandwich approach—starting and ending with a positive comment

      Compare and contrast to what Claude Steele calls the "Tom Ostrom strategy" - framing feedback in terms of "I have high standards; here is my feedback; I believe you can reach my high standards by taking this feedback."

  15. Sep 2020
    1. It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
    1. I like bundlers. Correction, I like fast bundlers. Bundlers that help me tighten the feedback loop and help me focus on the code. Not bundlers that make me doze off, waiting for the recompilation to finish, while my CPU fan sounds like an old hair dryer.
    1. The present study demonstrated that there are differences between the quantity and quality of handwritten and electronic feedback

      The takeaway messages are the first with experimental evidence for the benefits of electronic feedback for coursework, electronic feedback is an adequate way to provide feedback, and the courses in COVID-19 will be an example of whether electronic feedback is adequate for strong academic performance.

    2. Course and Students

      This study has a robust sample size that will be adequate for the statistical analyses. The experimental design is clear, with the manipulation of the independent variable as the grading format as handwritten or electronic.

  16. Aug 2020
    1. This means that while groups can generate high levels of solidarity, which can in principle be put to powerful political effect, it also becomes harder to express disagreement within the group. If, for example, an outspoken and popular member of a neighbourhood WhatsApp group begins to circulate misinformation about health risks, the general urge to maintain solidarity means that their messages are likely to be met with approval and thanks. When a claim or piece of content shows up in a group, there may be many members who view it as dubious; the question is whether they have the confidence to say as much. Meanwhile, the less sceptical can simply forward it on. It’s not hard, then, to understand why WhatsApp is a powerful distributor of “fake news” and conspiracy theories.

      Instead of positive feedback like this, is there a way to create negative feedback loops in these social media apps?

    1. I honestly don't know what you find unclear about this question. I think you initially misread. I edited out your title change because it wasn't what I'd intended and it misled others. I edited in two more sections to clarify. The last section makes it as clear as I can: A single question provokes 1 of 3 responses (not necessarily answers). To chose between them I need to understand acceptable scope of both question and answers. Yes this topic is a muddy one, that's why I'm asking! I want others to help me clarify the unclear!
  17. Jul 2020
  18. Jun 2020
    1. Just as journalists should be able to write about anything they want, comedians should be able to do the same and tell jokes about anything they please

      where's the line though? every output generates a feedback loop with the hivemind, turning into input to ourselves with our cracking, overwhelmed, filters

      it's unrealistic to wish everyone to see jokes are jokes, to rely on journalists to generate unbiased facts, and politicians as self serving leeches, err that's my bias speaking

    1. Note that we are not making the common argument that making new tools can lead to new subject matter insights for the toolmaker, and vice versa. This is correct, but is much weaker than what we are saying. Rather: making new tools can lead to new subject matter insights for humanity as a whole (i.e., significant original research insights), and vice versa, and this would ideally be a rapidly-turning loop to develop the most transformative tools.
    1. Most people think you build the product then you market it. Thinking in loops means you build the marketing into the product. The product doesn't precede the marketing. The product is the marketing.

      By thinking in loops Harry Dry refers to a way of thinking about your acquisition strategy as being part of your product.

      This reminds me of Brian Balfour's idea of product-channel fit and how stresses that the product gets shaped by its acquisition channel.

  19. May 2020
    1. Future keyword improvements are being discussed in our epic for improving rules, where anyone can add suggestions or requests.
    1. Help & feedback Docs Edit this page to fix an error or add an improvement in a merge request Create an issue to suggest an improvement to this doc Show and post comments to review and give feedback on this doc