What I see is an inexperienced developer who instead of systematically debugging the issue keeps trying random stuff hoping that it will somehow work.
What I see is the developer who's left after multiple rounds of cost cutting layoffs and subsequent exodus of anyone qualified, that knows they are only there because they are willing to work for the least amount of money, and are willing to endure abuse from their sadistic manager, not knowing how to systematically debug the mountain of accumulated issues, and keeps trying random stuff hoping that anything will somehow work.
Eh, that moment when you get a different error message tho ;)
That is what hope and dreams are made of
Shit, did I forget to close my blinds again!?
Back in my day we called that Programming by Coincidence.
Scattershot troubleshooting is the most frustrating way of looking for solutions, can't imagine why that would be any sane persons first option, or even before asking for another set of eyes.
Not really relevant to your comment, just that I've seen that myself a few times and it always frustrates me. Especially if the person does multiple changes so it's hard to find the origin of any new issues
Tell me about it, all the juniors were doing it at my old job, and I was usually the one tasked with fixing their shit. And since we basically didn't do any form of mentoring (including code reviews) it was such a pain in the ass to get them to change their ways
Tell me about it, when the roles are reversed and nor the manager ex-dev nor the older dev care about good programming practices it's a far west where the junior desperately tries to become the dictator of a ruleless country
But if you do it fast enough, you can call it Machine Learning
Immediately onto the lap.
Christ almighty, this is perfect. Literally my life for the past twenty years, except the I start by assuming they did something dumb, so I would have checked the lid first. Then promptly they spill it unto their lap and I have to clean it.
"whatever you do don't forget to check the big tab is on the left and the little tab is on the right, even if you get it backwards it won't close as a safety precaution."
Gets call of machine not working in another country, sends out consultant.
Big tab is on the right, little tab is on the left and the entire tray has been forced into position because "it wasn't closing properly so we had to apply a lot of force"
Professionals with confidence are the absolute worst, I tell ever consultant or technician that comes into my lab "I'll be in the corner if you need me to grab you any supplies or coffee, do you mind if I ask questions as you go so I can have a better understanding of what's going on with this magical box". I like to think they appreciate me.
The real question is, what the hell are they eating?
They almost look like big flans.
Post funny things about programming here! (Or just rant about your favourite programming language.)