This is a bad article, based on a fundamental misunderstanding of TDD, as virtually all the comments on the blog post itself and here on HN attest. People don'

This is a bad article, based on a fundamental misunderstanding of TDD, as virtually all the comments on the blog post itself and here on HN attest. People don't spend weeks writing tests for all the functionality and then write the tests. That's not what even the most die-hard TDD advocates do. I think many people here (like me) clicked through to read a well-reasoned article about how TDD enthusiasm may have gone too far, but sadly, this isn't that. HN readers would do well to just move on, and the author would probably be well served by the advice of some of the commenters on his blog to take this post offline.