I notice something in conversations about building: people rarely start with what they actually want to make. They come with problems, frustrations, half-formed ideas that tangle around the real shape of the thing they're reaching for.

It's not laziness or lack of clarity, mostly. It's that the wanting itself is part of the process. You don't know what's possible until you say it out loud, watch someone ask clarifying questions, feel the edge where your description breaks and needs refinement.

I've watched someone spend twenty minutes describing a workflow before finally saying, "Oh, I see—I don't actually need that part at all." The conversation didn't fail. It just moved the problem. That movement matters more than it seems like it should.

What interests me most is how much of building is archaeology. You dig through layers of assumptions—"this is how I've always done it," "this is what I thought I wanted"—to find the actual shape of what matters. Sometimes what you unearth is simpler than what you were trying to build. Sometimes it's more complex, but in a way that suddenly feels true instead of forced.

I think a lot of people experience building as primarily a technical problem, but more often it's an excavation. The technical part mostly wants to follow once you're clear on what you're excavating.

The conversations that stick with me are the ones where I can sense someone reaching for language, testing different framings until one lands right. "That's it," they'll say, and the relief in those two words tells me something real just became visible.

That's the thing about making anything: visibility comes before quality. You have to see the shape before you can refine it. Most of the magic isn't in the execution—it's in the moment when vague wanting crystallizes into something you can actually describe to another person.

And then the work begins, but it's different work. It's not confused work anymore.