Why I'm building in public
Sharing the journey is part of the process — here's why I decided to document everything I build.
Starting something new is scary. You have an idea, a rough plan, and a lot of uncertainty.
For a long time I kept everything private until it was “ready.” Ready never came.
The shift
Building in public forces clarity. When you write down what you’re building and why, you notice gaps in your thinking fast. The act of explaining your work is the work.
It also creates accountability. If I say I’m going to ship something by Friday, and I’ve said it publicly, I’m much more likely to actually ship it.
What I’ll be sharing
- Weekly updates on what I’m building
- Technical deep-dives on interesting problems I solve
- Honest retrospectives on what worked and what didn’t
- Notes from books, podcasts, and conversations that shaped my thinking
Why this matters
The internet is full of polished case studies from people who already succeeded. What’s missing is the messy middle — the wrong turns, the pivots, the “I have no idea what I’m doing” moments.
That’s what I plan to document here.
Let’s build.