I have tried * Rubber Ducking - Explaining the problem to your rubber duck * Invert Thinking - What do I think is true about this system that might be incorrect
These techniques have helped me greatly but I was just wondering if anyone had any other tips or perhaps a chapter of a book they could point me to that would be beneficial
Pernosco (pernos.co) is an even more powerful debugger. It takes an rr recording and gives you an omniscient view of it. It's difficult to describe how powerful this is, but you should definitely watch the demos on their webpage. I think that this is what all competitive debuggers will be like in 10 years. (Any debugger that doesn't gain these features will simply fall out of use.)