Building loud.
Why we stream the workbench, push the half-finished commits, and write down the things that didn't work.
There's a tradition in software that says: ship the demo, hide the rough edges. Cut the commit history. Quote the success metric. The polished surface is the product; the workbench is a liability.
We stopped doing that about a year ago, and the work got better. Not because attention is a virtue — it isn't — but because writing things down forces a kind of honesty the workbench rarely sees on its own. You can't pretend a hack is elegant when you're explaining it to a stranger at 2am on a stream.
So now we ship loud. The repo is public. The Twitch is on. The bad ideas live in the same git tree as the good ones, with the date stamp to prove which came first. Field Notes is the next chapter — the place where we collect what we've learned, what we'd do differently, and the small details we want to remember.
If you're here for the highlight reel, fair warning: there isn't one. There's the work, and there's writing about the work. Everything else is just marketing.
Polish is what happens when you stop hiding. Not the other way round.
— Field Notes № 01