Programming isn’t a spectator sport.
But wait until the proverbial excrement hits the fan!
Then everyone who believes he has a stake or interest in the emergency is summoned by some arcane force.
Then they all gather around the guy who needs to fix the problem, and they swarm around him like flies on a fresh cow turd!
Unfortunately, it’s nothing like the epic “hacking scenes” from a movie.
There’s only stress.
Software and systems emergencies remind me of the times when you needed to find a plumber over the weekend.
While the plumber is fixing the leak or declogging the sewerage you’ll also see everyone standing around.
They’re not watching in awe though, but more out of morbid interest— Secretly being glad they don’t need to do the job but also irritated by having to pay for someone to invade their sanctum on a weekend.
I think many white-collar office emergencies fall in the category where management is just relieved someone pitched up to find an accounting error, incorrect booking or whatever other glitch showed up on a monitoring screen.
Yeah, alright then— Perhaps you’ll get the courtesy nod of approval if you fixed the error timeously.
Just don’t think for a minute there’s a medal in it for you.
After having worked a dozen jobs I very seldom received more than a cursory “thanks dude” for fixing “leaks.”
It seems that inadvertently the boss easily perceives a glitch as an inconvenience.
Perhaps he was lounging by the pool when the crisis was reported.
On some level, he equates the problem with you, because irrespective of whether you caused it, he needs someone to personify the irritation he feels at losing some leisure time!
If you’re working for a cool boss he might appreciate your efforts, just don’t assume it will improve his happiness, well-being or anything for that matter.
Getting you to do the job—That’s the job for him, and you’re part of the job.