Should I Use TDD?

Question

I\'m the only developer in my (very small) company and I\'m about to start on a medium sized ASP.NET web application for said company.

I\'m trying to figure out if

Answer 1

Thought I would summarise and comment on some of the above comments:

1. Yes TDD is about Design. It is not about testing.
2. Not sure why QA were getting involved with George’s design stage. It sounds like they were specifying automated tests. As Tim pointed out, it’s a Development Process.
3. Kevin, you said ‘skip the testing’. One more time. TDD is about Design, it is NOT about testing. OK You can skip the design, but the finished app will be buggy and unsupportable.
4. Roshan mentioned, ‘executable specification of what your component should do’. That means fully up to date documentation. When you are new to a project you can get up to speed very quickly, you can see exactly what the original Developer intended. And, as Jon mentioned you can make code changes and ensure that nothing is broken.