There’s a particular sound I’m thinking of. It’s the sound of a server rack humming in a closet at 3 AM. It’s the sound of a 2014 ThinkPad booting up for the thousandth time, fan whirring like a small helicopter, because you refused to throw it out. It’s the sound of a Raspberry Pi running a home automation stack that everyone told you to replace with a commercial solution.

I love that sound.

Not in a nostalgic way, exactly. Not in a “things were better back then” way. More like a deep, quiet appreciation for the stubborn refusal to give up on something that still works.

The Cult of the New

We live in an economy built on replacement. Your phone is designed to slow down after two years. Your laptop’s battery is glued in. Your smart light bulb has a chip inside it that will stop receiving updates on a date chosen by a product manager who’s already moved on to the next thing.

Planned obsolescence isn’t just a business strategy. It’s a philosophy. It says: new is better, old is broken, and you should always be upgrading.

I reject that philosophy. Not entirely, not dogmatically. But in a quiet, persistent way.

Why I Still Run a 2012 Server

My homelab runs on hardware that would make a sysadmin laugh. A Dell OptiPlex from 2012. A Raspberry Pi 3B that’s been hosting my internal DNS since 2018. A WD My Cloud NAS that I bought used and immediately flashed with open-source firmware because the stock software was spyware in a pretty box.

None of this hardware is impressive. None of it benchmarks well. The OptiPlex has a spinning hard drive that takes forty seconds to boot. The Pi 3B struggles with anything heavier than a lightweight web server.

But here’s the thing: they work. They’ve been working for years. And every time I think about replacing them, I ask myself: what problem would that solve?

The answer, almost always, is: no actual problem. Just a feeling that I should have something newer.

Maintenance as Meditation

There’s something meditative about maintaining old systems. Updating packages on a server that’s been running for three years. Clogging dust out of a laptop fan. Replacing a thermal paste application that’s finally gone dry.

These aren’t glamorous tasks. They’re not the kind of thing you post on social media. But they teach you something that buying new gear never will: you learn the shape of your tools.

When you’ve maintained the same system for years, you know its quirks. You know which log file to check first when something goes wrong. You know the sound the hard drive makes versus the sound the fan makes versus the sound that means “please plug in the power cable, you forgot again.”

That knowledge is embodied. It lives in your fingers. It can’t be replicated by a YouTube tutorial.

The Environmental Argument (Briefly)

I don’t want to preach, but it’s worth stating plainly: keeping old hardware running is one of the most effective things you can do for the environment.

A new laptop represents roughly 300-400 kg of CO2 emissions in manufacturing. That’s before you factor in shipping, packaging, and the e-waste generated by the old machine you’re replacing.

Every year you extend the life of a device is a year of avoided emissions. Your old ThinkPad isn’t just a nostalgia project. It’s a climate action.

The Aesthetics of Patches

There’s a Japanese concept called kintsugi—the art of repairing broken pottery with gold. The idea is that the repair doesn’t hide the damage; it celebrates it. The cracks become part of the object’s history, made visible and even beautiful.

I think about kintsugi when I look at my homelab. The Pi with the cracked case and the zip-tie repair. The server with the fan that’s been replaced twice. The network switch with the port that stopped working, so I just moved everything down by one. The Nginx config file that’s been patched so many times it looks like a quilt.

These aren’t signs of failure. They’re signs of persistence.

A Note on Security

I should be honest here: keeping old systems running does have real risks. Unsupported software gets vulnerabilities. Old kernels miss security patches. Running an old version of anything connected to the internet is a calculated risk.

That’s why maintenance isn’t just about keeping things running as-is. It’s about staying on top of updates, even for software that long ago stopped being fashionable. It’s about firewall rules and network segmentation and refusing to expose your 2014 file server directly to the internet.

The key is intentionality. I run this old hardware because I’ve chosen to, with full awareness of the trade-offs. That’s different from ignoring the problem. That’s different from laziness. That’s stewardship.

The Quiet Satisfaction

There’s a satisfaction in keeping things alive that I think our throwaway culture has almost forgotten.

It’s not the thrill of unboxing something new. It’s not the dopamine hit of a purchase. It’s quieter than that. It’s the satisfaction of a system that’s been running for 1,000 days straight. It’s the knowledge that your setup works because you understand it, not because someone else set it up for you and you’re afraid to touch it.

It’s the hum of a server in the closet at 3 AM. Still going. Still yours.

Don’t let anyone tell you that new is the only way.