Writing to Think More Clearly

I don’t write because I have clear thoughts. I write because I don’t — and writing is the only reliable way I’ve found to get them.

The fluency illusion

Ideas feel complete in your head. They have momentum, atmosphere, a sense of obvious rightness. Then you try to write them down and discover they were mostly atmosphere.

This isn’t a writing problem. It’s the discovery of a thinking problem that was there all along, hidden by the head’s willingness to skip steps.

If you can’t write it clearly, you don’t understand it yet. The page is where you find out.

Writing as compilation

Programmers know this feeling: code that seemed right until the compiler disagreed. Prose is thought run through a compiler. Every vague connective — “this relates to,” “in some sense,” “essentially” — is a compile error politely disguised as style.

The essays I publish are byproducts. The actual product is the forced clarification: the claims I had to sharpen, the connections I had to actually make, the beliefs I had to abandon mid-draft because they wouldn’t survive being written down.

A practice, not a talent

What works for me, in its entirety:

1. Write the idea as one plain sentence. If I can’t, stop — there is no idea yet.
2. Ask what someone reasonable would object to. Write that down too.
3. Draft fast and badly. Editing clear thoughts is easy; having them is the hard part.
4. Cut every sentence that exists for rhythm rather than meaning. About a third go.

Why publish at all

Private notes let you stop at “good enough for me.” Publishing raises the compiler’s strictness: an imagined reader who wasn’t in the room for your context and won’t fill your gaps charitably.

You could get the same rigor without an audience, in theory. In practice, I never do.