The internet rewards speed. Publish first, correct later, let the feed sort it out. This essay argues the opposite: that the writing worth reading in five years is the writing someone sat on for five weeks. ## The cost of fast Every editing pass you skip is a debt the reader pays. A rushed piece externalizes its confusion. ## What slow buys Time is the only editor that works for free. A draft that survives three weekends of rereading has earned its claims. Write fast. Publish slow.

- The bug is always in the code you were most sure about - Writing the summary first makes the meeting shorter - If a file needs a comment to explain its name, rename the file - Coffee after 3pm is a loan against tomorrow

Everything that has to happen before Tuesday's announcement. Anything not on this list waits until Thursday.

Figma’s engineering deep-dive on their multiplayer sync: client-side prediction, server-authoritative conflict resolution, and why they chose properties-last-writer-wins over OT. The section on undo in a multiplayer world is the best writing on the topic anywhere.

Four frames from walks I took instead of writing. The gallery keeps the set together and lets the pictures lead.

Notes from the talk, written up the same evening while the questions were still fresh. ## The premise Most technical writing is addressed to the person sitting next to you. The reader who actually shows up is a stranger, two years later, halfway through a bad day. ## What changes You stop writing "obviously". You define the term the first time. You say what you tried that did not work, because that is the part they cannot reconstruct. ## The question I could not answer Someone asked how you write for a stranger without writing for nobody. I still think the answer is that you pick one real person and let the stranger overhear.