[Eric Jarvi] Timely for me, since code coverage is a technique we’re using here… Brian Marick posts How To Misuse Code Coverage: http://www.testing.com/cgi-bin/blog/2003/07/25#code-coverage

Summary: “I wouldn’t have written four coverage tools if I didn’t think they’re helpful. But they’re only helpful if they’re used to enhance thought, not replace it.”

For some reason, my mind has been consumed lately with CLR performance, IL modification and profiling. I’ve started switching my understanding of .NET from “how to do something with the CLR” to “how and why the CLR does something”.