With two of the projects I’ve been working on finally out the door, I’ve finally got some downtime at work. To make use of the time, I’ve started reading Debugging Applications for Microsoft .NET and Microsoft Windows by John Robbins. One recommendation he makes that’s very useful is to treat warnings in managed code as errors. I followed that advice for our in-house bug tracking tool (a customized version of the IssueTracker starter kit) and it revealed at least a couple dozen instances of methods that needed to be overriden, unreachable code, declared but unused variables, etc. I wonder how much of the code we’ve written since last year needs the same treatment?