I second this recommendation. Its the best description I've found of how to systematically approach debugging. I read it after I already had lots of industry experience, but still found it useful because it provides a "formal" description for what is usually an ad-hoc process. Its a useful way to think about things.