Fallacies of Software Development
summary
Lists common cognitive traps and gives concrete countermeasures: an org builds a bespoke cloud platform and even a git server under someone’s desk (not invented here), developers overvalue homegrown code—people pay 63% more for self-assembled furniture (IKEA effect)—and teams keep expensive status quo choices (intellij vs maintained eclipse instances) because of the sunk cost fallacy. Practical fixes include asking “why?”, using fresh eyes, rubber‑ducking or a quick pair call that often solves issues in under a minute, and stepping back to avoid yak shaving and premature solutioning.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:38The Design Patterns
- 5:14The Not Invented Here Problem
- 9:52The Ikea Effect
- 10:38The Mirror Exposure Effect
- 16:54Sunk Cost Fallacy
- 21:27Never Underestimate the Value of Fresh Eyes
- 30:18Imposter Syndrome
related talks
45mFallacies of Software Development
50mFallacies of Software Development
01h 02mCognitive biases in software development
01h 00mCognitive biases in software development
52mYour Brain on Software Development
44mBehavioral Software Engineering
21mDerailing irrationality
55mImprove your thinking, improve your software