Hien Phan
Hien Phan
WorkAI craftWritingAbout
WorkAI craftWritingAbout

Apps

SpeakEn
Back to Writing

When Building in Public Backfired on Me

Exploring the popular 'building in public' trend from my authentic perspective. I'll share personal experiences, including times it boosted my motivation and times it led to unexpected pressures or even negative feedback, offering a balanced view and a guide on how to do it authentically without burning out.

July 1, 2025•4 min read•Hien Phan
Indie Hacking
building-in-public
lifestyle
indie-maker

Beyond the Hype: My Honest Take on 'Building in Public' (and When It Backfired)

The idea of "building in public" sounds amazing, right? Sharing your journey, getting instant feedback, and building a community around your work.

I was all in. I remember vividly sharing a small win with my nascent product, feeling so proud of a tiny feature I'd finally implemented.

Within hours, someone pointed out a flaw I hadn't even considered, and it felt like a punch to the gut. Suddenly, that little win felt exposed, and the vulnerability was overwhelming.

A person looking thoughtfully at a laptop screen with code on it.

This is the unstated challenge of building in public. It's not just about sharing progress; it's about managing expectations - both yours and everyone else's.

There's a subtle pressure to always show progress, to appear constantly on the verge of a breakthrough. This can lead to burnout, forcing you to put on a brave face when things are tough, or worse, making you share things that aren't truly ready, just to keep up appearances.

It can feel like a performance, not a process.

I've realized that to do this sustainably, I need my own rules. So, I created my "Authentic Public Builder Blueprint." It's not a rigid system, but a set of guidelines that help me share honestly without sacrificing my sanity or my product's integrity.

Here's what it looks like:

  • What to Share: Focus on learnings, challenges, and genuine progress. Share the "why" behind your decisions, not just the "what." Celebrate small wins, but also be honest about roadblocks.
  • When to Share: Don't feel pressured to share daily. Share when you've something meaningful to communicate, whether it's a new feature, a customer insight, or a lesson learned.
  • Handling Criticism: View constructive criticism as a gift, but don't let negativity derail you. Develop a thick skin, but also know when to disengage. Not every comment needs a response.
  • Setting Boundaries: Decide what is private. You don't need to share every single detail of your life or your entire business plan. Protect your mental space.
  • Focus on Process: Emphasize the journey and the learning, not just the final outcome. This makes your progress more relatable and less about chasing vanity metrics.

A flowchart illustrating the steps of the Authentic Public Builder Blueprint.

I've seen both sides of this coin. Early on, sharing a demo of my MVP on Twitter led to a few valuable conversations and even a potential collaborator reaching out.

That felt incredible. On the flip side, I once spent weeks building a feature I thought was revolutionary, only to announce it to… crickets.

It was disheartening, and the silence felt louder than any negative feedback. There was also a period where I felt judged for not shipping anything for a few days, even though I was deep in user research.

Building in public is a powerful tool, but it's not a magic bullet. It can be incredibly motivating and helpful when done with intention. The key is to find a balance that works for you.

Ultimately, the goal is to build something meaningful, and that process is often messy and non-linear. By setting your own boundaries and focusing on authentic sharing, you can leverage the benefits of building in public without succumbing to its pressures.

A person smiling and giving a thumbs up, with a background of successful product launch graphics.

My Takeaway for You:

  • Define your own "building in public" rules. What are you comfortable sharing, and what are your boundaries?
  • Focus on sharing your learning process. This is often more valuable than just showing finished products.
  • Don't compare your behind-the-scenes to everyone else's highlight reel. Be kind to yourself.
  • Build in public, but build for yourself first. Your journey is yours to control.

Previous

TypeScript Best Practices for React Developers

Next

How I Bounced Back from Burnout

Hien Phan
Hien Phan

Full-stack engineer shipping production-grade web systems. Real apps, real stack.

Navigate

  • Work
  • Writing
  • About
  • Contact

Live apps

  • SpeakEn

Reach out

harrisonphan5@gmail.com

Saigon, Vietnam
Product-minded teams. AI-native product work welcome. Remote-friendly. Based in Vietnam (GMT+7).

© 2026 Hien Phan. All rights reserved.

Built with Next.js · TypeScript · SQLite · self-hosted KVM