631

submitted 4 months ago by cows_are_underrated@feddit.org to c/programmer_humor@programming.dev

177 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] JamBandFan1996@lemmy.ml 78 points 4 months ago* (last edited 4 months ago)

You can take away my auto complete, performance monitoring and all that jazz but you can't tell me a debugging system isn't absolutely essential if you actually want to finish a project in a reasonable amount of time

[-] panda_abyss@lemmy.ca 46 points 4 months ago

Why debugger when print?

[-] Valmond@lemmy.dbzer0.com 15 points 4 months ago

Embedded systems 😁

[-] panda_abyss@lemmy.ca 22 points 4 months ago

That’s what a single red LED is for, right?

[-] skulblaka@sh.itjust.works 14 points 4 months ago

Is the single red LED solid, or is it flashing Morse for "please kill me"?

[-] shaw@slrpnk.net 2 points 4 months ago

Solid, always on. Whether the code runs or not, you know there's an error in it so prepare to go through all of it again.

[-] firelizzard@programming.dev 5 points 4 months ago

Because I don’t hate myself

[-] Quadrexium@sopuli.xyz 1 points 4 months ago

javascript moment

[-] cows_are_underrated@feddit.org 16 points 4 months ago

It depends on what you do, but generally I can't argue against a debugger.

[-] BartyDeCanter@lemmy.sdf.org 14 points 4 months ago

gdb works great without an IDE, and many text editors have autocomplete.

[-] michael@piefed.chrisco.me 11 points 4 months ago

Most text editors like vim/emacs/ect have ways of using a debugger.

I remember vim being a bit involved, but the performance was awesome.

But then if you put enough bells and whistles on text editors, do they become an ide?

[-] Feyd@programming.dev 15 points 4 months ago

But then if you put enough bells and whistles on text editors, do they become an ide?

Yes

[-] TORFdot0@lemmy.world 7 points 4 months ago

9000 IQ programmer starts every project rolling their own debugger instead of dedicating 8GB of RAM to vscode

[-] raspberriesareyummy@lemmy.world 1 points 4 months ago

I think you are not looking at the full picture - there are developments (arguably everything back-end) where a debugging system is absolutely not essential and in many cases (multithreading) outright useless for some types of bugs.

[-] ThirdConsul@lemmy.zip 3 points 4 months ago

I believe that is a vast minority of developments. And tbh multithreading debugging is a breeze in C# on Rider (except race conditions, those will always be tricky, but also easily identifiable).

[-] raspberriesareyummy@lemmy.world 2 points 4 months ago

And I believe you are very wrong in that belief. However, a reliable statistic is not the first search result that I can find, so we'll have to disregard the disagreement on that point. You lost me at your C# multithreading reasoning though. A debugger will always interfere with the processes you are looking at, hence making debugging of multithreading-related errors a game of whack-a-mole.

[-] ThirdConsul@lemmy.zip 1 points 4 months ago

A debugger will always interfere with the processes you are looking at, hence making debugging of multithreading-related errors a game of whack-a-mole.

It's a very pleasant debugging experience when you can easily switch threads, have them log what happened first, check the variables in the thread at the moment in time it was hit (vs now), etc. etc.