On How Your Brain is Conspiring Against You Making Good Software
summary
Decisions about code and teams fail for specific, measured reasons: logical puzzles show only 9% or 4% success on syllogisms and the Wason four‑card task, concrete examples raise success to 73%, and planners predict 34 days but take 56 on average with only 30% finishing on time. Confirmation bias and sunk‑cost errors make debugging drag, interrupted breaks and pairing improve problem solving, selective attention and the availability heuristic skew hiring, and diverse teams boost associative creativity and better solutions.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:11On how your brain is conspiring against you making good software
- 0:25Engineering Manager@ DigitalOcean
- 4:24On Being Logical
- 6:15On Bugs and Debugging
- 11:01On Others' Code
- 13:05On Planning Your Work
- 15:08On Open Offices
- 19:20On Knowing Your Worth
- 22:21On Assembling a Team
- 28:12On Getting Past This
related talks
29mOn How Your Brain is Conspiring Against You Making Good Software
38mThe Not So Rational Programmer
51mThe Psychology of Code
47mThe Psychology of Software Teams
44mBehavioral Software Engineering
38mFallacies of Software Development
57mDebug your thinking
47mFantastic Biases & Where to Find Them in Software Development