|
|
|
|
|
by bluefirebrand
1406 days ago
|
|
> If you don't have a good idea of where to look, debug output from several places might also be nicer than having the program stop at lots of breakpoints that turn out to not be useful. I have the exact opposite opinion. Firing up the debugger is what you do when you no longer know where to look, because you need it to examine the whole program state and have the ability to step through. Writing a console log with output from a variable is the precise "I already know what the problem is, all I'm doing is verifying it" approach. > if you have to restart the application/module/whatever anyway, doing that in a debugger instead of a non-debug run is also just a click A click that spawns a process that takes 10x longer to spin up. Debuggers are slow and heavy. |
|