The Standup How BAD is Test Driven Development?
15 snips
May 14, 2025 
Join Casey Muratori, a software engineering expert and regular guest, as he digs into the quirks of Test Driven Development (TDD). They hilariously evaluate the pros and cons of TDD through real-world anecdotes. The discussion shifts to Progressive Driven Development, emphasizing careful changes for better user satisfaction. With amusing tales from the NeoVim project, they reveal the challenges of maintaining effective tests. Lastly, they delve into the paradox of code coverage, critiquing unrealistic standards with a witty nod to pop culture.
AI Snips
Chapters
Transcript
Episode notes
TDD Produced A Test-Friendly But Impractical API
- ThePrimeagen used TDD to design a card-deck API and it passed tests but produced an interface unsuitable for the game integration.
- He rewrote the interface after discovering it was great for tests but poor for actual usage.
Iterate Implementation Then Add Tests
- Co-create tests after exploring how you want to use a feature to get faster iteration feedback.
- Write a quick implementation, then add tests to validate behavior and refine usage.
TDD Can Misalign Developer Focus
- Casey argues TDD shifts developer focus toward tests and away from designing good production APIs.
- He calls programming zero-sum: time spent driving code by tests reduces time designing for real use cases.