Fallacies of Software Development
summary
Argues that common mistakes are cognitive and concrete: teams not invented here hand-roll a Spring-like framework that costs hiring and maintenance, a free IDE ends up with six developers supporting it, and an overnight widget batch fails at scale until processing is parallelized with worker queues (which fixes throughput). Shows Groovy rejected then adopted as tooling, replaces a 17-argument capitalization routine with a built-in language feature, calls out sunk cost fallacy and recommends rubber-duck debugging and rubber duck style fresh-eyes reviews.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:40Patterns, cognitive biases
- 8:18Not invented here bias
- 15:05Status quo and sunk cost
- 22:29Fresh perspectives
- 28:12Solutioning misconceptions
- 33:22Breaking mental ruts
- 37:34Dogmatism and impostor syndrome
- 41:30Specialization limits
- 46:04Q&A
