308 Matching Annotations
  1. Last 7 days
  2. Jun 2021
    1. better “decision hygiene” such as designating an observer for group decisions, to prevent common biases and noisy judgments. For example, they can ensure that participants in a team reach independent assessments before coming together as a group to aggregate their decisions.

      Approaches for decreasing noise in decision making

  3. May 2021
    1. Career decision making involves so much uncertainty that it’s easy to feel paralysed. Instead, make some hypotheses about which option is best, then identify key uncertainties: what information would most change your best guess?

      We tend to think that uncertainties can't be weighted in our decision-making, but we bet on uncertainties all the time. Rather than throw your hands up and say, "I don't have enough information to make a call", how can we think deliberately about what information would reduce the uncertainty?

    1. Dr Nisreen Alwan 🌻. (2021, March 14). Exactly a year ago we wrote this letter in the Times. We were gobsmacked! We just didn’t understand what the government was basing all its decisions on including stopping testing and the herd immunity by natural infection stuff. We wanted to see the evidence backing them. [Tweet]. @Dr2NisreenAlwan. https://twitter.com/Dr2NisreenAlwan/status/1371168531669258242

  4. Apr 2021
  5. Mar 2021
    1. Chapman, G. B., & Coups, E. J. (2006). Emotions and preventive health behavior: Worry, regret, and influenza vaccination. Health Psychology: Official Journal of the Division of Health Psychology, American Psychological Association, 25(1), 82–90. https://doi.org/10.1037/0278-6133.25.1.82

    1. Baker, C. M., Campbell, P. T., Chades, I., Dean, A. J., Hester, S. M., Holden, M. H., McCaw, J. M., McVernon, J., Moss, R., Shearer, F. M., & Possingham, H. P. (2020). From climate change to pandemics: Decision science can help scientists have impact. ArXiv:2007.13261 [Physics]. http://arxiv.org/abs/2007.13261

  6. Feb 2021
    1. While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.
    1. In object-oriented programming, information hiding (by way of nesting of types) reduces software development risk by shifting the code's dependency on an uncertain implementation (design decision) onto a well-defined interface. Clients of the interface perform operations purely through it so if the implementation changes, the clients do not have to change.
    1. Say, for instance, a hypothetical self-driving car is sold as being the safest on the market. One of the factors that makes it safer is that it “knows” when a big truck pulls up along its left side and automatically moves itself three inches to the right while still remaining in its own lane. But what if a cyclist or motorcycle happens to be pulling up on the right at the same time and is thus killed because of this safety feature?

      I think that an algorithm that's "smart" enough to move away from a truck is also "smart" enough to know that it cannot physically occupy the same space as the motorcycle.

  7. Jan 2021
  8. Dec 2020
  9. Nov 2020
    1. The syntax of the fallback, like that of custom properties, allows commas. For example, var(--foo, red, blue) defines a fallback of red, blue — anything between the first comma and the end of the function is considered a fallback value.
    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)
  10. Oct 2020
    1. To silence circular dependencies warnings for let's say moment library use: // rollup.config.js import path from 'path' const onwarn = warning => { // Silence circular dependency warning for moment package if ( warning.code === 'CIRCULAR_DEPENDENCY' && !warning.importer.indexOf(path.normalize('node_modules/moment/src/lib/')) ) { return } console.warn(`(!) ${warning.message}`) }