Continuity over intensity

Most things worth building are won by people who kept a steady cadence for longer than was reasonable, not by bursts.

Above, one tall effort on a line that ends. Below, smaller beats that compound, on a line still going past the frame. The second is the larger sum.

Intensity is loud and legible: the heroic weekend, the all-nighter that saved the launch. Continuity is quiet, almost invisible, until it has compounded into something that cannot be copied. A codebase tended weekly for three years, a product whose reliability is simply assumed, a body of writing with a voice: none were built in a sprint. They were shown up for, at a cadence, for longer than was reasonable.

The trap is that intensity feels like progress and continuity feels like waiting. But the compounding is real, and it is unfair: the person who held a sustainable pace for five years ends up somewhere the sprinter can no longer reach. (This is old wisdom worn smooth by repetition, from consistency over intensity back to the tortoise. The reason it keeps being said is that it keeps being true.)

Pick a cadence you can hold when nothing is going well. That is the one that compounds.

All principles