4 ms·
Print debugging is a case of the Flub Paradox. Having experienced the higher plane of fully integrated IDE / run / debugging with arbitrary expression evaluati
by Sahhaese 8y ago
Print debugging is a case of the Flub Paradox.
Having experienced the higher plane of fully integrated IDE / run / debugging with arbitrary expression evaluation, conditional breakpoints, etc, I can't even imagine how anyone could work with "print debugging".
- wtetzner 8y agoI actually have gone in the opposite direction. I used to use a step-through debugger for all my debugging needs, but at this point I pretty much only do printf debugging. I find that in most cases it's easier for me to figure out what's going on, because I can quickly scan a log of how different variables changed over time, instead of having to step through one step at a time.