Hi. I'm the author of the post. I actually agree here. As soon as I realize it's going to be non-trivial for me to trace the issue with the debugger, more and

Hi. I'm the author of the post. I actually agree here. As soon as I realize it's going to be non-trivial for me to trace the issue with the debugger, more and more instead of setting up complex conditional breakpoints I just step back from the computer and have a think, and white board out my current understanding of how things are working. Usually, I get an "aha!" moment pretty quickly. However, sometimes I don't get that "aha!" moment quickly, it random issues endup taking 30 minutes to hours to trace. What I've come to understand is that's only true because debuggers are so limited. For example, white-boarding out the problem is incredibly useful.. why can't my debugger do that for me, by presenting a number of ways to layout the program and some filters so I can just view my code as graph and watch execution slowed down? Today's debuggers even in their best form are like looking through a tiny peep hole at a picture, I can only see this tiny section... but I want to see the whole picture.