Building in Public is a Privilege
Not everyone can share their work freely. Recognizing that changes how I think about the movement.
The "build in public" movement assumes you have the safety to share your numbers, your failures, your revenue. That is not true for everyone.
If you are on a work visa, sharing a side project's revenue could complicate your immigration status. If you work for a company with strict IP clauses, sharing code could get you fired. If you live in a country where success attracts the wrong kind of attention, showing revenue screenshots is a bad idea.
I have friends in Bangalore who build incredible side projects but never share them publicly. Not because they are shy, but because their employer's contract says anything built on their time (including weekends, which is absurd) belongs to the company.
The people who build in public most loudly tend to be:
- Based in the US or Europe
- Self-employed or in a flexible job
- Not worried about visa status
- In a financial position where failure is uncomfortable but not catastrophic
This is not a criticism of building in public. I think it is wonderful when it works. But I have noticed the movement sometimes looks down on people who keep their projects private, as if they are hiding something or lack confidence.
Sometimes, they are just being practical.
I build in semi-public. I share ideas freely (hence this blog), but I keep the specifics of what I am actually building a bit closer to the chest. This is a choice shaped by circumstances, not personality.
- Mohan
- Mohan