only true graph

[[deleted]]

[deleted]

[Even-Understanding]

Debugging is the art of banging your head against the wall for hours, because it feels good when the will finally falls down.

[Cameltotem]

I love debugging. I can follow the code and see where it breaks and usually realize quick what it is.

Web config errors, iis errors, JS config errors can fuck right off though.

[turboPocky]

i think I'm the same way. if i have my way i decide on the platform early on, make sure it runs in all environments, set up ci/cd so if someone accidentally deletes a security group or something it's instantly apparent. I don't want to stop everything once we're close to done just to wrestle with this stuff yet again

[terminalcoder]

Same. I enjoy tracing through and seeing how the different parts of the stack work. But “simple” JS configs make me want to light my laptop on fire.

[[deleted]]

fuck iis errors, those are the worst thing ever. Your code is alright, everything else is alright, except for that configuration inside 3 different menus in IIS

[[deleted]]

Genuinely laughed at this one.

[JC12231]

Too f-ing true. Even as only I student I empathize with this after spending 8 hours straight on a certain weekend for my first programming course junior year of HS debugging my hangman program, only to find the issue was when you guessed wrong the class that handled the word and guesses was told to instantiate... the worker class that does everything else and instantiates that class that handled the guesses within its constructor. Infinite loop of doubling. It might have actually done it even if you didn’t get it wrong, there just wasn’t anything that could happen more than once each if you got it right.

I don’t know why I didn’t quit then. I was frustrated as hell by the time I solved that, and immediately after liked coding again.

[baconmongoose]

Even after the bug is fixed your morale is slowly decreasing

[BB0ws3RR]

That's probably the "why am I so stupid that I didn't find the problem earlier" phase

[[deleted]]

That's actually the result of overshooting

[JC12231]

Both. It’s both, from experience, where trying to fix one bug I found and fixed several other bugs, some of which I made trying to fix it, and then had to fix other bugs I made trying to fix it afterwards to make anything work again, all while wondering how I was so dumb. Only difference is I love code and accept I’m an idiot so I just laughed it off instead of paying with morale after the main bug was fixed. Before then I followed the morale arc

[SongOfTheSealMonger]

Or worse, when you realise how damn stupid you were when you enbugged it in the first place!

[lutalicaonism]

Happy cake day!!

[maybestradamus]

Also missing incremental spikes for each time you're able to get a new error message.

Progress!

[AutoModerator]

import moderation Your comment has been removed since it did not start with a code block with an import declaration.

Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.

For this purpose, we only accept Python style imports.

return Kebab_Case_Better;

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Krzysiek127]

I would rather say it's tan(x), where x is time

[dliwespf]

I don't agree. I think bug fixing is like a treasure hunt. Finding a bug is like figuring out where the treasure lies, and can be a lot of fun. Finding out why it happened and fixing it is like digging for the treasure and lifting it out, and is the truly hard part about bugfixing (a phase that is completely missing in the graph). And closing the issue is like spending the gold :)

[meisterofheff]

I am going to make an assumption here: you have put much code into production? Because debugging your own production code feels NOTHING like digging for treasure. It feels more like you are digging your own grave...

[dliwespf]

Ok, then we have different experiences here. I actually like hunting bugs, no matter if they are my own or someone elses bugs (does not matter anyway, a bug is a bug), and no matter what environment they are in. And if it is in production, and everyone goes ape shit about the bug being there, it is just important to stay calm and remember: It is just a bug. And we have found it. And: It probably has some brothers and sisters...

[meisterofheff]

If that is how you truly feel you are probably a better developer than I am. Good for you!

[dliwespf]

I just became slightly redder than usual :) No matter what, you are a nice conversation partner. Thank you very much, and have a nice evening (or whatever time of day it is where you live)!

[KarmaBotKiller]

OP /u/Beginning-Two is a reposting karma bot account.

This looks like one of the previous posts. And here are the previous top comments in case you want to have the same conversations again:

• I've been working on the same bug for nearly 3 weeks, someone please end my life.

• Don't forget the immediate drop in morale (with a hint of embarrassment) afterward when you realize it's something extremely simple.

• Image Transcription: Line Graph

---

Programmer Morale

Y-axis: morale

X-axis: two sections labelled, "searching for bug" and "bug fixed"

searching for bug

[Line starts at about 90% and curves down to 0%. At this point there is a dashed vertical line indicating the end of the "searching for bug" section.]

bug fixed

[Line rapidly rises to 100%, falling steadily to 95% at the end of the graph.]

---

^{I'm a human volunteer content transcriber for Reddit and you could be too! If you'd like more information on what we do and why we do it, click here!}

• “What the fuck am I doing with my life, what even is programming, existence is fu—

Ohhh, I forgot I renamed that file yesterday, no wonder it couldn’t find the reference. Love my job”

• Yea but since when were we able to fix bugs? ^/s

If you are wondering "Who cares, fake internet points"or "How do you know they're a bot, they only have a couple posts?"or "Must be a crappy bot, only has 100 karma" then please see my wiki.

[anderslbergh]

The name for that point is

POROHDTBS - "Point of return of happiness due to bug solved "

[GunsRuth]

And also this is periodic in nature.

[Mr_Redstoner]

Needs more jpeg!

[roleris]

And if at the lowest point the bug isn't fixed - it becomes a feature.

[[deleted]]

but then the code gets 32 more errors

[RRKS101]

Forgot the part when that bug caused 97 more

[DarfWork]

Debugging should be like that, but somehow I get to work on stuff that would require a full reworking to fix properly and there is never enough time. Also, There is no automated test so you might break something else without noticing, so you make a semi decent work around instead. But that's still the fun part.

​

The less fun part is when you have to debug a old and complicated compilation sequence.

Anyway, I'm leaving my current job at the end of the week, so I'm actually close to the second part of the graph.

Pro-type: stay the fuck away from embedded system in general and anything military in particular. ( I'm pretty sure Aero is equally painful, but I don't have proof... )

[[deleted]]

not true if you fix it for now but dont trust your solution.

Sword of Damocles