There is a version of building that most developers default to. Work quietly. Ship when ready. Tell...
There is a version of building that most developers default to.
Work quietly. Ship when ready. Tell people when it is done.
It feels professional. Disciplined. Like you are protecting your work until it is worthy of being seen.
The problem: most things never get "ready." And most developers who build in silence spend far longer than they need to before finding out if anyone wants what they are making.
Building in public is the opposite of that.
To read the original version, click here. Stop building in public. Here's why. I started building...
I've been building in private for too long. Two months of solo development, zero public commits, and...
For the past year, I've been building a Web3 project called BOINKO. Along the way I've learned...
I have been quieter than usual over the past few months. Although I enjoy building in public, some...
Give people a free, working result instead of promising one. It earns trust faster than any claim, costs little if you build it…
I built more tools than I ever shipped, and called it progress. Four honest mistakes that kept me busy, sharp, and completely…
