After 5PM stop looking for a fix, start looking for a stopping point and write up some notes to review when you’re fresh again.
post
At 11:00 in the evening, there are two options for what they're dealing with. Either:
- They have made precisely no headway whatsoever in actually solving the bug, or
- They have fixed the bug, but the debugging made them go "---wait, how did that ever work in the first place?!"
If it's #1, odds are pretty good that there's a random debug step they put in at 9:08 in the morning that's screwing everything up now. If it's #2, odds are pretty good that it actually didn't work before, and now they've got to go back through the last six months of data and rectify it to fix that bug.
Ahhh just entering the phase where the bug is fixed, but everything else is broken.
The rules to remember when this is happening but before it gets that bad:
- remember your own advice
- have you tried turning it off and on again?
- have you explained the issue to the ducky?
- have you eaten?
Rule 1 is the hardest tho
More like:
11:00 in the evening: it's a simple bug, I can fix it in a few minutes
9:00 in the morning:
This is why I take a late lunch every day. Every standup I’m like “I’ll wrap up this small issue from yesterday, then move on to something bigger…”
Usually the “small issue” is finally done around 4 PM.
Usually it’s just one character that’s wrong
Bonus points if it’s failing because you spelled it right and the preexisting is misspelled.
I don't code, but I do work with a lot of really shitty proprietary software. The amount of time vendors haven't been able to fix their own shit is so high. Spent 6 hours on the phone once. Work 2.5 hours overtime for that call.
In that case though, the person helping you doesn't have the ability to solve the problem by changing code. They have to work around the bug to try to make it work for you in its broken state and report the problem to developers to fix in the next release. It's a more difficult problem to solve
And the official solution to this problem in the documentation is a library deprecated four versions of the framework and/or programming language ago.
I've had security incidents that go like this too.
...like more than a few.
I've had this experience and morning was like, "I'm gonna plan the trip of a lifetime to London and Paris and maybe Rome for a month or more."
Then in the evening I'm like, "well Vegas is a cheap flight, so if I spend a night in Vegas maybe I can go to Denver too?"
That's me right now. Just recently sent an issue report to Proton over the fact I have not been able to connect to their servers on my Linux running laptop for almost a week at this point and have given up on trying to self-disgnose and fix it on my own using what little skills I have and whatever information I could find through web searches. The worst part is how it effortlessly works perfectly on my desktop running windows 10.
However, she solved the more important issue that there was a post-it glued on top of the screen.
all 40 comments