Honestly depending on how you interpret TDD it might be to strict but thinks which I belive are never to strict and always a good idea is: - Writing tests firs

Honestly depending on how you interpret TDD it might be to strict but thinks which I belive are never to strict and always a good idea is: - Writing tests first. - Have a write test => write code => loop. But there are some people which are pedantic about how small the loop needs to be or insisting that TDD excludes doing any planing about aspects like how you likely will structure code on a larger picture and similar (i.e. software architecture). At the same time there are tools/library/framework/language combinations which are testing in generally really hard and can play really bad with TDD. While I believe such tools should be avoided there are situations in which you can not do so and in which you furthermore due to e.g. time constraints are simile not able to do any proper testing including TDD. It's kinda a nightmare situations but it does happen. EDIT: Yes I realized I responded to the wrong comment :(