Building in Public

There’s something powerful about showing your work as it happens. Not the polished case study after the fact, but the messy middle — the decisions, the dead ends, the moments where you almost gave up.

I’ve started sharing more of my process publicly. Not because I think every decision I make is interesting, but because the act of explaining forces clarity. When you know someone might read your reasoning, you reason better.

What building in public means to me

It’s not about Twitter threads or engagement metrics. It’s about leaving a trail. When I build something, I want to document the why alongside the what. Future me will thank present me, and maybe someone else will find it useful too.

The uncomfortable part

Sharing unfinished work feels vulnerable. The code isn’t clean yet. The design isn’t refined. But that’s exactly the point — the interesting stuff happens before things are polished.

I’d rather ship something rough and real than wait for perfect.