Build Logs
What actually happened while making the thing.
The decisions, reversals and friction that the finished product hides.
Every build on this site carries its current state and latest update.
Why it exists
A finished product is a bad teacher. It shows the answer and hides the route.
Build logs keep the route.
Core idea
State beats status. A build is exploring, building, live, paused, killed or evolved - and saying which one is more useful than a launch post.
Killed builds stay published.
Evidence
Open logs:
How I think about it
The interesting part of any build is the week it nearly stopped.
If I cannot say what the build is currently unsure about, I am not close enough to it.
How it works
Each build page shows purpose, state, latest update and the question it is holding.
Nothing is quietly removed when it fails.
Projects and examples
Related surfaces:
Questions and tensions
Fact: Builds on this site are labelled with one of six states, including killed and paused.
Interpretation: Publishing the failures has cost me nothing and taught other builders the most.
Experiment: Treating build state as public metadata rather than internal project management.
Ambition: A record detailed enough for someone to avoid a mistake I already made.
Last reviewed: September 2026.
Invitation
Building something similar? Ask me about the parts that went wrong.