TUESDAY, MAY 5, 2026VOL. XXVI · NO. 17
Cars

Reliable Used to Mean Something Mechanical. Now It Means the Software Hasn't Quit Yet.

A writer at Hagerty Media named the thing nobody in a showroom will say out loud.

By Chasing Seconds · APRIL 30, 20264 minute read

Photo · Hagerty Media

The Battery That Held

Picture a morning in 1952. Cold garage, maybe. A driver turns a key, and what happens next is almost embarrassingly simple: chemistry holds a charge, contacts conduct current, copper loops respond to magnetism. A writer at Hagerty Media opens with exactly this image — not with nostalgia, but with precision. Because the point of the image isn't warmth. It's contrast. In 1952, you could trace every link in the chain from your hand to the engine turning over. The system was legible. You could understand it if you tried, and fix it if you understood it.

Now consider what happens when a modern car doesn't start. Where do you even begin?

That's the question Hagerty Media has decided to stake out in plain language, and I find the existence of that piece more interesting than any single argument inside it. Because this isn't an obscure forum complaint. This isn't someone who restores Alfa Romeos raging into the void. This is automotive media — enthusiast media — saying, in measured but unambiguous terms, that the industry has been engineering reliability out of its own product. That the complexity accumulating under modern hoods and behind modern dashboards isn't all progress. That some of it is, structurally, fragility with better marketing.

Someone had to say it. The question worth sitting with is why now, and what it costs us that it took this long.

Complexity as a Feature Nobody Ordered

There's a version of this conversation that sounds like old-man-yells-at-cloud, and I want to avoid that version. New cars are genuinely remarkable in ways that matter. The safety engineering alone has saved lives that simple mechanical systems would have ended. Nobody serious is arguing for a return to drum brakes on wet mountain roads.

But the Hagerty piece isn't making that argument either. What it's doing is something more uncomfortable: drawing a line between complexity that serves the driver and complexity that serves the manufacturer's business model. Between redundancy that makes a car safer and interdependency that makes a car harder to fix, more expensive to maintain, and shorter-lived as a result.

The confession at the center of the piece — and it is a confession, even if the industry didn't write it — is that reliability has been quietly redefined. It used to mean the car would run for a long time without significant intervention. Now it increasingly means the car will run fine until a specific module fails, at which point the repair cost approaches the car's value and the practical answer is replacement. That's not reliability. That's a subscription to a machine that hasn't told you the terms.

I keep coming back to a simple question the piece raises without quite asking directly: who does the complexity serve? When a system requires specialized diagnostic tools that only dealers possess, when a component can't be replaced without recalibrating five others, when the failure of a sensor that costs eleven dollars bricks a car worth thirty thousand — at some point, you have to reckon with the fact that this architecture benefits someone, and it isn't the person making the monthly payment.

The Moment Planned Obsolescence Stopped Pretending

Planned obsolescence used to be a theory people argued about. Consumer advocates made the case; manufacturers denied it, or dressed it up as innovation cycles. The new model is better, they said. And sometimes that was even true.

What feels different now — and what the Hagerty piece gestures toward without quite using this language — is that the pretense is getting harder to maintain. When you engineer a car with enough electronic interdependency that a single failed module can strand it, when you build systems that only your own technicians can diagnose, when you make components that cannot be sourced independently — you have built obsolescence into the architecture itself. You've made the car's longevity a business decision, not an engineering achievement.

This is the moment I think the piece is actually marking. Not a new development so much as a threshold being crossed where the industry's own enthusiast press can no longer look away from the trajectory.

And here's what I find genuinely unnerving about that: the people who will feel this first and hardest aren't the ones buying new cars every three years on a lease. It's the person who buys a five-year-old car because it's what they can afford, who needs it to run for another eight years, who does not have a dealer relationship and cannot absorb a four-figure repair bill to replace a module that controls something a carburetor used to handle mechanically for forty years without a software update.

Reliability was never just a technical specification. It was always partly a promise about who got to keep the car running and who got to decide when it was done. A writer at Hagerty Media just put that promise under a microscope. What they found there should make you think about whatever you're driving — and for how long it will let you.

End — Filed from the desk