Nothing says ‘career peak’ like standing in a drafty hallway while the VP of Marketing shakes a dead iPad at you, asking why it won’t connect to the hotel Wi-Fi in Des Moines. I was in the middle of diagnosing a latent race condition in our production cluster-a problem that could potentially cost the company $49,999 an hour in lost transactions-but there I was, staring at a screen that was simply in Airplane Mode. I fixed it with a thumb swipe, and she smiled as if I’d performed a minor exorcism. ‘You’re a lifesaver,’ she said, already walking away before I could explain that my time was technically billed at a rate that made that 9-second interaction more expensive than the device itself.

We’ve reached a point where ‘technical skill’ is viewed as a singular, monolithic trait, like being tall or having blue eyes. If you can configure a database, surely you can fix the CEO’s smart toaster. If you can write a deployment script, why can’t you make the printer in the breakroom stop making that ‘grinding’ noise?

The Bridge Builder and the Nightstand

It’s a bizarre conflation of vastly different disciplines. It’s like asking a structural engineer who builds suspension bridges to come over and help you assemble an IKEA nightstand because ‘they’re both just building things, right?’ The bridge builder might actually be terrible at IKEA furniture. In fact, they might hate it. But in the corporate ecosystem, the person who knows what a ‘packet’ is suddenly becomes the custodian of everything that requires a battery.

I’ve got that damn ‘Mr. Brightside’ song stuck in my head today. It’s been looping since 9:49 AM. *Coming out of my cage and I’ve been doing just fine.* It’s a rhythmic distraction that matches the frantic tapping of my fingers as I try to get back into a flow state that was shattered by a request to ‘look at the coffee machine’ because it has a digital display and therefore falls under my jurisdiction. I’m not doing just fine, Brandon. I’m trying to prevent a data breach, and the coffee machine is just out of beans.

Take my friend Casey G., a safety compliance auditor. You’d think a guy whose job is literally to ensure people don’t die in industrial accidents would be exempt from the ‘can you look at my laptop’ tax. But no. Casey G. was once in the middle of a high-stakes audit-checking 29 separate points of failure on a pressurized system-when a floor manager cornered him. The manager didn’t want to talk about the emergency shut-off valves. He wanted to know why his Excel formulas weren’t auto-calculating.

Casey G., being a fundamentally decent human who suffers from the curse of knowing things, spent 19 minutes fixing a broken VLOOKUP while a potentially explosive valve sat uninspected ten feet away. He told me later that he felt a weird sense of guilt, not for the valve, but for actually fixing the spreadsheet. He’d validated the manager’s belief that ‘the safety guy’ is also ‘the computer guy.’

The Pride Tax and Devaluation

We do this to ourselves, too. I’ll admit it. I have a hard time saying ‘I don’t know’ when it comes to technology, even when I genuinely don’t know. I’ve spent 59 minutes Googling how to fix a proprietary driver for a peripheral I don’t even own, just to prove that I can. It’s a pride thing. We want to be the ones with the answers. But every time we fix a personal device for a superior, we are devaluing the 19,000 hours we spent learning the actual architecture of our systems. We are training the organization to see us as a commodity rather than an asset.

When we treat technical talent as a universal janitorial service, we create a massive bottleneck. Imagine a developer who is responsible for the integrity of an entire cloud infrastructure. They are deep in the weeds of security protocols, ensuring that the windows server 2019 rds device cal counts are accurate and that the remote desktop environment isn’t going to collapse under the weight of 499 concurrent users on a Monday morning. This is high-level, high-stress work that requires intense focus. Now, interrupt that person because the VP’s daughter’s Minecraft server is lagging. The context switch alone takes about 29 minutes of recovery time. The mental overhead of shifting from RDS licensing logic to ‘why is Minecraft slow’ is enough to induce a localized stroke.

I once made the mistake of fixing a monitor for a guy in HR. It wasn’t even broken; the cable was loose. For the next 9 months, I was the only person he would call for anything. He’d bypass the ticket system entirely-a system I helped build to prevent exactly this-and Slack me directly with things like ‘The internet feels heavy today.’ What does that even mean? I don’t know, but because I’d fixed his monitor once, I was now his personal concierge for the entire World Wide Web. I eventually had to lie and say I’d developed a sudden, acute allergy to HDMI cables just to get him to stop. It was a pathetic lie, and I think he knew it, but it worked.

The Shaman and the Burden of Knowledge

I remember an old server room we had back in ’09. It was a mess of tangled Cat5 cables that looked like a plate of blue spaghetti. Everyone stayed away from it. It was the forbidden zone. I loved it. In that room, I wasn’t the guy who fixed printers. I was the king of the spaghetti. I knew where every single one of those 89 cables went. But the moment I stepped out into the fluorescent light of the office, I was just the guy who knew how to make the ‘Save’ button work in Word. It’s a jarring shift in identity.

We need to start setting boundaries, but the problem is that the ‘helpful tech’ persona is baked into our professional DNA. We are solvers by nature. If we see a puzzle, we want to solve it. If we see a broken system, we want to optimize it. This is great for our actual jobs, but it’s a disaster for our work-life balance and our perceived value within a company. If you spend 49% of your day doing tasks that a teenager could do, don’t be surprised when the company thinks your 6-figure salary is a bit steep during the next budget review. They don’t see the database optimization; they see the guy who fiddled with the TV remote for the conference room.

Casey G. once told me that he started carrying a clipboard and looking ‘aggressively busy’ even when he was just walking to get water. He found that if he looked like he was in the middle of a life-or-death calculation, people were 79% less likely to ask him about their iPhone updates. It’s a survival tactic. We shouldn’t have to resort to mimesis just to do our jobs, but here we are.

Protecting the Architect: Defining Boundaries

I’m still hummimg that song. *But she’s touching his chest now / He takes off her dress now / Let me go.* The lyrics don’t even apply to my life, but the driving beat keeps me moving through these tickets. I have 19 tickets in the queue. 9 of them are legitimate infrastructure issues. 10 of them are ‘user error’ disguised as technical catastrophes. I’ll solve them all, because that’s what I do. I’ll be the janitor and the architect, the shaman and the engineer. But don’t expect me to be happy about the smart toaster.

So, the next time someone asks you to fix something that plugs into a wall just because you’re ‘good with computers,’ take a breath. Think about the race condition. Think about the database. Think about Casey G. and the valve. Then, politely, firmly, tell them to try turning it off and on again. And if that doesn’t work? Well, I hear there are some great tutorials on YouTube for that.

Is it possible that we’ve enabled this behavior for too long? Probably. Is it too late to change the culture? Maybe not. But it starts with acknowledging that our time has a specific, high-level purpose. We are not just the people who make the ‘magic’ happen; we are the ones who build the stage, wire the lights, and keep the theater from burning down. It’s time we started acting like it.