Exactly. I mostly use the debugger to see the call stack so I can understand what calls what without having to read everything. I can work backward from the fau

Exactly. I mostly use the debugger to see the call stack so I can understand what calls what without having to read everything. I can work backward from the faulty behavior to better understand the context of the issue. I rarely actually fire up the debugger, and I try to refrain from gratuitous prints (though I use them in emergencies or if a debugger isn't convenient). I think this makes me a better programmer, though that's really hard to tell objectively.