> For example it's paramount to test your software, but whether this is TDD or not is secondary.
If you don't examine your motivations for writing tests, and evaluate whether they're being fulfilled, how do you know their necessity is paramount?
If you don't examine your motivations for writing tests, and evaluate whether they're being fulfilled, how do you know their necessity is paramount?
Of course, you might not believe that design feedback is an important motivation for writing tests, which is absolutely fine, but then the issue isn't that the OP is "focusing too much on process and methods" - he simply has different processes and methods to you.