TDD makes you a better everyday developer
summary
Demonstrates TDD as the red–green–refactor loop with a live IntelliJ demo that creates a Greeter class, writes JUnit asserts, then refactors; claims it produces better code coverage than post‑hoc tests, improves API design and pair programming workflow, and enables safe performance work via micro‑benchmarks in Go. Offers a concrete counterexample (mortgage‑driven development) to show testable code can still be bad, and argues practicing TDD teaches habits that make non‑TDD work cleaner and safer.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:51What is TDD
- 7:35Live TDD coding demo
- 13:30Red-green-refactor cycle
- 14:33Thinking backwards with TDD
- 20:31TDD as scientific method
- 26:12Boolean algebra interlude
- 30:04Does TDD imply good code
- 33:51TDD improves code quality
- 41:54TDD for better coding
- 43:42Closing & Q&A
