Building in Public Without Burning Bridges

Building in public as a software engineer means sharing what you learn from building software products — without turning your online presence into a liability at work. It’s a way to grow your personal brand, attract an audience, and compound your reputation over time, all while keeping your professional relationships intact.

There’s a growing narrative that if you build software on the side, you need to brand yourself as a founder. Announce your MRR. Post daily updates. Signal that you’re on your way out.

I disagree.

Why engineers should build in public

Most of the people I admire who ship great side projects don’t make noise about it. They let the work speak. They write about what they learn — not to build an audience, but because writing clarifies thinking.

Building in public works for engineers because it compounds. According to Stack Overflow’s 2024 Developer Survey, 63% of developers learn new technologies through self-directed projects — and sharing what you learn from those projects gives others a reason to follow your work.

The benefits are practical:

Writing sharpens thinking. If I can’t explain a decision clearly, I probably haven’t thought it through. Writing forces precision in a way that coding alone doesn’t.
It compounds over time. A well-written post about a real problem attracts people who have that problem. That’s more valuable than any social media algorithm.
It’s employer-safe. Nothing here signals you’re halfway out the door. You’re an engineer who builds things and writes about it. That’s a feature, not a liability.

What building in public looks like for engineers

Building in public doesn’t mean revenue screenshots and daily update threads. For engineers, it looks like this:

Write essays about engineering decisions — not what you shipped, but what you learned and why you made the choices you did.
Share technical deep-dives — break down real problems you solved, with enough detail that other engineers can learn from your approach.
Document your process — the tools, frameworks, and tradeoffs involved in building a real product.

The key distinction: you’re sharing knowledge, not performing success.

A practical framework for building in public

Here’s the framework I use. It’s simple, sustainable, and doesn’t require you to become a “content creator.”

Build something useful. Not a todo app. Something that solves a real problem you or someone you know actually has.
Write about what you learn. Not what you shipped — what you learned. The distinction matters. Shipping is a fact; learning is valuable.
Let the work compound. Good writing about real problems has a longer half-life than any tweet thread. One strong essay can drive traffic for years.

That’s the playbook. Simple, sustainable, and you don’t have to burn a single bridge to do it.

How to keep it employer-safe

The line between “ambitious engineer with side projects” and “flight risk” is thinner than you think. Here’s how to stay on the right side:

Focus on craft, not revenue. Write about engineering and product decisions, not income.
Frame it as learning. “I built this to learn X” is always employer-safe. “I’m building my own thing to quit my job” is not.
Don’t announce timelines or business goals publicly. Your ambition is real — it doesn’t need to be broadcast.
Let the work speak. A portfolio of well-built projects and thoughtful essays makes you more valuable to any employer, not less.

Frequently asked questions

How do I start building in public as a software engineer?

Start by building a side project that solves a real problem, then write about what you learn along the way. You don’t need a large following or a content strategy — just publish one honest essay about a real engineering decision, share it on X or LinkedIn, and repeat. Consistency matters more than volume.

Is building in public risky for my career?

Building in public is only risky if you frame it as a departure from your current role. If you position yourself as an engineer who builds and writes about it, most employers see that as a positive signal. Avoid sharing revenue goals or “escape plan” language publicly, and focus on craft and learning.

How often should I publish when building in public?

Quality beats frequency. One well-written essay per month is more valuable than daily low-effort posts. Aim for a sustainable cadence you can maintain for years — the compounding effect of consistent, quality writing is what builds a real audience.

What’s the difference between building in public and personal branding?

Building in public is one tactic within personal branding. Personal branding is the broader strategy of shaping how people perceive your work and expertise. Building in public specifically means sharing your process — what you’re building, what you’re learning, and how you’re thinking about problems — in real time.