A senior infra dev gets pulled from a critical server migration to fix a VIP's printer. The twist? It was turned off. Hilarious Reddit IT tales and lessons.
You’re neck-deep in a critical server migration, and suddenly you get yanked away to fix a... printer. Welcome to corporate IT, folks, where logic goes to die.
Our OP is a Senior Infra & Ops guy. He's actively dodging bullets trying to keep the entire server estate from catching fire during a massive restructure project. (Probably using his Free $300 to test VPS on Vultr to spin up some backup instances and pray).
Out of nowhere, an ultra-urgent, VIP-back-channeled ticket drops. An exec emailed the CIO, who yelled at the Head of IT, who yelled at Ops. The crisis? The VIP's personal printer is down. Unacceptable!
Because OP is the "get shit done" guy, he becomes the dumping ground. He sets up a Friday 3 PM appointment, packs his bag like he's going to war, and drives to the remote site.
Surprise! The VIP had already left for the weekend at 9 AM. OP gets a spare key from the staff, walks in, and tests the printer. Nothing happens. Why? IT. WAS. TURNED. OFF.
Weeks of corporate politics, escalating emails, and wasted time... because a grown adult C-level exec couldn't press a power button. OP's only solace? Petty revenge. He stole a gummy worm from the VIP's desk. It was chewy, but tasted like absolute victory.
Reddit naturally lost its mind over this classic Layer 8 issue. Here’s how the community weighed in:
The Chaotic Evil Approach: One veteran advised leaving it off. Tell the boss it's fixed. When the exec rages on Monday, act surprised: "I turned it off after testing because I assumed you were saving power! Good job, sir!" Follow up by sending a highly detailed, 10-page manual on how to press the power button, complete with millimeter measurements for button depression.
The Courtroom Drama: Another IT wizard shared a time he fixed a projector in a packed, high-profile courtroom trial by simply... turning it on. When the embarrassed judge asked what he did, he bluntly replied, "I turned it on" and walked out. His boss later told him to make up a better excuse next time. The community's suggestion for a better answer? "An electron cascade interruption event was resolved by means of creating a suitable physical carrier link." Boom. Instant corporate promotion.
The 'Iconic' Fix: One user recalled their favorite ticket ever:
Look, whether you're a junior dev, a sysadmin, or a senior wizard, you will eventually face the dreaded user error.
The Golden Rule of IT: Always check Layer 1 first. Is it plugged in? Is it turned on? Did a rat chew the ethernet cable? Don't go debugging the network stack, checking DNS (it's always DNS, except when it's not), or reading logs if the damn thing has no power.
Also, learn the fine art of corporate speak. Knowing how to say "you forgot to turn it on" using technobabble without making a C-level exec feel like a toddler is a highly paid soft skill. It keeps the paychecks rolling in and the drama out.
Source: Reddit
