Frank
Picture an old mechanic’s toolbox. The kind your grandfather kept in the garage, built like a tank, full of tools that had a specific purpose for a specific era of engine.
Some of those tools still work on modern cars. Most don’t. And here’s the uncomfortable part — the mechanic who refuses to open a new drawer is still standing in that garage, wondering why the work dried up.
That’s IT in 2025. And I’ve been that mechanic at different points in my career. I know what it looks like from the inside.
The Drawer That Kept You Employed in 2005
When I was cutting my teeth in IT, the premium skills were almost entirely about physical infrastructure and tribal knowledge. Could you build a Windows domain from scratch? Could you troubleshoot a network drop by walking the cable path through a ceiling? Did you understand RAID configurations well enough to explain why the array just failed at 2 a.m.?
Desktop support was an actual career path with real ceiling. Knowing Group Policy deeply made you indispensable. Being the person who understood the phone system, the backup solution, and the aging Exchange 5.5 server all at once made you a one-person emergency response team.
The rarest skill back then wasn’t technical at all. It was documentation. Most IT shops ran entirely on institutional memory — a single person’s brain containing the entire operational history of a company’s infrastructure. That person had enormous, unspoken job security.
Those tools weren’t wrong. They were exactly right for the era they were built for.
The Problem With Carrying Every Tool Forever
Here’s where I see people go off track — and I’ve watched this happen to smart, capable people over nearly three decades. They get exceptionally good at one layer of the stack, that layer gets commoditized or abstracted away, and instead of opening a new drawer, they double down on what already worked.
Active Directory administration is a clean example. In 2005, being the AD guy at a mid-size company made you the keeper of the keys. In 2025, AD still matters — I work with it daily — but the expectations have shifted dramatically. You’re not just managing objects anymore. You’re expected to understand hybrid identity, conditional access policies, Entra ID integration, and why a sync conflict is causing half your users to hit MFA loops they can’t explain.
The underlying knowledge still transfers. But the person who learned AD deeply and stopped there is now only doing half the job.
I have 28 years of self-taught IT experience and nearly 17 years at the same organization. I know our Exchange environment like I know the back roads between Gray and Macon. But Exchange itself has changed more in the last five years than the previous fifteen combined. The skills that matter now aren’t just the ones I built — they’re the ones I kept building on top of those.
What Actually Matters Now (And Why It’s Not What You Think)
The answer most people expect here is “learn cloud” or “learn AI.” That’s too simple. That’s like saying the mechanic’s new skill is “learn electric vehicles.” Technically true, practically useless as advice.
Here’s what I’ve actually observed as the real differentiators in 2025:
Scripting as a first language, not a last resort. PowerShell transformed how I work. Not because I’m a programmer — I’m not, and I’ll be the first to say so — but because the ability to automate repetitive tasks is now table stakes for anyone in enterprise IT. The administrators who are still doing manual bulk operations are working twice as hard for the same outcome.
Understanding the seam between on-prem and cloud. Pure on-prem expertise is narrowing. Pure cloud expertise is cheaper to outsource than most people realize. The irreplaceable skill right now is understanding how they talk to each other, where they break, and who owns what when it goes sideways. That hybrid seam is where most of the actual problems live.
Reading logs like a language. This one hasn’t changed, but the logs have gotten more complex and more distributed. The person who can trace a failed authentication through four different systems — on-prem AD, Entra ID, a cloud app, a reverse proxy — and come out the other side with a root cause is genuinely hard to replace.
Being useful to people who aren’t technical. This is the one that nobody puts on a resume and almost everyone undervalues. After 17 years in a health system, I can tell you that explaining a complex infrastructure issue to a clinical director in plain English is a different skill than fixing the issue itself. Both matter. One of them keeps you employed longer.
The One Thing That Actually Didn’t Change
Here’s what I didn’t expect when I started thinking through this: the single most durable skill across my entire career isn’t a technology. It’s the instinct to isolate variables.
When something breaks, the person who starts by asking “what changed?” instead of immediately guessing or Googling is the person who solves it faster and learns more in the process. That troubleshooting methodology works on Exchange 5.5. It works on a Kubernetes pod that won’t start. It works on a Docker container behaving badly at midnight. The mental framework transfers even when the technology doesn’t.
I started as a hardware guy who taught himself everything else. What actually made that possible wasn’t raw intelligence or access to training. It was a habit of treating unfamiliar systems as problems to be figured out rather than mysteries to be feared. I open a tab to check one thing and resurface later with 32 tabs and a new career idea — but somewhere in that chaos, the actual problem usually gets solved.
That instinct is worth more than any certification. It’s also the thing you can’t credential.
The New Drawer You Need to Open
The mechanics who are thriving right now aren’t the ones who abandoned everything they knew. They’re the ones who kept their core competency intact and added adjacent skills deliberately, not frantically.
If you’re in enterprise IT and you’re not at least functional in PowerShell, Python, or both, that’s the drawer to open first. Not because scripting will replace you if you don’t, but because it will compound everything else you already know.
The toolbox metaphor earns its keep here: you don’t throw away the wrenches. You just stop pretending they work on every engine made after 2010.
