[hdi]

The problem I've seen come out of test after is complete implementations with 0 tests. People will just forget to do it!

Especially if working on few different areas of the code at the same time. And it happens often enough for it to be dangerous.

Another issue I've seen pop up is the amount of spaghetti you see when someone said "Screw the tests can do it after". You could or couldn't do it after, cos sometimes things are so coupled it's impossible to test in a meaningful way. This varies between developers of course, more junior people will be coupling things more.

One approach that has worked for me whenever I'm not quite sure how I am going to implement something is something like this.

- First, prototype your feature, go in and go mad, write 0 tests and just try and find out how you're going to build it. - Then, stash it all away, wipe your workspace clean and start with tests. I've found this works for me when I'm not quite sure how I'm going to piece something new together.