TDD is an antidote for uncertainty

Everyone on a team has to buy into TDD for it to work.

That’s partly why so few teams do it.

What’s wrong with “Just build it and debug it later?” They ask.

Nothing, as long as you’re OK with being uncertain how long it will take to debug, and how long it will take to fix future bugs when you find them. Even if you’re 100% confident in that; what happens when your most junior team member draws the short straw. Are you certain they’ll find it in the same amount of time you would?

TDD is a strategy to combat uncertainty. Uncertainty in your codebase, in your team, and whether or not you’ll be woken up by a production issue at 3am on a Saturday morning.

Leave a Reply