Heuristics That Almost Always Work An Article by Scott Alexander astralcodexten.substack.com Sometimes there’s a Heuristic That Almost Always Works, like “this technology won’t change everything” or “there won’t be a hurricane tomorrow”. And sometimes the rare exceptions are so important to spot that we charge experts with the task. But the heuristics are so hard to beat that the experts themselves might be tempted to secretly rely on them, while publicly pretending to use more subtle forms of expertise. …Maybe this is because the experts are stupid and lazy. Or maybe it’s social pressure: failure because you didn’t follow a well-known heuristic that even a rock can get right is more humiliating than failure because you didn’t predict a subtle phenomenon that nobody else predicted either. Or maybe it’s because false positives are more common (albeit less important) than false negatives, and so over any “reasonable” timescale the people who never give false positives look more accurate and get selected for. expertiseheuristicsprediction
Beauty and compression An Article by Scott Alexander astralcodexten.substack.com The Buddha discusses states of extreme bliss attainable through meditation: Secluded from sensual pleasures, secluded from unwholesome states, a bhikkhu enters and dwells in the first jhāna, which is accompanied by thought and examination, with rapture and happiness born of seclusion. ...If you could really concentrate on a metronome, it would be more blissful than a symphony. The jhāna is also a strong contender as a theory of beauty: beauty is that which is compressible but has not already been compressed. The Abode of the Unsymmetrical beautysilencesensesattention
Negative Creativity An Article by Scott Alexander slatestarcodex.com Coming up with entirely novel ideas is really, really hard. Misinterpretation as inspirationSit Down And Think About It For Five Minutes ideascreativitymetaphor
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality