Reading & resources
The books, articles and talks that shape how I code, with my key takeaways.
I list here the resources I read and watch from August 2026 onward, with my own summary. I didn't track my reading before, so I'm making myself re-read and re-watch, and this page grows over time.
My takeaway : Test behaviours, not classes. “One test class per production class”, with a mock per dependency, builds a harness that blocks all refactoring — the opposite of what TDD promised. A test is triggered by a requirement, never by creating a class. The answer was already in Kent Beck’s book (2003); we had just misread it.
Key points
- The “unit” in unit test is the test’s isolation, not the class: a test can span several classes.
- RED-GREEN-REFACTOR: go green “dirty” (as fast as possible); refactoring is the non-negotiable step.
- Never couple tests to classes extracted during refactoring — otherwise any change breaks everything.
- Over-mocking couples tests to the current design. Test at the “port” (hexagonal), not internal details.
- TDD
- Tests
- Craft