3 ms·

Tools help you be more productive. The keystroke reduction in using debuggers far supercedes print debugging. Imo you've blamed tool fetish when it's really in

• throw827474737 4y ago
  You didn't get the point. My juniors work around fallout in some detail instead of solving the root cause or higher level systemic issue by just a little bit of thinking. Sure, there is the right time for a tool, but tbh all of my bugs are usually much quicker solved by thinking, understanding, unit tests with maybe a print than trying to catch something with breakpoints and stepping. And for the other nasty situations (think about concurrency, multiprocess, embedded irq handling) they are not even able to help but only professional tracing is (print-debugging always sounds so amateurish). So > Tools help you be more productive. The keystroke reduction in using debuggers far supercedes print debugging Sometimes yes, but in general I have seen those tools get into the way. For some reason I rarely need them and juniors often get mislead and don't see the forest for the trees.
• d883kd8 4y ago
  Keystrokes are so very much not the bottleneck