Categories
Writing

Still Learning

I never thought about rhythm in my writing. Not once.

A lifetime of writing. More essays than I can count. One book. And the sonic quality of my sentences — the way they moved, or failed to move, through a reader’s mind — simply wasn’t something I considered. I was too busy trying to say something true. I thought that was enough.

What changed was reading differently. Not for pleasure anymore, or not only for pleasure. David Perell conducts long interviews with writers about how they actually work — not what they believe about writing, but what they do, physically, at the desk, in the dark, before anyone sees it. He asks the same structural questions of very different writers and the patterns emerge slowly, the way patterns always emerge: first you see it once and think nothing of it, then you see it again, then you can’t stop seeing it. Rhythm came up constantly. Always in different language. Pacing. Breath. Music. Momentum. Always pointing at the same thing.

Then I found this from Susan Orlean:

My new preoccupation was on the sonic quality of my writing — the rhythm and tone of the sentences. I began reading all my work out loud, listening for places that lagged and dragged, that didn’t sparkle. I knew it was unlikely that anyone else was reading my stories out loud, but I was convinced that you do “hear” writing in your head as you read, and this pushes you (or stalls you) through the piece. I wanted the music — that is, this subconscious tonal effect — to match the subject.

I stopped. Read it again.

Because she was describing something real — something I had been doing wrong for twenty-five years without knowing it was wrong. You don’t know what you can’t hear. That’s the whole problem. The silence where the knowledge should be is itself silent.

I don’t read my work out loud. There’s something strange about it, something that breaks the spell — you stop being a writer and become an actor, hearing your own sentences hanging in the air, too exposed. But I do read and read again, more carefully now, looking for the wobble. Orlean’s point holds regardless of method: you hear writing in your head as you read it, and that hearing either carries you forward or it doesn’t. The ear that matters is the one inside.

George Saunders has a practice he describes in A Swim in a Pond in the Rain: he reads from the beginning of a piece over and over, and the moment something feels off — a word, a rhythm, a single syllable landing wrong — he stops and fixes it before moving forward. Never skips the trouble spot. Never tells himself he’ll come back. His opening pages accumulate dozens of passes before he ever reaches the end. What he’s really doing, underneath the technique, is training himself to feel the exact microsecond when a reader’s attention would start to drift. To catch the loss before it happens.

That’s not craft instruction. That’s building a new sensitivity where there wasn’t one before.

John McPhee works from the other direction entirely. His famous boxes — index cards, sorted into piles, piles arranged into sequences, nothing drafted until the structure is known — are about architecture before a single word is written. He’s deciding which rooms exist, and in what order, before he furnishes any of them. Where Saunders builds outward from one true sentence, McPhee builds downward from a blueprint.

But they’re asking the same question. McPhee: is this section in the right place? Saunders: is this word in the right place? Both listening for the moment the piece loses its hold on the reader. Both doing triage on something most writers never even examine.

What I’m still learning — slowly, and late — is that rhythm isn’t decoration. It isn’t the thing you tend to after the real work is done. It’s structural. A sentence moving at the wrong speed for what it’s carrying fails the thought itself, not just the ear.

There’s something else I’ve been thinking about. If rhythm is the thing that’s hardest to hear in your own work — if the ear takes years to develop — then maybe the most useful writing tool isn’t a grammar checker. Those are solved. What isn’t solved is the rhythm problem. An editor who listens for the wobble, explains what’s failing and why, and works through the fix with you rather than just patching it. Not a red pen. A teacher.

I’ve been experimenting with exactly that. An AI editor I call Clark. His job isn’t correctness. It’s the sonic quality of prose — the rhythm — the same thing Orlean was describing, the same sensitivity Saunders spent years training. Clark finds what’s working as hard as what isn’t. And when something fails, he explains what the reader’s inner ear is hitting and why. Helpful.

I didn’t know much about rhythm in writing when I was fifty. Didn’t know it at sixty.

I’m not entirely sure I know it now. But I know it more than I did, which might be the only kind of knowing that’s real.

A lifetime of writing. Still learning how to listen.

Categories
Storytelling Writing

The Craft in the Work: A Reading Guide to Ten Storytellers

There’s a kind of reading that’s really a form of listening — not to what a writer is saying but to how they’re solving a problem. Every great piece of nonfiction is an argument about structure, and most writers never explain it aloud. The argument is in the choices: where the piece starts, when it digresses, what it leaves out, how it ends. You can enjoy the work without seeing any of this. But once you start seeing it, you can’t stop — and eventually, some of it becomes yours.

This guide is for both kinds of reading. Each writer here is worth your time as a reader. Each one also has something specific and stealable for anyone who writes. I’ve tried to name both.

The ten: John McPhee, Robert Caro, John Jeremiah Sullivan, Michael Lewis, Joan Didion, David Grann, Sam Anderson, Susan Orlean, Tom Junod, and Wright Thompson. Different registers, different obsessions, different methods. What they share is a commitment to making difficult things feel inevitable — and the discipline to make that look effortless.

They fall into three loose clusters, which might help you find your entry point. Structure builders — McPhee, Caro, Grann — write pieces that feel inevitable because the architecture is invisible but load-bearing. Emotional access — Orlean, Junod, Thompson — get you inside feeling before you know you’re there. Voice and form — Didion, Sullivan, Lewis, Anderson — the sentence, the digression, the explanatory seduction, the essay as genuine inquiry. The clusters overlap, and the best writers in each group are doing all three things at once. But if you’re trying to solve a specific problem in your own writing, the clusters tell you where to look first.

Categories
Writing

The Unfinished Note

I’ve been sitting with a Susan Orlean line for a few days now, the way you sit with a splinter you can’t quite locate.

“Stories don’t need a ‘conclusion,’ a flourish of finality. It’s better to leave readers falling forward, tumbling through the piece and beyond it, finishing the tune in their heads.”

What strikes me isn’t the advice — plenty of writing teachers have said something like it — but the verb she chose. Tumbling. Not drifting. Not lingering. Tumbling. There’s a loss of control in that word, a small helpless momentum, the way you take one more step than you expected on a dark staircase and your body has to catch up to itself.

I’ve always been suspicious of endings that arrive wearing their own bow. You can feel them coming, those last paragraphs — the rhythm slows, the sentences get more declarative, the writer seems to straighten up and clear their throat. And then comes the lesson, the restatement, the turn toward uplift or hard-won wisdom. The piece explains what it was about. You close the browser tab and that’s the end of it.

But some pieces don’t end so much as they stop, at the right moment and the right angle, and something in you keeps moving. You find yourself thinking about them in the shower two days later. You’re not remembering the conclusion because there wasn’t one. You’re still inside the piece, finishing the tune, as Orlean says. The writer handed you the melody and walked off mid-phrase.

I think about this with music. Jazz, especially. The best solos don’t resolve — they suggest a resolution and then leave the air charged with it. Miles Davis understood that the note you don’t play is still a note. The silence after the phrase is part of the phrase.

I’m not sure I’ve ever actually written an ending this way. Most of my pieces come in for a landing; I can feel myself starting to circle and descend. Maybe that’s the real lesson in Orlean’s line — not a craft note about structure, but a challenge to trust the reader enough to leave the door ajar. To believe the piece was good enough that they’ll want to keep walking around inside it.

I’m still not sure I do.

Categories
AI AI: Large Language Models Claude

Make It Better

I came across a post on X this morning with some advice I immediately tried out. The advice – when working with an AI to help create writing or code – is to reply to the first pass the AI takes by asking it to “make it better”. The author suggested doing this multiple times.

I tried this out with Claude and enjoyed how it worked on just the first “make it better” pass. When I asked it to “make it better” it began by replying:

Certainly, I’ll refine the musing to make it more impactful and engaging. I’ll focus on enhancing the imagery, tightening the structure, and deepening the insights.

And indeed the second “better” pass that it wrote was even better. A fun experiment to try on your next use of an AI chatbot.