This whole TDD discussion reminds me of the "Safety Third" episode of Dirty Jobs.
Testing is definitely and activity that needs to be kept in mind (i.e. "Safety Third" or near the end, Rowe mentions that it's more like Safety Always). It shouldn't be overdone to the point that you cannot get your objective done.
In reality, there are lots of projects with insufficient automated testing. Preaching about the TDD might sound great until you find out that putting the test there would easily mean nothing gets done. Everyone would love to be able to stop all work and put tests in, but that just ain't gonna happen.
Also the preachiness gets to people - it isn't like people don't know they should write tests; it's just they also have to balance other objectives.
This lead me to think that Uncle Bob kinda misses DHH's point.
Testing is definitely and activity that needs to be kept in mind (i.e. "Safety Third" or near the end, Rowe mentions that it's more like Safety Always). It shouldn't be overdone to the point that you cannot get your objective done.
In reality, there are lots of projects with insufficient automated testing. Preaching about the TDD might sound great until you find out that putting the test there would easily mean nothing gets done. Everyone would love to be able to stop all work and put tests in, but that just ain't gonna happen.
Also the preachiness gets to people - it isn't like people don't know they should write tests; it's just they also have to balance other objectives.
This lead me to think that Uncle Bob kinda misses DHH's point.