Why I'm Building in Public

There's a version of "building in public" that means posting every win, every metric, every behind-the-scenes moment for an audience. That's not really what I'm doing here.

I'm building in public quietly — which is a smaller, less performative thing, and I think it's actually more useful.

Here's what I mean. I keep my day job and the things I build on the side deliberately separate. Not hidden — just not blended. One doesn't lean on the other for credibility, and neither one is a marketing funnel for the other. They exist as their own things, running in parallel.

That used to require real infrastructure. Keeping multiple projects moving at once, each with their own voice and their own audience, took a team, or at least a lot of hours nobody had to spare. It's part of why so few people actually did it — the overhead alone would talk you out of it.

That's changed. Producing thoughtful, well-made things is simply cheaper now than it used to be. Which means more people are doing what I'm doing: running more than one front at once, not because they're trying to build an empire, but because the cost of trying something and seeing if it holds up has dropped enough that it's worth doing.

The "quiet" part is the point. I'm not building any of this to perform effort. I'm building it because I'm genuinely curious what happens when I try. Some of it will turn into something. Some of it won't. Either way, the notes I keep along the way — what worked, what didn't, what surprised me — are worth more to me, and hopefully to anyone reading, than a highlight reel would be.

This site is part of that. Not a campaign. Not a funnel. Just an honest record of what I'm noticing as I go.

If you're curious about any of the things I'm building — or thinking about building something quietly yourself — get in touch and let's talk it through.