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
Thought I would summarise and comment on some of the above comments:
TDD is a great practice and I cant talk highly enough of it.
However, if I was in your position I would not worry so much about TDD for now and instead concentrate on having some good unit tests around your code.
You can always start using TDD a bit later on in your project, when the tricky business logic comes around.
I wouldn't want you to have a bad experience of TDD, which could happen if you are under delivery pressures and have no experience in using the practice.
It could be an idea to try out a few TDD Katas at home to become familiar with it, before using it at work.
Some good Katas can be found here
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).