Hacker News new | past | comments | ask | show | jobs | submit login

Building in public comes down to a few core things: marketing your product, staying sane, and getting noticed. It’s a way to get people talking about what you’re building before it’s even done. The journey itself becomes the story, pulling in an audience that feels connected to your work.

For a lot of solo founders, though, it’s not just about visibility. It’s about support. Building something alone can be isolating, and sharing your progress becomes a way to stay connected, even when you’re grinding away in a room by yourself. The openness keeps you grounded and helps ward off the burnout that comes with long stretches of isolation.

It also puts you on the radar of other entrepreneurs and investors. They see what you’re up to and can offer feedback, partnerships, or even funding without you having to chase them down. You’re essentially creating a public portfolio of your work in real time.

Some people also use it as a humblebrag—a way to show off without being too obvious about it. That’s fine if that’s your thing, but for most, it’s a way to turn the lonely process of building into something more connected and human.

And I think that shouldn’t be discouraged.




Definitely agree. Sorry if the article sounds a bit negative, but I'm overall still in favor of building in public, for various reasons like the ones you mentioned.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: