The Well-Balanced Programmer
summary
Argues that combining Getting Things Done with test‑first programming solves concrete problems: use the two-minute rule and ticklers to stop significant work slipping, apply test‑driven development to catch bugs and rebuild a three‑month mess in nine 14‑hour days, and apply dependency inversion to move details up the call stack so refactoring becomes feasible. Uses a DMZ/happy‑zone universal architecture and Theory of Constraints to pick which red‑arrow problems to fix, yielding fewer bugs, steadier progress, and lower volatility in feature cost.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:45The Illusion of Control
- 6:37Arguments
- 10:33Pain
- 16:41Getting Things Done
- 22:18Second System Effect
- 26:49TestDriven Development
- 30:55The Test List
- 32:46Proven Path to Effectiveness
- 39:38Abstraction
- 42:26The Happy Zone
- 48:21Integrated Tests
- 51:23Universal Architecture
- 54:55Passion is bullshit
- 55:43You need to plan
- 57:18Theory ofConstraints
related talks
48mPair Programming, TDD and Other Impractical Things
36mProgramming Is the Easy Part
31mThe Effective Developer - Work Smarter, Not Harder
49mFrom Busy To Effective Developer
01h 03mThe Effective Developer - Work Smarter, Not Harder.
52mThe Zen of Programming
50mThe Effective Developer - Work Smarter, Not Harder
51m"Time Management for Developers"