Test-Driven Development Is Stupid (opens in new tab)

Starts with:

  I am against writing unit tests in general, since experience shows that they actually prevent high-quality code from emerging from development

And the quality goes a long way downhill from there. Even if TDD generally led to poor outcomes, this article fails to support that thesis.

This article grumpily skewers its own thesis at the top:

>This indeed makes TDD less ridiculous.

>However, even though I didn’t address this....

(perhaps he should though?)

Inside out TDD (what he talks about) fails horribly, outside in works well.

It isnt even really about TDD actually: low level unit tests suck 90% of the time even if you write them after.

This is a useful way to practice critical thinking by spotting the logical fallacies employed.

My take is that TDD is woke. Everyone has a gut feeling it's stupid but no one wants to be the first one in the team to point out that it's stupid, since if I did I'd get labeled as a cave man whose brain is too small to understand all the intricate reasons why we need to do this seemingly stupid things.