I enjoy reading blog comments. In most cases, I enjoy it more than the actual blog article itself. I also really enjoy blog posts about improving process and becoming more productive.
Often, I’ll read a article about testing, and will casually skip over comments about “Why should I TDD? There is no evidence that it actually does something?”. I also skip comments with name calling and the like. Unfortunately, there is one type of comment that I can’t skip over: If you question why we are testing, then we (as developers) have failed.
This one comment in particular went something like, “when things change and propagate up the code base, doesn’t having unit tests mean twice the work?”. I only have one answer for a question like that. YES! It does mean twice the work. The alternative is worse. The alternative is not know how much work will be needed. The best case scenario that I can think of would put it some higher multiple than two.
This is just something to think about the next time you think that skipping that one small unit test.