The five stages of debugging

Question

1.Denial
"I'm sure this is right" or "This is impossible"

2. Bargaining/self blame
"Can you please work? I only have 1 hour to complete this!" or "if I fix this, I'll only have 14 errors left!"

3.Anger
"You better get your @&!#

Answer 1

1. Realization.
" Wow. The codes I write are truly impecca --- Erm, no, the program isn't producing correct results. dARN UNHOLY CODES F -- "

2. Identifying errors.
" Well ok, I've placed print statements everywhere and now I see that input 89 causes overflow. This should be an easy fix. Datatype. "

3. Implementing fix.
" The fix works, but now the code looks bloat because it isn't optimised for the tweaks I made initially. No, I can't live with this piece of abomination. "

4. Backspacing.
" Yep, I don't need this. That seems to be bloat. Delete that one too. Whoa, I don't even need these 3 header files lol, what was I even thinking. "

5. Release.
" K guys, fix implemented. Hope it runs without errors. "

Answer 2

lol that's me 😄😄
I have add something though

2.5. Fixing errors (not really)
*Compilation error* "oh okay, so that's the error. let me run this again. I cant believe how idiotic I was to write that line of code--WHAT? THIS WASN'T THE ERROR? COMPILE YOU PIECE OF S----"

Answer 3

Well I normally have two reaction:
1.Why isn't this code running😤
2.Why is this code running😮