I was disappointed by this article. There is no such thing as a "perfect" methodology, so I tend not to trust people who tell me their methodology is perfect. I

I was disappointed by this article. There is no such thing as a "perfect" methodology, so I tend not to trust people who tell me their methodology is perfect. I have a lot more respect for people who recognize the tradeoffs that any methodology forces and then finds the right places to use them and the right places not to use them. And this is not to say anything at all about TDD. There are a lot of good uses for it. It just isn't the One True Paradigm of software development. But then again, neither were dynamic languages, object oriented programming, extreme programming, nor any of the other paradigms that were going to cure the problems of software development that went on to add value when creating well thought out plans for every unique project.