Blog / build in public
How to build in public when AI writes half your code
Building in public means sharing a project while you are making it, including the parts that go wrong. When AI does a lot of the typing, there is a new thing worth sharing: how you steered it.
Say how AI helped
Readers are curious about the process. What did you ask for? What did the model get right? Where did you have to step in? Saying so is not a confession. It is the useful part of the story, and it is what other builders can learn from.
Share small, share often
A short entry once a day beats a long essay once a month. One sentence about what you tried is enough. Small entries lower the cost of writing, so you actually do it.
- What I tried today.
- What worked, and what did not.
- What I am doing next.
- One thing I would tell a friend about it.
Show the dead ends
Failed approaches are the most valuable entries. They save other people hours and they make the wins credible. If you shelved an idea, say why.
Number your entries
Numbering gives a project shape. Entry 001 is the first idea. By entry 040 a reader can see the whole arc. It also makes it obvious that you have been consistent, which builds trust faster than any claim.
Ask for help in public
When you are stuck on one specific thing, say so. Other builders often know the answer, and the question itself is a useful entry. Keep the question narrow: what you tried, what you expected, what happened.
Protect what is private
- Never share keys, tokens or customer data.
- Blur or crop screenshots that show private information.
- Share the lesson, not the credentials.
Let people follow the project, not just you
If you are working on several things, let people follow the one they care about. It keeps your audience interested instead of overwhelmed.
Keep your own build log
Write numbered entries, follow other builders, and let people watch your idea become real.
Join vibFolio