Remember when building a website meant you could shout into the void and actually be heard? Before algorithms decided who saw your words? I do. That’s why I spent three months building a static site generator from scratch. I wrote custom CSS, optimized every byte, and even hand-rolled an RSS feed. And then I looked at my empty blog and realized I’d fallen into the most expensive trap in tech.
The most expensive thing you can build is a tool you’ll never use to create.
I’m not alone. Every week on Hacker News, another developer unveils a meticulously crafted personal site—coded in Rust, hosted on a Raspberry Pi, deployed via a custom CI/CD pipeline. The comments applaud the architecture. The author beams. And then the site is never updated again. We’ve confused the act of building with the act of being a creator.
Let’s call it what it is: the maker’s trap. You want control over your digital presence, so you build your own platform. But control is an illusion we pay for with our time. Every hour you spend tweaking your static site generator is an hour you didn’t spend writing. Every line of code is a line between you and your audience.
Control is an illusion we pay for with our time.
I saw a friend spend 400 hours on a custom CMS. His site had three posts. The comments section was a masterpiece of moderation tools. The analytics dashboard was stunning. But nobody was reading. He had built a cathedral for a congregation that never came.
This isn’t an argument against owning your platform. It’s an argument against mistaking infrastructure for voice. The early web was magical because people wrote badly but wrote often. GeoCities pages were ugly, but they were alive. Today we obsess over perfect markdown rendering and forget that words matter more than typography.
The best personal website is the one you actually write on.
So here’s the twist: the website you’re building might not be a website at all. It’s a monument to procrastination. A beautiful, optimized, perfectly-scored-on-Lighthouse monument to the one thing you’re afraid to do: publish something imperfect.
Stop building. Start writing. Use a free template. Use a subdomain. Use a piece of paper if you have to. The only thing that spreads is ideas, not architecture. The only thing that matters is the next sentence. And the one after that.
Take it from someone who wasted three months: your website is not your legacy. Your words are.
FAQ
Q: Isn't owning your platform important for digital sovereignty?
A: Yes, but not at the cost of never publishing. A simple blog on a subdomain you control is better than a perfect site with zero content. Sovereignty is about audience independence, not architectural purity.
Q: What about the indie web movement? Are you dismissing it?
A: Not at all. The indie web is noble—but it's become a fetish for tooling. The real indie web is about ideas, not infrastructure. A manually updated HTML page is more indie than a microservice-driven monolith.
Q: So should I just use Medium or Substack instead?
A: Use whatever gets you writing. But own your domain, even if it's a one-page site. The goal is to produce content, not to build a museum for your technical skills. Ship first, optimize later.