How John Started to Like TDD (Instead of Hating It)
summary
Compares three concrete implementations in Java with Spring Boot: starting at the database, starting at business logic, and starting from the external endpoint with tests first. Claims TDD produces faster feedback, earlier defect discovery and easier refactoring; demonstrates unit, integration and acceptance tests using mocks, Docker and a background task that returns a token. Shows synchronous design collapsing at scale (fails with 1,000 services), forces a redesign, and shows the TDD-driven async solution compiles, tests pass and works.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:04Why John and TDD
- 3:14John’s early struggles
- 7:26John’s TDD journey
- 10:35TDD’s power
- 13:46TDD process examples
- 15:54Database-first approach
- 25:20Database-first problems
- 26:22Business-first approach
- 30:10Business-first failures
- 30:53Endpoint-first approach
- 37:54Endpoint-first benefits
- 41:27Lazy developers and TDD
- 42:10Summary
- 42:30Q&A
related talks
56mLearning Spring Boot with TDD
45mTDD makes you a better everyday developer
01h 01mTDD Revisited
58mTDD for database related code, how is it possible?
46mHow to fall in love with TDD
53mHow to fall in love with TDD
41mTesting done right: From bugs to brilliance
52mBuilding Operable Software with TDD (but not the way you think)