It's funny that many people here seem to think TFA is a criticism of TDD, which is telling, IMO. It seems many people feel that TDD is always a net benefit to t

It's funny that many people here seem to think TFA is a criticism of TDD, which is telling, IMO. It seems many people feel that TDD is always a net benefit to the software development process, regardless of how it is implemented. I saw the same thing with agile development and object oriented programming: just follow the buzz and software will be better. The author is not arguing against TDD. Instead, the authoR is simply stating it is possible to do it poorly. Everybody should be looking at every process they implement and deciding if it provides value and how it can be done better. Doing anything else is cargo cult development and doesn't lead to better software.