One Rule to Rule Them All
summary
Claim: aim for changeability not correctness — there is no 100% correct code and requirements change ~25% per year so systems must be easy to adapt. Advises practical moves: extract rules into a Rule table and a Google Sheet with a validation hook so non-programmers update tax rates, split into modules, and prefer small reversible choices. Critiques 100% test-coverage as busy work (write tests to enable change, then delete), and recommends a handwritten daybook to record changes and train intuition.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:46Back to the 1990s
- 3:49Classic waterfall
- 5:22Theorem proving
- 6:17100% test coverage
- 7:53Correct code
- 11:53Dave's postulate No. 1
- 12:44Change
- 16:01Manifesto for Agile Software Development
- 20:22Agile is Dead
- 25:14Easy to change
- 26:13How?
- 34:28Dave's postulate No. 2
- 35:09Conscious & subconscious
- 42:21Experience
- 46:22Handwrite on paper
- 49:07Make it easier to change
- 49:36Outro
