One Rule to Rule Them All
summary
Claims that a single design rule—make it easier to change—beats chasing “correctness,” backed by data that requirements shift about 2% per month so a year-old spec is ~25% wrong and half of ’90s projects never finished. Demonstrations include modularizing tax rules into data (Google Sheets), preferring single-change points over constants, taking fractal small steps with rapid feedback, and a simple ritual—write it down and say it aloud—to train intuition; doing this measurably improves estimates and decision quality.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:28Back to the 1990s
- 3:57Classic waterfall
- 6:14Theorem proving
- 6:58100% test coverage
- 8:17"Correct code"
- 12:05Dave's postulate No. 1
- 13:50Change
- 16:18Manifesto for Agile Software Development
- 19:58Agile is Dead https://youtu.be/a-BOSpxYJ9M
- 23:23Easy to change
- 24:20How?
- 32:41Dave's postulate No. 2
- 35:07Building intuition
- 37:37Conscious & subconscious
- 43:31Experience
- 46:37Handwrite on paper
- 50:27Make it easier to change
- 50:48Outro
related talks
36mChange without changing: Keep your project healthy by refactoring your code
36mProgramming Is the Easy Part
31mKeep Software Weird
50mThe Effective Developer - Work Smarter, Not Harder
01h 02mAll Things Open 2020 Keynote (Speakers Only) Day #2
29mThe Undeniable Virtue of Doing Less
33mHow Minimalism Helps Build High-Quality Products
30mMaintaining Sanity and Code