> Debugging complex code is hard, first simplify, then debug I've always made it a point to do a first pass just reading code and forming a hypothesis about th

> Debugging complex code is hard, first simplify, then debug I've always made it a point to do a first pass just reading code and forming a hypothesis about the problem (which is often wildly wrong) before making any changes or even running it in a debugger. If nothing else you usually find other oddities, and get more familiar with the code as written. It isn't fast but it tends towards being beneficial for more than just solving the specific bug at hand.