Notes on shipping fast

By BC·6 min read

The gap between a working demo and something reliable enough to depend on — and the small process changes that close it.

Process overview

feedback loop

Idea

Build

Evaluate

Ship

feedback loop: Evaluate → Build

State

Fig. 1 — the loop, with feedback running from Evaluate back to Build.

The gap between a demo and something people can depend on is rarely about polish. It's about how quickly you find out something is wrong, and how cheap it is to fix once you know.

This is a section heading

Most projects stall not because the idea was wrong, but because the loop between building and finding out got too slow. Shrinking that loop matters more than getting the first version right.

This is a subsection heading

First point in a bulleted list.
Second point, same measure as body text.

First step in a sequence.
Second step.

ship.ts

const ship = (idea) =>
  build(idea).then(test).then(deploy);

Run npm run build before every deploy — inline code sits on a slightly darker chip than the page background.

Momentum matters more than polish in the first version.

“A quoted line from someone else — kept quiet, secondary to the author's own voice.”

— Source Name, Publication

That means shipping smaller than feels comfortable, watching what actually happens, and treating the plan as something you update weekly, not something you defend. Read more in the original essay for full context.

Designing with constraints →