Hacker News Reader

The TDD one I sort of half agree with.

Purism and zealoutry are rarely a good reaction to anything, but I've seen a lot of dodgy code that, if it had been written with at least testability in mind, or with a test first it wouldn't have been half as dodgy.

View on HN

>test first it wouldn't have been half as dodgy.

Feel part of this, in my very little experience, is with tests focus is getting smallest thing working so less to go wrong

I think another commenter said something poignant around this as well; it’s great too if you are working to a spec. For exploration it might be a cumbersome approach to go all in with.

I tend to do TDD because I hate having to pull up a full application, run the thing and then eyeball a result. The problem with TDD zealotry is that often they'll induce all sorts of architectural rot (DHH did a thing on test induced design damage a while back) in the name of testability

Reply on news.ycombinator.com