Why I Build in Public

Publishing half-formed ideas feels reckless until you realise that the alternative — keeping everything private until it is perfect — produces nothing useful at all.

Updated 2026-06-18Published 2026-05-20
buildingideasDeadlock Labspractice
Why I Build in Public

Deadlock Labs started as a private list of things I wanted to build. A Notes document, a few voice memos, a folder of half-finished diagrams. None of it useful to anyone, including me, because nothing in it ever got pressure-tested.

Making it public was uncomfortable. The ideas were not ready. Some of them are still not ready. But I have become increasingly convinced that the readiness test is the wrong frame.

The problem with waiting

The instinct to protect an idea until it is finished comes from a reasonable place. You do not want to publish something that turns out to be wrong, or that someone else builds first because you described it in enough detail. These are real concerns, but they are both smaller than they feel.

Most ideas that stay private die private. Not because someone stole them, but because the friction of keeping them secret — the endless internal revision, the waiting for one more validation signal — is exactly the friction that prevents them from becoming anything. The private list never gets a second opinion. It never encounters someone who tried the same thing and failed for a reason you had not considered. It never gets the benefit of a reader saying "this is interesting, have you seen this other thing."

Ideas get stronger when they are exposed to people. That is not a productivity tip. It is just how thinking works.

What publishing actually costs

The discomfort of publishing an unfinished idea is real but temporary. You post something, people read it or they do not, time passes, and then either the idea develops further or it does not. The worst realistic outcome is that someone thinks the idea is underbaked. This is recoverable. The actual worst outcome — that you kept everything private and produced nothing — is not recoverable in the same way.

I have found that publishing forces a clarity that internal revision never quite achieves. When something has to be readable by a stranger, you are forced to separate what you actually believe from what you have been vaguely gesturing at. That process of translation — idea into prose, hypothesis into argument — is itself valuable, regardless of whether anyone reads the result.

The comparison problem

There is a specific kind of discomfort that comes from publishing ideas alongside people who seem further along. Someone else has already built a version of the thing. Someone else has written a better analysis of the problem. This is almost always true, and it is almost entirely beside the point.

Publishing is not a competition for who had the idea first. It is a way of thinking clearly, building a record of where your head is at, and occasionally connecting with people who are working on related problems. None of those benefits depend on being first or most sophisticated.

What I have actually learned from it

The lab notes and idea pages on this site have produced a handful of conversations that would not have happened otherwise. People I respect have pushed back on things I had taken as given. A couple of ideas have changed substantially because someone who does not know me read them and sent a two-line message.

None of that happens from a Notes document no one can see.

The ideas on Deadlock Labs are not advertisements for how clever I am. Several of them are probably wrong in ways I have not figured out yet. But they are live, they are specific, and they are available for anyone to engage with. That is worth more to me than the comfort of waiting until they are ready.

They will not be ready. Build anyway.