2 ms·
In code I have written, understand how things come together, how things control and data flow from one subsystem to another, I find I don't really need a debugg
by xen0 5y ago
In code I have written, understand how things come together, how things control and data flow from one subsystem to another, I find I don't really need a debugger and print statements provide the same information. In these cases, I'll use whichever is easier to get going with; if stdout etc isn't immediately reachable, or recompiling is awkward then a debugger is useful. But sometimes getting a debugger running is harder than just rerunning a routine again with print/log statements.
On the other hand, when I'm working with a system that I don't know inside and out, a debugger is immensely valuable for helping me 'navigate'; to see what actually gets called when some interface/virtual method is called.
I live in the second world more often than the first.