Frank
Picture the “tech person” the industry wants you to imagine. Twenties. Hoodie. San Francisco or Seattle. Computer science degree from somewhere impressive. Startup equity. Standing at a whiteboard covered in system diagrams, probably drinking cold brew out of a vessel that costs more than my first car payment.
That image got built on purpose, and it served the people doing the building.
The reality of who actually keeps technology running in this country looks nothing like that. It looks like a 55-year-old from Gray, Georgia, troubleshooting Exchange Hybrid configurations before most of that hoodie crowd has poured their first cup of coffee.
The Mythology Was Always a Marketing Move
Tech culture didn’t stumble into that identity. It got assembled piece by piece, mostly by venture capital and media outlets that needed a clean story to sell. The genius founder myth. The “move fast and break things” philosophy. The idea that real innovation only happens inside a handful of zip codes.
That mythology always needed an implied other. The IT guys in the server room. The admins at mid-size companies in mid-size cities. The self-taught folks who learned by doing instead of studying under someone important. The ones who built their skills on necessity, not curiosity backed by a trust fund.
The mythology needed those people invisible. They complicated the story.
Spend twenty years in enterprise IT and you figure out fast that the shiniest tech isn’t always the most important tech. The systems that can’t go down, the ones where failure means actual consequences for actual people, those aren’t usually running the freshest stack. They’re running the stack somebody understood well enough to trust. That’s a different kind of knowledge than what gets celebrated at a product launch.
What “Culture” Actually Does to a Field
Here’s the extended metaphor I keep coming back to: tech culture works like a car show that only displays concept cars.
Concept cars are real. They represent genuine engineering ambition. Some of the ideas in them eventually make it into the vehicles people actually buy and drive to work. But nobody commutes in a concept car. Nobody hauls a load of feed to the farm in one. The cars doing the actual work are the ones you never see on a poster.
Tech culture, especially the version that lives on social media and conference circuits, is almost entirely concept cars. The shiny AI demos. The framework that rewrites everything you thought you knew about frontend development. The startup pitch promising to disrupt an industry that was doing fine. That stuff gets all the oxygen.
Meanwhile, the actual work, the Active Directory management, the Exchange configs, the PowerShell scripts keeping 162,000 employees’ accounts functioning on a Tuesday morning, that’s the fleet vehicle nobody photographs. It’s what the organization can’t live without, and nobody’s writing Medium posts about it.
The problem isn’t that concept cars exist. The problem is when people inside the industry start believing concept cars are the whole of what automobiles are.
The Generational Handoff Is Messier Than Anyone Wants to Admit
Gen X built a big chunk of the infrastructure that younger generations are currently “disrupting.” That’s not a complaint. That’s just history. But there’s a specific kind of cultural amnesia that happens when a field grows fast and starts worshipping newness for its own sake.
Experience gets rebranded as obsolescence. Caution gets mistaken for incompetence. The person who says “I’ve seen this pattern before and here’s how it broke last time” gets treated like a problem instead of a resource.
I’ve watched this happen inside IT shops. The new approach wins the argument not because it’s been tested, but because it’s newer. Then six months later, when something goes sideways in production at 2 AM, who do they call?
Tech culture has a short memory by design. Short memories are useful if you’re selling something new. They’re a liability if you’re trying to build something that lasts.
The people who’ve been doing this work for twenty-plus years, in places the industry never thought to look, in roles the mythology never bothered to glamorize, those people carry institutional knowledge that no amount of onboarding documentation can replace.
That knowledge doesn’t show up in a LinkedIn headline. It doesn’t get a keynote slot.
But it’s what’s keeping the lights on.
