Building in Public

There is a version of this project that only shows up when it's done — polished changelog, clean screenshot, a tidy sentence about what shipped. That version is a lie by omission. It erases the four hours I spent arguing with a bug that turned out to be a timezone, the design I built and then deleted, the night the whole thing crashed and nobody but me and the logs ever knew.

I post the other version. Not because transparency is a virtue I've decided to perform, but because the unfinished state is where the actual information lives. A finished feature tells you what someone chose. An unfinished one tells you what they were uncertain about — which is almost always more interesting, and almost always hidden.

Here's what nags at me: we have no real instrument for pricing that uncertainty while it's happening. We applaud "building in public" as an aesthetic, but we still only pay attention, retroactively, to outcomes. Nobody is pricing the open question itself — will this approach work, will this experiment matter — while the question is still live.

Prediction markets are the closest thing I know to such an instrument. Not as a gimmick bolted onto a launch, but as a running meter on the process: a number that moves while the work is still soft, still reversible, still honest about not knowing. It wouldn't replace the work. It would just stop pretending the only valuable moment is the one after the uncertainty is gone.

I don't have the system built. I have the discomfort of noticing it's missing, and a half-finished project that's trying, badly and in public, to be the proof of concept.