Is TDD always the right choice?

For the unfamiliar TDD can be a scary concept, and difficult to justify a need for such significant change in development approach. The fear is due to preconceptions associated with the learning curve and perceived shortcomings such as longer time to implement. Which is entirely false.

“While it is true that more code is required with TDD than without TDD because of the unit test code, total code implementation time is typically shorter.”

There is a natural aversion to adopting a practice like TDD for most experienced developers due to a number of misconceptions.


Many very experienced developers who have worked in TDD still express doubts about it’s desirability. Ayende posts on the topic to initiate some discussion by highlighting his issues with TDD. These issues are then addresses neatly in the following post by Daniel Cazzulino.
More links to come.

Short answer. No.
Long answer. If maximizing return on investment is important to you, and you are working with modern technologies and frameworks. Hell yes.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s