Re:Demystifying Debuggers, Part 2: The Anatomy of a Running ...
by righthand on Tuesday December 24, 2024 @11:00AM
(#42502744)
They did, as never before were people talking to a chat bot to have code generated. Seems different to me, but please more talking down and pettiness.
Re:Demystifying Debuggers, Part 2: The Anatomy of a Running ...
by norir on Tuesday December 24, 2024 @12:22PM
(#42503301)
> Debugging is immeasurably more useful to understand and get to the root of the problem in a complex system
I try to write systems that aren't so complex that I need a debugger but get the same job done. And I choose not to work on systems already so complex that their usage is mandatory. I do not consider this a loss at all. Systems that I write can almost uniformly rebuild and rerun their tests in under a second. I can add (pretty) prints and see the results faster than I can switch to a different tab to run a debugger. I have never introduced or encountered a bug that required advanced debugging techniques besides getting a stacktrace from a crashing problem. YMMV.
They are not
> the way we code is not even print debugging for junior developers.
what
> I know very few senior developers that use a debugger at all
I know very few, too, and it's their loss. Debugging is immeasurably more useful to understand and get to the root of the problem in a complex system than printf'ing and logging.
> What is the best diet for those easily triggered?
The best diet for you is to unplug from the hype trains on Twitter and HN.