The Itch That Has No Scratch

Side projects begin as solutions to problems that don’t actually exist. You realize this about halfway through the third rewrite, when someone asks what you’re building and you have to pause. “Well,” you say, “it’s like but for homelabs or a better way to track…” You trail off because even you barely believe the problem description anymore.

Never mind that the existing solutions work fine. Never mind that nobody asked for this thing. Never mind that you have a dozen unfinished projects scattered across your hard drive like abandoned cities. You keep working because there’s a particular satisfaction that comes from building something that exists only because you willed it into being.

The Unoptimization Problem

Professional software development teaches you to optimize for the user, the business, the metrics. But side projects thrive in the space between “this works” and “this is good enough.” They’re optimized for a single human: the person typing at the keyboard.

This creates a strange dynamic. When you finally show your side project to someone, they squint. “Why didn’t you just use popular existing tool?” The question stings because you know they’re right. And yet, showing them the thing you made — explaining the quirks, the compromises, the little flourishes that make it uniquely yours — fills you with a quiet pride that no corporate achievement ever has.

The Museum of Useless Things

Your homelab is a museum of these useless things. Not “useless” in the trivial sense, but useless in the sense that they serve no purpose beyond their existence. Each service was built to scratch an itch you invented.

There’s the RSS reader you rewrote because the interface felt wrong. The backup system you cobbled together from shell scripts when you could have used any of a dozen pre-built solutions. The dashboard that exists entirely to display information you already knew.

These projects aren’t about efficiency. They’re about the practice of making things. The recursive joy of building tools that help you build tools. The gentle discipline of finishing something, of seeing it through to running code.

Why We Keep Starting New Ones

The psychology is subtle but real. Side projects are playgrounds where we can be simultaneously incompetent and brilliant. We can ignore best practices and immediately regret it. We can embrace best practices and wonder why we bothered. The stakes are perfectly calibrated to keep us learning without breaking us.

Each abandoned project becomes a monument to what we learned. Each finished one becomes a small proof that we can start and finish. The ratio doesn’t matter — the act of creation does.

So we keep starting new projects with names like “yet another” and “better than the alternative.” We keep building for an audience of one, knowing that the real reward isn’t using the thing, but making it.

The Quiet Rebellion

In a world that demands we justify every hour of work, side projects are a quiet rebellion. They declare that not everything worth doing needs a business case. That making things for their own sake is a valid way to spend time.

Your homelab, your little museum of beautiful uselessness, stands as proof that curiosity is its own rationale.