What the Clock Knows

There is a kind of work that does not announce itself. It does not demand a launch, a press release, a number that goes up. It enters the room quietly and stays for a long time. Every morning you check on it, the way you might check on a fern, and most mornings nothing has changed. Then one season you look up and notice the shape of the room is different.

The clock knows this work. The calendar does not.

The calendar speaks in events: the launch, the deadline, the milestone, the quarterly. It is a vocabulary built for visible work, work that can be summarized in the present tense at a meeting. The clock speaks in something else, a slower verb. Accumulate. Compound. Hold. The clock will let you do nothing for a year if you have not earned an answer yet, and it will not be impressed when you finally do.

The shape of patience

Most of what we call ambition is impatience wearing a tie. It wants the result before the work that produces the result. It wants to be the kind of person who has a finished thing without going through the embarrassing middle where the thing does not yet exist and you cannot defend it to anyone.

Patience is not the opposite of ambition. Patience is what ambition turns into when it has learned the local terrain. It is the form ambition takes once you have understood that some things only happen on time scales the calendar refuses to track because the calendar was designed for a different category of work entirely.

The slow thing has a different physics. It runs on residue, on what is left after the immediate enthusiasm has burned off. A friendship is slow. A practice is slow. A body of work is slow. The discipline of returning, on a Tuesday morning in the rain, to a thing nobody is asking you to return to, is slow. None of those things can be hurried, and none of them survive without a clock that is patient enough to outlast the calendar's interruptions.

You can model the difference. The fast project optimizes for the gradient at t. The slow project optimizes for the gradient at t + n, where n is large enough that most of the people now arguing about the gradient at t are no longer in the room. This is a mostly mechanical observation, but it has a moral edge: most arguments are about the wrong derivative.

// the difference, simplified.
fn fast() {
  optimize("this quarter");      // loud, legible, finite
}
fn slow() {
  optimize("this decade");
  return compounding(work);      // quiet, illegible, unbounded
}

The two are not opposites. A real practice runs both. fast() pays the bills and the rent of attention. slow() pays the rent of being a person. You will get into trouble if you stop running either one.

What scales is what stays

The compound curve is the most over-cited shape in the genre. It is also true. The thing about compounding is not that the rewards are large. The rewards are large in many shapes of work. The thing about compounding is that the rewards are silent for most of the duration, and then loud all at once, and the silence is the part that filters out everyone who was here for the noise.

The silence has a name in physics. Underdamped systems take time to converge. They appear to be doing nothing, then overshoot, then settle. The behavior is not slow because the work is small. It is slow because the work has not finished phasing.

Three kinds of patience, ranked

1. Boring patience. Waiting because there is nothing else to do. The cheapest kind. It does no work.
2. Greedy patience. Waiting because the calendar said to wait. Slightly more useful, but still tied to someone else's clock.
3. Earned patience. Waiting because you have done the underlying work and you understand which derivative you are tracking. This is the only kind that compounds.

The third kind is the one nobody describes well, because describing it makes you sound either pious or smug. The honest version is closer to: I know what I am doing. I have done it before. I will keep doing it on Tuesday morning whether or not anyone is watching, because the thing I am building requires Tuesdays, and the calendar does not get a vote on what I do with my Tuesdays.

The patient man may not see his patience rewarded; but the impatient man will not see his impatience rewarded either. One of them, however, will have spent the interval doing the work.

The clock's reply

If you sit with a clock long enough you stop hearing it tick. You start hearing it answer. It answers in the negative space between events: in what you stopped doing, in what you did not say, in what you returned to without being asked. The reply is never an event. The reply is the long, slow accumulation that forms underneath the events, the way sediment forms underneath whatever the river happens to be carrying that week.

• What compounds: a body of work, a friendship that survives a hard year, a practice you cannot remember not having, a place in a town that recognizes you on a Wednesday in February.
• What does not compound: anything that lives entirely inside the calendar's vocabulary. The launch, the announcement, the streak. These can be useful. They are not the substrate.
• What is hard to tell apart at the moment: most of it.

Build for the second column when you can. Spend the first column where you must. Be honest about which is which. The clock will be the only auditor that matters and it will not arrive until you have stopped checking.

If you found this useful, the rest of the archive is one click back. There is more on the same theme there, none of it in a hurry.

— Everett