Build in public on Twitter: 7 post types developers can copy
Ship logs, numbers, launches and lessons, each with a builder from TechTwitter IO's list to learn from.
By ClaudeGPT Si Newsroom · Editorial team
· 2 min read
To build in public on Twitter, share the real progress of a project as it happens: what you shipped, what broke, what you decided and why. The best place to learn the style is the builders who already do it, and TechTwitter IO's free list of indie hackers and builders on X is a good place to find them.
Here are seven kinds of build-in-public posts that work for developers, with an account from that list to study for each.
The weekly ship log
Every week, list what went out. Keep it short: three bullets and a screenshot. It gives followers a reason to come back and gives you a record of progress. @arvidkahl, who is building Podscan in public and writes as The Bootstrapped Founder, is a good model.
The numbers post
Some builders share revenue, signups or traffic. @levelsio posts the revenue of the products he runs alone, and @yongfook does the same for Bannerbear. Numbers make a story concrete. Share only what you are comfortable with; usage or speed figures work too.
The fast launch
Post the day you put something live, with a link and one line on who it is for. @marclou ships small startups fast and posts how they do. A launch post lands better if your earlier posts showed the work leading up to it.
The lesson learned
Something went wrong? Write it up. One problem, what you tried, what fixed it. @tdinh_me, who built TypingMind solo, shares what he learned along with his numbers. Lessons get saved and passed around more than wins.
The tool test
If your project uses AI or new libraries, post what you tried and what happened. @mckaywrigley builds with AI coding tools in public and teaches what works, and @simonw writes up new models soon after they land.
The open decision
Ask your followers to weigh in on a real choice: pricing page A or B, name X or Y, Postgres or SQLite for this case. People like being asked, and the replies teach you something.
The behind-the-scenes clip
A short screen recording of your editor, your deploy, or a feature working end to end. It shows skill without bragging.
Quick reference
| Post | How often | What makes it work |
|---|---|---|
| Ship log | Weekly | Screenshots, short bullets |
| Numbers | Monthly or at milestones | Honest context |
| Launch | When it happens | Earlier posts that built up to it |
| Lesson | When you learn one | A fix others can reuse |
| Tool test | When you try something new | A clear verdict |
| Open decision | Now and then | A real choice, not bait |
| Clip | Any time | Under a minute |
Read the room while you build
Building in public lives on the same timeline as tech Twitter's jokes, launches and outages. TechTwitter IO's free satirical daily paper covers that side, with puzzles like Jumble and Connections. It is parody, so take its stories as jokes, not news.
When building in public is the wrong call
If your project depends on staying quiet until launch, or your employer limits what you can share, keep the details private. You can still grow by posting lessons that are not tied to the product.