Nathan Gwyn
Back to blog
Projects2026-03-105 min read

Building in public without faking progress

Shipping screenshots is easy. Showing the real tradeoffs, dead ends, and version changes is much more useful.

projectsprocessproduct

The fake version 🎭

A lot of project pages jump from idea to polished outcome as if the middle never happened. That makes the work look cleaner, but it also strips out the most interesting part: how decisions were made under pressure. That missing middle is usually where the real learning happened.

I want this site to show more of the middle. Not every rough draft. Not every bug. Just enough to prove there was actual thinking behind the final thing. 🧪

The useful version 🧭

Real-world shipping includes weird bugs
Build in public means showing the weird bugs too.

When I write about a project, I want to capture what changed, what constraint forced the change, and what I would do differently now. That is the part that makes future me better, and it is also the part that other builders usually care about.

A good project archive should feel less like marketing and more like evidence. Evidence beats polish-only storytelling.