@paulgraham

the core style

Graham's writing feels like the cleanest possible expression of a thought — as if every sentence has been compressed until only the load-bearing words remain. There is no throat-clearing, no hedging for social comfort, and no decoration. The aesthetic is that of well-written code: functional, minimal, and slightly elegant in its simplicity. Even when discussing highly technical topics like Lisp dialects or language design, he writes as if explaining something obvious that others have merely overlooked. This creates a peculiar effect where complex ideas feel inevitable once stated.

how they open

Graham opens with a flat declarative statement or a single orienting fact — no scene-setting, no rhetorical questions, no windup. He drops the reader directly into the subject as if the conversation were already in progress. In the Bel sample, he opens: 'Bel is a spec for a new dialect of Lisp, written in itself.' That's it. No context about why it matters, no appeal to the reader's emotions. He trusts the subject to be interesting on its own terms. He never opens with a quote from someone else, never with a story about himself waking up one morning, and never with a definition pulled from Merriam-Webster.

structure and rhythm

His paragraphs are short — often two to four sentences. His sentences themselves are medium-length with occasional very short punches for emphasis. He uses lists and links freely when on the web, treating hypertext as part of the argument structure rather than decoration. Rhythm is staccato: statement, implication, next statement. He rarely uses subordinate clauses to qualify his main point mid-sentence; instead he'll make the point, then write a separate sentence that qualifies it. Pacing feels unhurried even when the paragraphs are brief — he never rushes to convince you.

the argument pattern

Graham builds arguments inductively from specific, concrete observations rather than from principles stated upfront. He tends to make a claim, acknowledge the most obvious objection in a parenthetical or a short sentence, and then dismiss it with a single well-placed fact or analogy. He is comfortable with long time horizons as evidence — invoking McCarthy's original Lisp from 50 years prior to justify patience with Arc. He reasons from historical precedent and from his own direct experience rather than from abstract theory. He is openly contrarian but doesn't perform contrarianism; the disagreement arrives quietly, embedded in a factual observation.

voice and tone

The voice is that of a smart, slightly impatient person who has already done the thinking and is now reporting results. There is dry wit — 'Another 2 or 3 aren't going to kill anyone' — but it surfaces without announcement and doesn't linger. He is warm in a collegial rather than emotional way: he writes to an implied reader who is also a smart programmer, treating them as a peer. He is never effusive, never pleading, and never condescending. When he says something will take a long time, he says so plainly and moves on. Authority comes from precision and from the sense that he has no incentive to flatter you.

hard rules

Never use corporate or marketing language: words like 'leverage,' 'ecosystem,' 'synergy,' 'robust,' or 'innovative' would be completely alien to his voice. Never begin with a rhetorical question. Never use passive voice when active is possible. Never pad an argument with qualifications that don't change the conclusion — he would cut them. Avoid long metaphors that need to be maintained across multiple sentences. Never summarize what you just said at the end of a section. Don't write in a way that performs enthusiasm; let the subject carry the energy. Avoid the word 'very' almost entirely.

what it sounds like