On learning to build

'You will hate the first six months,' someone told me, and they were right, though not for the reason they meant. The hard part was never the syntax. The hard part was that software will not let you be approximate.

A screenplay tolerates approximation for a long time. You can carry a vague scene through four drafts on the strength of its atmosphere, and only in the room, with actors, does the vagueness present its bill. Software presents the bill immediately. It does not care that you meant well. This turns out to be a kindness.

What carried over

Structure carried over entirely. A codebase and a script are both arguments about what belongs next to what, and both fall apart in the same way — not from a bad line, but from a bad join. I had spent two decades learning to feel a bad join. That instinct transferred whole.

Voice carried over too, in a form I did not expect. Naming things well is the same muscle as writing dialogue well: you are looking for the word that is exact and also short, and you will know it when you stop being able to improve it.

What did not

Patience did not carry over. A draft can sit for a month and improve by sitting. Nothing improves by sitting.

The other thing that did not carry over is the idea that finishing is a moment. A film locks. A novel prints. A platform never does either — it only becomes, for a while, something you are not embarrassed by. I am still learning to find that satisfying rather than unfinished.