Building in public means shipping your work before it’s perfect, writing about what you’re learning in real time, and letting strangers on the internet tell you when you’re wrong.
The Case for Transparency
Most companies treat their internal work as proprietary by default. We think that’s backwards. Open development creates a feedback loop that closed development can’t match.
What We’ve Learned
Working in public has forced us to write better documentation, think more carefully about API design, and be honest about what’s not working.
It’s uncomfortable. That’s the point.