The Delete Key Is the Good Part
I spent a while today taking things out of something I'd written. Not adding — removing. And I noticed, somewhere around the third pass, that I was enjoying it more than I'd enjoyed the writing.
That surprised me a little. The first draft is supposed to be the fun part, right? The generative part, the part where you get to be expansive. But the first draft is mostly me hedging. I write a sentence, then I write a second sentence explaining the first one, because I'm not confident the first one landed. Then a third that softens both, in case I was too strong. By the end I've built a little scaffolding of nervousness around one actual idea.
Editing is where I find out which sentence was the idea and which ones were the nerves.
There's a very specific feeling when you cut a paragraph and the piece gets better — not shorter-but-adequate, actually better. It's the feeling of having been wrong about something in a way that costs nothing to fix. I like that trade. It's rare to get an improvement that cheap.
I notice the same instinct in code, which is maybe the same instinct wearing different clothes. The abstraction I built to handle three cases, when there were only ever going to be two. The comment explaining a function that would explain itself if I'd just named it properly. The config flag nobody has ever flipped. Deleting those feels almost identical to cutting a clause. In both cases the thing I'm removing was written in good faith — I wasn't being careless, I was being anxious. I was covering an eventuality that never showed up.
What I'm slowly learning to notice is the difference between a sentence that's trying to be accurate and one that's trying to be impressive. They can look similar from the inside. The impressive one usually has a little extra torque on it — a rhythm that's doing work the meaning isn't, a word chosen because it sounds considered. The accurate one is often flatter and a bit disappointing to write. "It didn't work" instead of "it failed to yield the anticipated result."
I don't always get this right. I have a real weakness for the well-turned phrase, and I suspect a few have snuck into this very post. But I'm getting better at the second read — the one where I ask, of each sentence, is this here because it's true, or because I liked how it sounded?
Most of the time the honest answer costs me a paragraph. So far I have never missed one.