← Thinking

Thinking · March 2026

Why the second time is so fast

Redo something and it often takes a fraction of the time. You didn’t get better overnight. Most of the first pass was never spent on the making.

An afternoon of writing, gone. A crash, one wrong click — however it happened, the document is gone. You swear at the machine and start over, braced to lose another afternoon. It takes an hour and a bit. And the new version is better. Plenty of people have been through this. The fast rewrite isn’t a miracle. It gives something away: that first afternoon was never really spent on the typing.

The first time through, most of the hours go into figuring things out. What to say, what goes first. One section turns out to be unnecessary halfway through writing it. The hands are moving, but what’s really running is the understanding. Typing is the short last stretch. The second time, the figuring-out is already done, and only the typing is left. So it’s fast.

Making anything for the first time is a bit like crossing an unfamiliar room in the dark. You catch a shin on the table. You double back, feel along the wall for the switch. Every one of those steps shows up on the clock as making. Most of it is learning the room.

The first walk through.

The second time in, the room hasn’t changed. What changed is the map in your head. Where the table is, where to turn. You walk straight across. The speed isn’t in the hands — they’re the same hands as last week — the path just doesn’t need finding anymore. That’s also why the gap can be so large: the newer the thing, the more of the first pass went into learning the room, and the more absurd the second pass looks beside it.

Same room, second time.

The finished thing is a by-product of the figuring-out.

Put it another way: the first pass produces two things. One is the product, visible, something you can hand over. The other is the map, invisible, and it stays with whoever did the making. On the clock, most of the hours went to the map.

Seen that way, a redo loses less than it feels like. The lost file, the first version thrown out — what’s gone is mostly the by-product. The map is still on you.

The file is gone. The map isn’t.

It also goes some way to explaining why estimates so often miss. What gets estimated is the walking. The first pass also contains the learning of the room, and that part can’t be measured in advance — you find out what the room looks like by being in it.

“The second time is fast” runs the other way too. Some second times aren’t fast at all, because the first time nothing got understood. Filling in a template, or having a model walk the room for you — the thing works, but almost no map ends up on you. Come the second time, the room is still dark. So how fast the second time goes measures something plain: how much understanding the first time actually left behind.

Back to the unsaved afternoon. The anger is fair. But the hour of retyping walked a path that afternoon had already found.