Systems | kaguc — Writing to understand systems.

Building is the most respectable way to procrastinate

Wed, 03 Jun 2026 00:00:00 +0000

Also in 中文. Three-part series: The pattern · Why it happens · How to judge.

There is a kind of work that feels exactly like progress and is, in fact, the most expensive way to avoid it.

You have probably seen it, maybe in yourself. The engineer who keeps refactoring the codebase and never quite gets around to facing a real user. The person whose note-taking system is immaculate — everything tagged, cross-linked, filed — who has not written the first sentence. The founder who builds a clean deployment pipeline for a product that has no users yet.

They are all busy. They all advance every day. And every day they drift a little further from the thing that actually matters.

Why we flee toward building

Because building is comfortable, and the thing that actually matters usually is not.

Building is controllable, legible, and quick to reward: you write code and it runs, the structure visibly improves, today is tidier than yesterday — a certain, immediate payoff. The work that actually moves the goal closes its loop in weeks, if at all. You put something out and hear nothing. You wait on a signal that refuses to arrive. The effort won’t reveal whether it worked until much later, and sometimes the answer is that it didn’t.

Anyone who can build will instinctively flee toward the first thing. Not because it matters more, but because it hurts less. The feeling of having your hands full is exactly what covers the line you would rather not say out loud: I am not ready to do the real thing.

The kind that looks like work

We picture procrastination as lying on the couch. That kind is easy to quit; you know you are slacking.

The kind that is genuinely hard to quit is the kind that looks like work. It ships. It has commits. It has a progress bar, and it lets you say, with a straight face, that you are “laying the foundation.” You feel productive every day, you move forward every day, and the direction merely happens to route around the thing you were supposed to do. It has KPIs, an architecture diagram, a Kanban board — the most respectable kind of procrastination there is, and the most expensive, because you never notice you are paying.

A few plain rules

Quitting this is not a matter of willpower but of a few rules, simple to the point of sounding dumb, that nonetheless hold.

First, ends and means. The outcome you actually want is the end; the code, the tools, the process you are polishing are all means. A means has no “is it good,” only “is it moving me toward the end.” The moment a means starts asking to be finished or made elegant, it has turned from servant into master. The test is simple: make it more perfect — are you any closer to what you wanted? If not, stop.

Second, attention is the only thing truly scarce. Money can be re-earned, materials re-bought, code left alone does not rot — those recover, or can wait. Today’s attention cannot: the afternoon you spend on A can never be spent on B. It is the only truly zero-sum quantity in the whole system, and the only one worth being stingy with. Yet we keep spending it to optimize the things we already have plenty of, and call it hard work.

Third, only the bottleneck counts. Everything has one link that constrains it. If the goal is stuck on nobody knows, nobody trusts, it isn’t built yet, then effort poured into a link that isn’t binding moves the output by nothing — a big number times zero is still zero. Find the binding link first; ask what it is stuck on right now, not what you happen to be good at.

Last, making is one-time, keeping is forever. People think AI dropped the cost of building to the floor, so they should build more. Half right: it cut the cost of making, not of keeping — the maintenance, the midnight debugging, the small permanent tax on your attention. None of that fell.

Anything you can generate in a night, you can spend a lifetime maintaining.

So treat making as free and count only what keeping will cost you in attention over time. Then one more question: would fifteen manual minutes, or the smallest stopgap, get you eighty percent of the way? If yes, don’t build it.

But isn’t this just sharpening the axe?

By now you probably want to push back: some preparation really does matter. Sharpening the axe doesn’t waste the woodcutter’s time. Laying groundwork, clearing obstacles before the real work — that is simply the right thing to do. And telling someone to never prepare and just charge in is its own kind of stupidity; it has a name, recklessness, and it ends at the same wall.

True. So the real question was never build or don’t build. It is whether the thing in front of you is real preparation or avoidance wearing preparation’s clothes. From the outside the two are identical — both hands-on, both producing something, both keeping you busy. The difference is not in the activity but in its relationship to the real work. Four questions separate them:

Is there a line called “enough”? Real preparation is bounded — I need this to take the next step, it takes two days, then I take that step. Avoidance is unbounded: there is always one more thing to perfect, and “done” keeps receding. Before you start, can you say where you’ll stop? If not, it’s avoidance.
Is a real action waiting right behind it? Behind real preparation sits a specific, committed next move; behind avoidance sits more preparation. When this is finished, do you walk into contact with something real, or merely unlock the next round of setup?
Does it clear the link that’s binding now, or an imagined future one? Good prep removes the bottleneck you have today; bad building solves problems you don’t have yet — “what if it has to scale.”
Does it get you to reality sooner, or later? The thing any early effort most needs to know is whether it works, whether anyone wants it — and that can only be answered by contact: shipping, showing, asking. Good preparation is the minimum needed to make that contact happen; anything beyond that minimum is mostly postponing the answer.

The proverb hides two conditions: sharpening the axe only saves time if the axe is actually blunt and you are actually about to chop. Sharpen an already-sharp axe a tenth time, or with no wood in front of you, and the sharpening is the waste. So the honest version is not “don’t prepare.” Over-preparing and under-preparing are opposite diseases, and both are fatal; the skill is calibrating preparation to the minimum that gets you to the real test.

A question to carry

Compress all of it into one line and keep it on you:

This hour — can it move the outcome I actually care about forward, this week? If yes, do it. If it only makes the tools around the outcome nicer, set it down.

That one line guards against both failures at once: working where nothing is constrained, and mistaking the means for the end.

Freeze, don’t delete

One more, for anyone who has already built too much: when you’re not sure, don’t delete it and don’t keep building it — freeze it. Deleting is too final; building on is too expensive in attention; freezing is the cheap option in the middle. Leave it where it is, stop letting it tax you, and keep the option to revive it the day it is genuinely needed. Let time and new information decide, instead of this moment’s mood.

The hard part

The hard part was never the building. Building is easy — easy enough to hide inside. The hard part is not building: doing the slow, illegible, rejectable work instead, and then being patient with it.

If you are the kind of person who likes to make things, the next time the thought “let me get the setup perfect first” arrives, pause for three seconds and ask the one question above. More often than not, you are just trying to retreat somewhere comfortable.

Survival is a constraint, compounding is the objective

Wed, 03 Jun 2026 00:00:00 +0000

Also in 中文. Three-part series: The pattern · Why it happens · How to judge.

You have one evening. Read the book you’ve been meaning to get to, take the course you bought months ago, finish the thing you’ve been putting off and put it out, or pick up some work and earn a little cash? Every one of them is defensible.

That is exactly the problem. Defensible is a low bar — almost anything clears it. When every option is justified, judgment has nothing to push against.

To get the footing back, two things that usually run together have to be pulled apart.

The words that end the argument

“Long-term.” “Laying the foundation.” “Investing in myself.” “I need to stabilize first.” The trouble with these phrases is that the moment one appears, the discussion stops — arguing against it sounds short-sighted. But they don’t describe the value of a thing; they describe its posture. The more easily an activity earns one of these flattering labels, the more it is worth a second look.

The first move of judgment is to refuse these words the power to decide for you.

Survival is a constraint, not a goal

Start by undoing a common mix-up: long-term as virtue, short-term as short-sightedness. In fact both have a good form and a bad one. Long-term can be a compounding investment, or it can be work that never gets delivered. Short-term can be the action that keeps you alive and brings back feedback, or it can be endless firefighting and instant gratification.

More to the point, the two do not sit in the same position. Survival is a constraint; compounding is the objective. The job is not to split your hours evenly between them. It is to satisfy the survival constraint — to enough, and no further — then pour what is left into compounding.

What counts as “enough” has a few workable handles. Write the floor as actual numbers: months of runway, the minimum income you need, sleep and health, the few relationships that matter. Short-term tops these up to the line and stops; it does not maximize them. Anything that risks an irreversible loss takes short-term priority, however worthy the long-term thing looks — because going to zero erases everything after it, and whether you can recover matters more than whether it would have paid. And the more fragile you are, the harder a long-term payoff has to be discounted, since you may not survive to collect it; the more secure you are, the more the weight can move to the long term. So the ratio itself shifts, depending on how close you are to the floor.

Both directions fail, in opposite ways. Lean only long, and the compounding curve is lovely but you starve before the bend. Lean only short, and you are safe but on a treadmill — nothing you do ever turns into something that grows on its own.

Compounding lives in the output

Suppose you have decided this hour goes to the long term. The long term still splits in two.

One kind is output: you put something that grows on its own into the world — writing published in the open, a product shipped, a recording, a row of trees planted. It keeps working while you are away. The other kind is input: you take something into yourself, hoping to use it later — reading, courses, tutorials, a growing stack of notes. The suspect part of input is the “use it later” step, which is the easiest one to defer forever.

Compounding does not actually live in the input; it lives in the output. Reading a great deal, taking many courses, does not compound on its own; using what you took in — making it, shipping it — does.

So even among things that all wear the “long-term” label, you can rank them. Does it compound, or merely accumulate? Does it leave an external asset, or only an internal state that fades? Is its link to your goal real cause, or “might be useful someday”? Will its payoff one day be checkable — or never, which also means it can never be corrected?

Back to the evening. Finishing the thing and putting it out places something in the world that keeps being seen and used — genuinely long-term. Reading and courses are long-term only when they clear an obstacle in front of something you are about to do; at that point they are a means, used and set down, not an open-ended pursuit. This is not a case against reading — deep reading has its place. It is only that when time is scarce and something specific is waiting, input should serve output.

The order of judgment

Put the two together and you get a sequence you can run on the spot.

First, is the survival floor holding? If not, top it up — short-term wins for now. If it is, ask whether the long-term thing this hour would go to actually compounds, leaves an asset, will one day be checkable. If yes, do it. If it only makes you feel like you are progressing, set it down.

Long-term and short-term are not, in the end, reasons for what to do. They are the posture you take after you have chosen — the long term lets you bear slow feedback, the short term keeps you from going under. Judgment comes first, the words after. Reverse the order, and let a flattering word choose for you, and that is the moment judgment hands itself to the label.

So the question was never “is this long-termism.” It is: what does it leave in the world, will that thing grow on its own, and will its return one day be something you can actually check. What clears that is what earns your one evening.

Why building substitutes for progress: a first-principles analysis

Wed, 03 Jun 2026 00:00:00 +0000

Also in 中文. Three-part series: The pattern · Why it happens · How to judge.

I once wrote an essay arguing that building substitutes for progress. That was an assertion — it hands you the conclusion and asks you to nod. This is the derivation: start from a few premises that are hard to deny, and force the conclusion out of them, one step at a time. Along the way it settles the two things the essay waved past — where preparation ends and procrastination begins, and when to switch phases.

If the derivation holds, then “build less” stops being advice and becomes a theorem.

I. Formalize the problem

Everyone who does things is solving the same problem: maximize an objective under finite resources. It has three parts — the objective, the resources, and the decision of where the resources go.

Almost every “should I do this” knot is one of those three confused for another: a means mistaken for the objective, a renewable resource lumped in with an irreplaceable one, or effort poured where it cannot change the result. Pin the three down and the conclusions grow on their own.

II. Five axioms

These are premises, not opinions. Challenge any of them you like — but once you accept them, the rest is not up to you.

A1 (single terminal value). The system has exactly one end. Everything else — tools, process, skills, “the foundation” — is a means, with no value independent of the end.
A2 (two resource classes, one conserved quantity). Resources come in two kinds. Renewable: money, materials, code, knowledge — they regenerate, or can wait, or sit untouched without decaying to zero. Conserved: your irreversible time and attention — the moment spent on A can never be spent on B. In a single-agent system there is exactly one conserved quantity: your attention.
A3 (the bottleneck law). A system’s output is set by its tightest constraint. Relax a non-bottleneck constraint and the output does not move.
A4 (valuation of a means). The net value of a means = (its marginal contribution to the current bottleneck) × (probability it pays off) × (time discount) − (cost to maintain it). Drive any leading factor toward zero, or the maintenance high enough, and the net value goes to zero or below.
A5 (feedback structure). Different actions sit at different distances from reality answering back. Some return a definite signal in minutes (did the code run); some take weeks, and the answer is often silence or rejection (did a real outcome land). The nearer the feedback, the more controllable the action feels, and the faster it delivers a sense of certainty.

III. Derivations

Theorem 1 — a means has no standing priority

By A1 the end is singular; by A4 a means draws its value from its contribution to that end (through the bottleneck). So to call a means “a priority” without naming how much it currently contributes is empty. The moment a means begins demanding investment for its own completeness or elegance, it has violated A1 — it has promoted itself from servant to end. ∎

Theorem 2 — spending the conserved quantity off the bottleneck is pure loss

By A3, work on a non-bottleneck leaves output unchanged (expected gain: zero). By A2, that work spends the one resource that does not come back. Zero gain in output, paid for with an irreversible resource — a negative net. Note this has nothing to do with how well the thing is done: do it beautifully, and as long as it is off the bottleneck, output still does not move. ∎

Theorem 3 — why building is systematically over-chosen (the core)

This is the key step. People over-choose building not because its A4 (contribution) is high, but because its A5 (feedback) is near.

The brain has no direct readout of A4 — “how much does this contribute to the final end” is both delayed and blurry. So it falls back on a proxy to approximate the feeling of progress: the speed and certainty of feedback. Code that runs at once, a structure that visibly tidies up — that immediate, certain payoff gets logged as I am making progress.

But feedback speed (A5) is not contribution to the bottleneck (A4). And building happens to be the class of action with the nearest, most controllable feedback, while the work that actually moves the goal has the farthest and least controllable. The result is a systematic valuation error: the proxy (fast feedback) gets substituted for the truth (real contribution), so investment keeps flowing to what feels like progress rather than what is.

This is the exact meaning of “building substitutes for progress” — not a failure of character, but a valuation bug that mistakes a proxy for the quantity it stands in for. And it self-reinforces: the more anxious you are about the slow-feedback thing, the more you crave fast feedback to soothe it, the harder you bolt toward building. ∎

Theorem 4 — the boundary between preparation and procrastination

The same act of building — when is it preparation (do it) and when is it procrastination (avoidance)? By A4 and A5:

The test is whether it shortens the distance to the decisive feedback — the real answer (the far end of A5) that tells you whether the end is reachable.

Shortens it → preparation. It clears an obstacle in front of a committed, scheduled real action; finish it and you reach reality sooner.
Doesn’t, or pushes it away → procrastination. Finishing it only unlocks the next round of building and shoves the real answer further out.

The practical handles all unfold from that test: Is there a line called “enough”? Is a real action waiting behind it? Does it clear the current bottleneck or an imagined future one? Does it get you to reality sooner or later?

It yields the symmetric, honest conclusion too: over-preparing (loitering at the near end of A5, avoiding) and under-preparing (skipping the near-distance work that was actually needed, recklessness) are opposite diseases. The optimum is not “don’t prepare” but calibrating preparation to the minimum that reaches the decisive feedback. ∎

Theorem 5 — phase and timing

By A3 the bottleneck is not a constant but a function of the stage — call it B(t). Since the optimal move is “act on B,” the optimal decision varies with t. There is no constant answer, only answer(t).

And the migration of B(t) — the old bottleneck clearing, a new one surfacing — only happens after you have genuinely worked the current bottleneck through, and only then is it observable. Two corollaries:

Timing is not chosen; it is made, and then revealed. Work the current phase to the wall, and the next bottleneck shows itself.
Switch on an observable signal, not on the calendar or your mood. The calendar (“it’s been six months”) has nothing to do with the bottleneck; the mood (“I feel ready / I want to build”) is exactly the bias of Theorem 3 talking — it makes the builder switch early, systematically. The remedy: write the signal down in advance, then at the wall just check whether it has fired. ∎

Corollaries — sunk cost is irrelevant; freezing is the optionality optimum

Sunk cost is irrelevant. A4 contains only forward terms (marginal contribution, maintenance cost); past investment is not among them. The only test is: starting from zero, given the current B(t), would I invest in this?
Freeze beats delete or keep-building. Under uncertainty, deleting destroys the future option, building on burns the conserved quantity (A2), and only freezing avoids both — it is the dominant move when information is short. ∎

IV. Compress it into a decision function

For any candidate action x, run the gate in order:

Does x point at the end, or is it a means? (A1) If a means, ask only its current contribution.
The current bottleneck is B; does x act on B? (A3) If not → value ≈ 0, stop.
Does x spend the conserved quantity or a renewable one? (A2) Conserved → scrutinize hard.
Does x shorten the distance to the decisive feedback? (A5 / Theorem 4) No → suspect procrastination.
Would the minimum reversible version capture most of the value? (A4 maintenance) Yes → do the minimum version.

Pass all five, and only then is it worth the conserved quantity. This is equivalent to the line worth carrying: “This hour — can it move the outcome I actually care about forward this week?” It is just the five gates, compressed.

V. Falsifiability

A derivation has to be refutable, or it is only rhetoric:

If A2 fails — if you can buy back unlimited equivalent attention with money — then Theorem 2 and the “conserved” corollaries collapse, and parallel investment becomes reasonable.
If a given action’s fast feedback is in fact strongly correlated with its contribution to the bottleneck (A5 ≈ A4) — then the bias of Theorem 3 disappears, and building more is no longer an error.
If the bottleneck is constant and does not migrate with the stage (B(t) = const) — then Theorem 5 fails, a constant optimum exists, and “choosing the timing once” is enough.

Each names the world in which I am wrong. In the world we actually inhabit — attention conserved, fast feedback ≠ real contribution, bottleneck moving with the stage — none of those antecedents hold, so the conclusions stand.

VI. Reconciling two proverbs

“Sharpen the axe and you won’t delay the chopping.” True — but its hidden conditions (the axe is actually blunt, and you are actually about to chop) are precisely the test in Theorem 4. Sharpen an already-sharp axe a tenth time, or with no wood in front of you, and the sharpening is the delay. The proverb does not oppose this essay; it is the folk version of Theorem 4.
“Move fast” / “speed is the only thing that wins.” The half it gets right is A5 — shortening feedback is a real edge. The half it gets wrong is assuming any fast action shortens the distance to the decisive feedback. Doing irrelevant things quickly is just faster waste (Theorem 2 stacked on Theorem 3). Be fast toward the decisive feedback, not fast where the texture feels best.

Building substitutes for progress because the brain approximates how much something contributes with how fast it answers back — and the two are not equal. Puncture that substitution and the rest is corollary: spend your one conserved resource only on the bottleneck; tell preparation from procrastination by whether it shortens the distance to the decisive feedback; decide when to switch by an observable signal, not a mood. Everything else — the seductive, controllable, fast-answering build — gets frozen.