How to fall in love with TDD
summary
Argues that TDD succeeds when you follow concrete habits not dogma: keep a test list (pen and paper or file) to pick the next small failing test, always run each new test to see it fail, follow red‑green‑refactor but skip trivial micro‑steps, and prefer the real object over mocks for pure internal helpers. Recommends architecting for testability with hexagonal architecture (ports and adapters), use mutation testing to measure test quality, and notes TDD converts debugger loops into tests so developers can go months without opening the debugger.
AI-written summary · about
chapters (12)
- 0:00Learning TDD feels hard
- 8:58TDD adoption hype cycle
- 13:58Forgotten thinking phase
- 18:32Red to green without overdesign
- 22:46Refactor tests like code
- 25:34Architecting for testability
- 30:39When TDD is not the right tool
- 33:06Test coverage misleading
- 35:14Test behaviors not details
- 40:54TDD reduces debugging
- 42:43TDD productivity flywheel
- 43:47Practice TDD alone?
