Eric Sink wrote this post in favor of code coverage. I wasn’t terribly familiar with the concept before two years ago, and my current job is the first one where I’ve seen such tools used seriously.
The best applications our organization puts out (correctness, performance, ease of maintenance) are the ones that have unit tests. The application I have the most confidence in though, is the one that has code coverage.
I’m trying to develop that habit for the code I write, so I can be a better example to the team I manage.