The article has a rather narrow perspective on unit testing, given his product is not mission critical. He's basically treating live production as a giant integ

The article has a rather narrow perspective on unit testing, given his product is not mission critical. He's basically treating live production as a giant integration test. Some of my perspectives: class/function level unit testing is only needed for common library code. component level unit testing is critical if you want to do any significant refactoring. non trivial integration tests (especially timing sensitive multithreaded code) can find many subtle bugs that would be too late to find in production. I've written a few tests (for a database engine) that paid themselves many times over.