Why Build-in-Public Became a Spam Problem
Build-in-public started as a genuinely good idea.
Be transparent. Share your journey. Let people watch you build something from nothing. The openness creates accountability, builds audience, attracts early users who care about the product before it launches.
For a lot of builders, it worked exactly like that.
Then it became a content strategy.
What Happened to Build-in-Public
When enough people saw that building in public could attract an audience, the practice shifted.
Instead of genuine transparency, it became a formula.
Day 1: announce the idea. Week 2: post an update. Week 6: excited to share the launch. Week 10: lessons from our first 100 users. Week 20: we are shutting down, here is what I learned.
Every step packaged as content. Every milestone framed as a story. Every product update posted as if an audience was waiting.
The problem: most of the time, nobody was.
The Spam Problem
Platforms that reward product posting attract product posting.
Twitter filled up with "building X in public, follow along" threads. LinkedIn feeds drowned in announcements. Product Hunt posts disappear within hours because everyone is launching and nobody is genuinely discovering.
The build-in-public movement, at scale, created a specific kind of noise.
Everyone broadcasting. Not enough people actually listening.
The issue is structural. When a platform makes it easy to post about your product, people post about their products. When there is no filter between genuine contribution and self-promotion, the promotional content takes over.
The signal-to-noise ratio collapses.
This is how platforms die slowly. Not from lack of users, but from lack of reason to pay attention.
The Algorithm Is a Values Statement
Here is something that does not get said enough about social platforms.
The algorithm is not a neutral tool. It is a values statement.
Whatever the algorithm rewards, the community produces more of. Reward engagement bait, you get engagement bait. Reward product spam, you get product spam. Reward genuine insight, you get genuine insight.
This is the lever that determines what kind of community a platform becomes.
Most platforms get it wrong because they optimise for engagement above everything else. Engagement is not the same as value. A spammy product post can generate engagement. A genuine technical insight can go unread. If the algorithm cannot tell the difference, the platform degrades regardless of how good the intentions were at the start.
What Forg Changed and Why
Forg's early positioning was drifting toward build-in-public.
The problem became clear fast. If the platform rewarded product posting, Forg would become a place where builders spam their products at each other with nobody actually paying attention. A promotional feed with a professional skin on top.
That is not a professional network. That is a bulletin board.
So the feed algorithm changed.
Genuine content gets priority. Tech insights, honest learnings, opinions about building, things that are actually useful or interesting to other builders. This is what rises in the feed.
Product updates and launch posts have their place, but they reach people only after a builder has established real presence through genuine contribution. You build an audience by being worth following. Then your product posts land somewhere real.
The principle: earn reach by contributing value, not by promoting yourself.
Why This Is the Right Call
Professional networks are built on trust and signal.
LinkedIn's core problem is that it became a promotional platform. Everyone is announcing, celebrating, sharing milestones. The genuine signal is buried under noise. Nobody opens LinkedIn expecting to learn something.
The platforms that stay useful are the ones where signal-to-noise stays high. Where you can open the feed and reliably find something worth reading.
That requires an algorithm that actively protects signal. It requires making a deliberate choice that not all content gets equal reach, and what determines reach is whether the content contributes something genuine to the people reading it.
This is how professional reputation works in the real world.
The people in any field who actually get listened to are not the ones who shout loudest about their own work. They are the ones who consistently contribute insight others find useful. Their signal-to-noise ratio is high enough that when they do talk about their work, people pay attention.
A well-designed feed algorithm replicates that dynamic at scale.
What This Means for Builders
Practically, the shift means one thing.
Post like a professional, not like a marketer.
Share what you actually learned this week. Write about the technical decision you made and why it was harder than it looked. Post about the thing you built that did not work and what you figured out from it. Talk about the tools you use, the patterns you keep seeing, the things the industry is getting wrong.
Build the kind of presence that makes people want to follow you because you are genuinely worth following.
Then, when you launch something or hit a milestone, post about it. At that point it lands somewhere real because you have an audience that actually cares about what you do.
The shortcut of posting product updates into the void never worked. It just took a while for platforms to stop rewarding it.
The Bigger Picture
There is a version of professional networking for builders that is actually useful.
Not a broadcast channel. Not a launch board. Not a feed of people announcing things to nobody.
A network where genuine contribution earns real reach, where builders post things worth reading, and where the platform actively maintains the quality of what it surfaces.
That is what Forg is trying to build.
The feed algorithm is not a technical detail. It is the most important product decision a social platform makes.
Get it wrong and you build a spam board.
Get it right and you build a network people actually want to be part of.
Replies
Hello Kumar, I like the idea of earning attention through useful contributions first. It creates a much stronger connection with the audience.
Forg
@pranay19 I'm not saying build-in-public is completely bad. It's just not good for your product and the viewers both if you spam build-in-public post about random things instead of actually sharing genuine lessons learned, mistakes etc.
Forg
@pranay19 Two wrongs don't make a right.
TrackerJam
How do you think platforms can separate genuine learning posts from posts that are only written for reach?
Forg
@maklyen_may I think the platform's algorithm can do partial job. I was facing this exact same issue in forg.to. I tweaked in algorithm. Also adding a report option as less effort post (or ai slop) can be better if users actually report.
WebCurate.co
I think the problem isn't build-in-public itself, it's when people treat it as a distribution hack instead of a way to share genuine experiences.
Some of the most useful posts I've read were from founders sharing mistakes, lessons learned, or things that didn't work. The issue starts when every post becomes "look what I'm building" and very little of it is actually useful to the reader.
In the end, people follow builders for insights, not for a daily stream of product announcements.
Forg
@hosseinyazdi I agree with you, this is my exact point. And it becomes annoying if you're aggressively spamming the build-in-public posts. It would be much better if you share lessons learned, mistakes with which everyone can relate.
This resonates. Build-in-public works when it is a record of judgment, not a stream of announcements. The posts I still pay attention to usually include the tradeoff, the mistake, or the decision behind the update.
For AI products especially, I think credibility comes from showing where the product failed, what guardrail changed, and what the team learned from real users. Otherwise every update starts to sound like launch theater. The useful version is less “watch us grow” and more “here is the problem we understood better this week.”
Forg
@rahulbhavsar I agree with you, genuine share about lessons learned, mistakes is much better than spamming build-in-public posts.
Build in public used to be watch me build. Now it's often "watch me announce that I'm about to build 😅
Forg
@bernard_lewis haha true!