There’s a particular kind of exhaustion that doesn’t come from doing too much. It comes from being able to do everything.

I noticed it last Tuesday at 11 PM. I had seventeen browser tabs open, each one a different way to solve the same problem: self-host a note-taking app. One tab was a Docker Compose guide for Trilium. Another was a fresh Obsidian setup with a git sync plugin. A third was a Reddit thread arguing about Joplin. A fourth was a YouTube video titled “I Built My Own Knowledge Base in Rust.” By tab twelve, I wasn’t researching anymore. I was just… scrolling through possibilities, feeling the weight of each one like a stone in my pocket.

We talk a lot about the paradox of choice in consumer culture — too many jams at the grocery store, too many streaming services, too many dating apps. But there’s a quieter, more insidious version of this problem that lives in the tech world. It’s the paradox of digital possibility, and I think it’s slowly draining the joy out of building things.

The Infinite Shelf

Here’s what makes tech different from other domains of choice: the shelf is infinite, and it restocks every morning.

When you walk into a bookstore, there are maybe ten thousand titles. That’s a lot, but it’s bounded. You can develop a sense of what’s out there. You can feel like you’ve “covered” a genre. The tech world doesn’t work that way. Every day, someone on GitHub releases a new framework, a new database, a new way to containerize your life. The feed never ends. The “what if” never stops whispering.

And the cruelest part? Most of these tools are genuinely good. That’s what makes it so hard. It’s not like choosing between a reliable Honda and a lemon. It’s like choosing between a Honda, a Tesla, a bicycle, a horse, and a really enthusiastic friend who’ll carry you on their back — and they’ll all get you where you’re going. The differences are real but subtle. The trade-offs are genuine but hard to evaluate. And so you research. And research. And research. And at some point, you realize you’ve spent four hours reading about note-taking apps and haven’t written a single note.

The Optimization Trap

I’ve started calling this the “optimization trap,” and I think it’s the defining anxiety of the modern builder.

It works like this: you set up a system — let’s say, a home media server. It works fine. Plex is running, your files are organized, everything streams smoothly. But then you read about Jellyfin being open-source. And someone mentions that you could hardware-encode with an Intel QuickSync GPU. And there’s a Docker setup that automates everything with Sonarr and Radarr. And suddenly, your perfectly functional system feels wrong. Not broken. Just… suboptimal.

So you spend a weekend migrating. The new system is objectively better in about four ways and subjectively worse in about six. But you can’t stop thinking about it. Because what if there’s something even better? What if you’re one blog post away from the perfect setup?

The optimization trap turns every finished project into a draft. Nothing is ever done because “done” isn’t a concept that exists when the possibility space is infinite.

The Loneliness of the Long-Distance Builder

Here’s the part nobody talks about: this is lonely.

When you’re caught in the optimization loop, you stop sharing your work. Because who wants to show off a media server when you know it could be better? Who wants to write a blog post about their Docker setup when they’re already planning to tear it down and rebuild with Podman? The infinite shelf doesn’t just drain your time — it drains your confidence. It makes everything you’ve built feel provisional, temporary, embarrassing.

I’ve talked to so many people in the self-hosting community who have incredible setups but never talk about them. Not because they’re secretive, but because they’re already three migrations ahead in their heads. They can’t enjoy what they have because they’re too busy imagining what they could have instead.

There’s a special kind of loneliness in being surrounded by tools and feeling like you’re using the wrong ones.

What the Amish Know That We Don’t

I’m not actually going to suggest we all become Amish. But there’s a concept in Amish culture called Ordnung — a set of unwritten rules about what technology is acceptable and what isn’t. The key insight isn’t that they reject technology. It’s that they choose deliberately and then stop choosing.

Once the community decides that a particular technology is acceptable, that’s it. You don’t spend your life wondering if there’s a better horse breed. You don’t lie awake at night reading forums about whether a different plow would increase your yield by 12%. You make a choice, you commit, and you get on with the business of living.

I think we need a personal Ordnung for our digital lives. Not a rigid set of rules, but a conscious decision to say: “This is good enough. I’m going to use it, enjoy it, and stop looking for alternatives.”

Good Enough Is a Radical Act

In a culture that worships optimization, choosing “good enough” feels almost transgressive. It’s an admission that you’re not on the cutting edge. That you’ve stopped chasing the perfect setup. That you’d rather spend your Saturday using your media server than rebuilding it.

But I’d argue it’s the most important skill you can develop as a builder. Not Docker. Not Kubernetes. Not the ability to configure Nginx from memory. The ability to say: “This works. I’m done. Let me go do something that matters.”

Because here’s the secret that the infinite shelf doesn’t want you to know: the tool was never the point. The point was always what you built with it. The blog post you wanted to write. The photo album you wanted to share. The game you wanted to play with your friends. The tool is just the door. At some point, you have to stop admiring the door and walk through it.

A Small Manifesto

So here’s my attempt at a personal Ordnung, offered not as a prescription but as a starting point:

• Pick one thing and use it for a year. No migrations. No “evaluating alternatives.” Just use it.
• When you catch yourself researching instead of building, close the tab. The research is not the work. The research is procrastination wearing a lab coat.
• Share your setup, even if it’s imperfect. Someone out there needs to hear that your “good enough” solution works. They need permission to stop optimizing too.
• Remember that the best system is the one you actually use. Not the one with the most GitHub stars. Not the one that would impress Hacker News. The one that’s running right now, serving your needs, quietly doing its job.

The Joy on the Other Side

Last night, I closed fifteen of those seventeen tabs. I picked Trilium for my notes — not because it’s the best, but because it’s good and I’m tired of thinking about it. I wrote three pages of notes for a project I’ve been putting off for months. The notes aren’t in the optimal format. The sync isn’t perfect. The search is a little slow.

And it felt wonderful.

Not because I found the perfect tool. Because I stopped looking for it. Because I remembered that the whole point of technology is to get out of the way and let you do the thing you actually care about.

The infinite shelf will always be there. The new frameworks will keep coming. The “what ifs” will never stop whispering. But you don’t have to listen. You can close the tab, open the editor, and start building something that matters — with whatever tools you have, right now, today.

Good enough is good enough. And that’s enough.