Why I Have a Personal Blog.

I’ve been building websites for over a decade, usually for other people, and more recently for myself.

Most new projects start the same way in my head: I’ll build X product, then I’ll write Y articles, then people will show up.

Reality is more like this: I build the product, I try to write the articles, and the writing starts feeling constrained. Everything has to align with “the brand” or “the product goals,” and suddenly I’m filtering my thoughts before I even get them onto the page. The result is predictable. Not much gets written.

The truth is my interests don’t stack neatly into a single company mission statement.

If I’m writing about crypto, it fits on buyhodlsell.com. If I’m writing about lifestyle, productivity, or money, it fits on existplan.com. But when I’m writing about building those brands (what’s working, what isn’t, what I’m learning as I go), where does that go?

So this is the personal layer. Not a funnel. Not a content strategy. Just a place to think in public.

Also, as a web developer, it’s really easy to fall into the trap of “I’ll just spin up a new site for this topic.” Then I spend a week perfecting the layout and the pipeline… and I don’t write a single paragraph. I’ve done that enough times to recognize it as a distraction with a nice UI.

Being my own Employee

I used to write daily. I want to get back to that.

Here’s the trap I fall into when I mix “writing” with “building brands”: I start treating writing as a requirement of the business.

If I force myself to publish for my brands constantly, I’ll end up spending my creative energy feeding the machine, while neglecting the parts that actually grow the machine: building, selling, shipping, making deals, finding collaborators, recruiting smarter people than me.

I don’t want to become my own content employee.

Instead, I want a home base. When something I write fits one of the other sites, great. I’ll cross-post it. But I need a place where the only alignment is with me.

The Exposure Case

Over the years I’ve written in a lot of places: random blogs, guest posts, forums, little side projects. And if I’m honest, most of it is gone.

Accounts get forgotten. Platforms shut down. Domains expire. “I should save that somewhere” turns into “it’s 404 now.”

And when your writing disappears, you lose more than words. You lose the trail. Credibility is built over time by showing your work and letting people see your name attached to it, again and again.

No one can be a thought leader on localhost.

This is my attempt at keeping my own archive: a place to collect ideas, lessons, and the occasional tangent so it doesn’t all evaporate.

Leaders Write

Not all leaders write, but the ones I’ve learned the most from usually do.

As a developer, it’s possible to avoid writing for a long time. You can ship code, pair with someone, hop on a call, and keep things moving.

But as you move into leadership (making decisions, aligning people, setting direction), communication becomes the job. And it’s not scalable to explain every idea to every person one-on-one.

Writing scales clarity.

Also, writing forces honesty. It’s easy to hand wave in conversation. It’s harder to hide fuzzy thinking on a page.

Topics You'll Find Here

• Building tech products in the modern age
• Finance and approaches to living well
• Thoughts on society
• Coding, design and architecture decisions
• Tangents, because this isn't a brand.

I don’t have a content calendar. I’m not trying to hit a posting cadence. I just want to share what I’m learning with people who might find it useful (or at least interesting).

If that sounds interesting, stick around. And if you have thoughts on something I write, reach out. The best ideas come from conversations.

---

Let’s see where this goes… or if it becomes another blog with two posts forever. Also fair.