In praise of the second draft
First drafts get all the romance. The second one does the work.
The first draft of this piece was longer, and it was worse.
That’s not modesty. That’s the whole argument, so let’s lay it out properly.
A first draft isn’t really writing. It’s thinking that happens to leave a residue. You sit down believing you know what you want to say, and somewhere around the fourth paragraph the actual point shows up, uninvited, wearing different clothes than you expected. This is normal. It might be the most useful thing about writing at all: you don’t find out what you think until you’ve watched yourself try to say it.
The same is true outside of prose. The first layout of a homepage, the first route for a logo, the first architecture diagram for a build.
Version one of anything is a question wearing the costume of an answer.
Its only job is to exist, because you can’t improve a thing that isn’t there yet. Blank pages have no bugs and no future.
That’s their whole appeal, and it’s a trap. The longer a thing stays imaginary, the more perfect it gets to pretend to be. Drafting is the act of trading a flawless fantasy for a flawed object you can actually work on.
So we’re gentle with first drafts around here. Fast, loose, unjudged. Get it down, get it wrong, get it out of your head.
Then the real craft starts.
The second draft begins with an unglamorous act: reading what you actually made instead of what you meant to make. Nearly all editing lives in the gap between those two. The opening you labored over is usually clearing its throat; the real opening is buried a few paragraphs down, already written, waiting to be promoted. The strongest idea often appears two-thirds of the way through, right where you finally stopped performing and started talking.
Editing is mostly the discipline of noticing this without flinching. Move the good thing up. Cut the runway it taxied in on. Ask of every sentence one blunt question: is this here for the reader, or for the writer? The line you’re proudest of usually fails that test. Clever is what a sentence does when it isn’t sure it’s useful.
Which brings us to darlings, and the killing thereof. The advice is old and correct, but people add too much drama to it. No ceremony required. No funeral, no moment of silence, no reading the deleted line aloud to the room one last time. Cut it and keep moving. If it was truly good, it’ll come back on its own in some future project where it actually belongs. Darlings are surprisingly durable that way. It’s the mediocre stuff you have to delete twice.
Some of us keep a graveyard file for the cut lines. Nobody has ever gone back to one and found a masterpiece, but the file makes the cutting easier, and easier cutting is most of the game.
A few habits that help, learned the slow way.
- Read it out loud, because your ear catches what your eye forgives.
- Delete the first paragraph and see if anyone would miss it; usually the answer is no.
- When you catch yourself defending a sentence, notice that the defense is the verdict.
- If the deadline allows, put a night between the drafts; distance is the cheapest editor there is.
None of this is confined to writing. Design reviews, code reviews, strategy revisions: it’s all second-draft work, and it’s where the actual quality gets made. First versions are cheap everywhere. What separates work that lasts from work that merely shipped is somebody’s willingness to go back in, coldly, and take things out.
The first draft of this piece had a much cleverer ending. We cut it.
This one’s for you.
