Frustrated, yes.
Especially if I've worked on it, given it a break, picked it up in a fresher mindset -- and still couldn't grasp it. Or if I've been breaking down the code and refactoring entirely and getting new, unfixable bugs. Or I decide to finally post my question on StackOverflow after finding it nowhere online, and getting people recommending solutions I tried 3 days ago.
But I live for that moment where I come up to a problem that's plagued me and solve it fairly instantly because of the different mental state I'm in. Makes me feel like there's no problem that's insurmountable without a good nap, yoga, or coffee break.
I read a joke on this rather recently.
Q: What is a that language all developers speak?
A: Profanity.
I swear when something doesn't work. I swear more than that when I ship something great (the former in agony, the later in joy). My colleagues may not know this since I do most of this at night. :D
If I can't fix a problem, that means I didn't look well enough and I am the one to blame (after the person who made that issue in the first place).
I do swear from time to time, but not aggressively and not loudly. I think it helps me focus a little bit.
Something like "and here we go again, same crap again, nobody learns or what?!" and that's it.
Also, you could say debugging is like a boss in Darksouls, the harder it is, as far as you don't give up, the more rewarding it gets ;)
No, just need some relax because that mind pain when stuck on some issue mean you on learning status, and this is something good, not need to be aggressive.
You ever see the movie "Falling Down"? You know that part where the Captain tells Prendergast he doesn't like him? "I don't trust a cop that doesn't swear."
I don't trust a programmer that doesn't swear; it means they are not in the proper mindset, have the proper motivation, or the proper passion for the craft to be writing a single damned line of code.
If it takes you four days to reach that point, you're in the wrong huffing business!
But as Patton would say, it must be eloquent profanity. A programmer without profanity couldn't code their way out of a piss soaked paper bag with a hole in the bottom.
Hence why we are overrun by mind-numbingly asshat ignorant bullshit like jQuery, bootcrap, SCSS, React, vuejs, and a host of other dipshit chazerei; but don't you DARE speak out against the code bloat, increased difficulty of development and maintenance, specificity hell, or all the other monuments to ignorance that have become the bread and butter of the soft-spoken "can't we all be nice and not use any naughty words" camel-mannered tunic-wearing mollycoddles -- the LOT of whom coast by on as little effort, knowledge, learning, passion OR compassion has possible... or worse, learning the wrong things just because they don't know any better.
Again see bootcrap whose snake oil peddling continues to dupe nubes and rubes alike into thinking that writing two to ten times the markup and as much custom CSS as you'd have without it -- ALL whilst pissing on the very purpose of both HTML and CSS -- is somehow magically "easier". BULLCOOKIES!
The truly great programmers? For all intents and purposes they are Sith lords. The hate is swelling in you now. Give in to your anger. Use your aggressive feelings, boy. Let the hate flow through you!
... and if you don't, well, let's just say you will pay the price for your lack of vision.
That or take Blade's advice. Use it. Use it... USE IT!!!
You get a little angry, and leverage it you'll be shooting though your code like crap through a goose, like shit through a tin horn. Someone else saddles you with bekaptah nonsense, you give it back to them double-dirty. Might not sound nice to some little old ladies at an afternoon tea-party, but it will help people to remember.
As to the types of statements I make... well, by Joe, I just get caught up in my own eloquence.
... and as our blessed St. George told us, worship the sun, but pray to Joe Pesci.
-- edit -- Oh and listening to Slayer or Cannibal Corpse can help keep you in the right mindset.
I get frustrated.
I have had a log out issue that prevents users from logging out for 1 year now. The problem is that it connected to a SAML2 service and I can't figure out at all why I can't kill the remote SAML2 session.
Richard Bilton
Front end ecommerce developer
Tbh I wouldn't have let myself get to day 4 on a bug.
1) is there a better way to solve the problem / have I gone down the wrong path and caused this issue myself?
2) is there no one else in the company that can help me go through the issue and come up with a solution?
3) hire a freelancer to fix the issue for me, review their solution and learn from it..
but there will be many choice words within the first few hours of trying to fix a bug never mind day 4...
:)