skip to content
← home

why i build in public

sharing the process is scarier than sharing the result. that's exactly why it works.

1 min readSeptember 20, 2025

sharing the process is scarier than sharing the result. that's exactly why it works.

when you share a finished product, people judge the product. when you share the process, people judge you. your thinking, your mistakes, your taste. it feels vulnerable because it is.

why it works anyway

building in public creates accountability. when you tell people you're working on something, you actually have to work on it. the social pressure is real and it's useful.

it also attracts the right people. the folks who follow your process — who care about how you think, not just what you ship — are exactly the people you want in your orbit. future collaborators, users, investors.

how i do it

i don't livestream my coding sessions or tweet every commit. that's performance, not building in public. instead, i write about what i'm learning, share design decisions and the reasoning behind them, and occasionally show something half-finished to get feedback.

the key is being honest about what's working and what isn't. nobody learns from success stories. we learn from the messy middle.