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
TDD, pseudo TDD and quasi TDD. Lots of different approaches. It just depends on who enforces the level of TDD. Lots of pros and cons too, again it depends your personnel. This is one of those double edge swords philosophies. If you don't know what you're doing or there is a separate level of understanding within your group(s), it will bog you down and lead to internal struggles, which eventually leads to removing TDD altogether. Also TDD is different from (Just writing tests).