Every craft podcast tells you to push through. On this, every craft podcast is wrong.

Or to be fair: right about half the time, badly wrong the other half. And nobody teaches you which half you’re in.

Most working writers have lived the bad version. A chapter you couldn’t draft for 3 weeks. You finally forced it onto the page, and the prose just sat there, dead, through three rounds of revision.

Then you accepted what the book had been telling you the whole time. That chapter didn’t belong in the book you were actually writing. So you cut it.

The weeks were gone. The forced draft was worse than nothing. And you didn’t know there were two kinds of stuck until the second kind cost you a month.

There are two kinds of stuck. Four questions will tell you which one you’re facing, before you waste the 3 weeks finding out the hard way.

The motivation case is real. Sometimes you’re stuck because you’re tired, or scared of a hard scene, or pulled away by life, or just out of practice.

In those cases the usual advice works exactly like the advice books say. Butt in chair, lower the bar, get something down, fix it later. The block is in you, and discipline really is the cure.

Here’s the tell: this kind of stuck follows you around. If you sat down today and tried to draft a different chapter, any chapter, you’d be stuck on that one too. The book is fine. You’re the problem.

The advice books have good reason to lead with this. For first-time novelists and hobby writers, the usual failure really is “I don’t have the discipline yet.” Push through is a fine default for the people the advice is aimed at.

But the people it’s aimed at and the people who hear it aren’t the same group. A working novelist on chapter 14 of book 3 gets the same line as a hobbyist on chapter 2 of book 1. The line was tuned for the second case.

When the first writer follows it on the wrong chapter, the cost is dead prose and lost weeks and a chapter they cut anyway. The advice fits when the resistance is general. It misfires, sometimes badly, when the resistance sticks to one chapter.

And you can learn to tell the difference.

Here’s the shift that did the most for my own work, once I learned to trust it.

An outline is a guess about the shape of the book. The draft tests that guess.

By chapter 14, the book has piled up choices, character growth, world details, and pacing facts the outline never saw coming. The outline made an educated guess. The draft has been quietly correcting it the whole way.

The chapter that won’t draft usually belongs to an older version of the story. The outline planned it for the book you meant to write. The book you’re actually writing has moved on.

As outlined, the chapter assumes something that turned out to be false:

When any of these is true, the chapter fights you because there’s nothing honest to draft. The prose can’t show a scene the rest of the book doesn’t support. That fight, the thing you experience as block, is the book refusing to lie.

This is why forced versions of these chapters read dead. You can produce sentences. The sentences can’t do story work, because the job the chapter was built for no longer matches the job the book needs.

The chapter sits in the draft like a wall built in the wrong part of the house, holding up nothing. Sooner or later you notice and cut it.

I’ve watched this happen in my own books and in friends’ manuscripts I’ve read for writing group. The shape repeats often enough that I now treat it as the first explanation for chapter-specific stuck.

So here’s the shift. Getting stuck on one chapter is information. The book is telling you, in the only language it has, that the chapter you planned doesn’t fit the book you actually wrote.

Listen. The question changes from “how do I force this chapter onto the page” to “what is this resistance telling me about what the book has become?”

Listening sounds vague. These 4 questions make it concrete. Run them in order and stop at the first one that fails.

Question 1. Can you say, in one sentence, what this chapter has to do for the larger story?

If you can name a clean job for it, go to question 2.

If you can’t, the resistance is structural. The chapter has no clear job in the book as it stands now. Maybe you outlined something that was never really a chapter. Or it was a chapter once, and the book handled its job somewhere else while the outline stayed the same.

Don’t force it. Cut it, or rebuild it around a job you can name.

Question 2. Has the book earned what this chapter assumes?

For the chapter to land, some things have to be in place already. A relationship. A fact. A stake. A character’s mood.

Check the actual pages. The outline thought the setup was done by chapter 8. Open chapter 8 in the draft and see if it’s there.

If the conditions are in place, keep going.

If they’re missing, the problem lives upstream. Drafting this chapter without the setup produces prose that asks the reader to feel something the book hasn’t earned. The fix belongs in the earlier scene that should have planted what this chapter expects to find.

Question 3. Is the point-of-view character the right one to carry this chapter?

The outline picked the POV. The draft has been growing the characters, sometimes faster than the outline guessed. The right POV for chapter 6 might be wrong for chapter 14, because the character has changed, or because the events read stronger from inside someone else’s head.

The test: can this character see what happens here, and care about it, in a way that gives the reader something worth sitting inside?

If your honest answer is “the outline said this character” instead of “this character is the only one who can show what the scene needs,” the POV may be wrong. Try the chapter from another character’s head and see what loosens.

Question 4. Are you stuck on this chapter, or stuck in general?

This is the motivation test, and it comes last on purpose. It only means something after you’ve ruled out the structural problems.

The warm-up check: could you draft a different chapter today, one you’ve already drafted and revised, and write honest prose?

If yes, the stuck is chapter-specific, and the first 3 questions should have caught it. If they didn’t, run them again with fresh eyes.

If no, the stuck is general. It’s motivation. The usual advice fits. Lower the bar, get words down, fix later.

The order matters. Start with question 4 and you’ll read every structural problem as a willpower problem, then spend a month digging the wrong hole deeper. Only push through when 1, 2, and 3 all pass and 4 points to general stuck.

Honest concession: sometimes the chapter that won’t draft is the chapter you discover the book through.

Some writers, especially discovery writers who think by drafting, work through structural problems by writing into them. The forced draft isn’t always wasted. Sometimes the dead prose is you learning what the chapter needs to be, by writing the wrong version and seeing what’s wrong with it.

The catch: this works best when you know that’s what you’re doing. The forced draft as exploration is a different animal from the forced draft as panic. The first is listening with a pen in your hand. The second is shouting over the book and hoping volume counts as craft.

Notice which one you’re doing. If the forced prose turns up real insight, if you end the session knowing more about the book than when you started, keep going. If it turns up dead sentences and self-blame, stop and run the questions.

The difference is usually clear by the end of the second hour, if you’re honest about what’s on the page.

The chapter you can’t write is usually a chapter the book has moved past. Sometimes the book is the smarter party in the room, and resistance is the only way it can tell you so.

Next time a chapter won’t draft, run the 4 questions before you call it block. Stop at the first failure and treat that failure as your answer.

Most of the time the trouble sits upstream, in some assumption the book has quietly dropped. Fix that and the chapter writes itself. Or you’ll find the chapter never needed to exist, and the book has been telling you so for weeks while you argued with a decision it had already made.

Until next time, thanks for listening.

A sixteen-year-old, one humiliating half second, and the reckless thing he does to prove it wasn’t the whole story.

You already know where you rank. Somebody decided years ago, the label stuck, and most days it feels settled. The athletes and the brains walk the halls like they can prove it, and the worst part is that sometimes they can.

Now give that a screen. Picture a version of high school where the ranking is literal: everyone gets scored on six traits, and the system shows the numbers. The kids who land high in the ones that count at school flash them around. The kids who don’t learn to keep their overlay shut.

That’s the world Kes lives in, and he’s holding the worst possible hand. Average almost everywhere. One odd flag on a stat called Flux, which is worth exactly nothing in a classroom. And his Flux had fired once in four years, at the worst possible moment.

Freshman year. Inter-school playoff, up one to nothing, seven minutes left. The ball came in at an angle nobody was reading, his stat flickered for half a second, his foot landed wrong, and he put the ball into his own net faster than he should have been able to kick it. The whole field saw it. Nev was in the stands. He hasn’t stepped on a pitch since.

So that’s who he is now. The kid whose one special thing turned out to be a way to lose in front of everyone.

The system left him one door, though, and it nags at him through every chapter. His Flux sits there flagged with a line he can’t put down: reassess upon measurable engagement. Do something big enough to make the variance fire again, and the system will take another look at you.

There’s one place near the colony where that’s possible. Past the perimeter fence, out in the unmapped country nobody’s cleared to cross, there’s a Flux rift. Reach it, and your Flux gets tested for real.

You can already see the shape of the bad idea. He talks his two best friends into coming. Nev comes mostly to keep him from getting himself killed, which stings, because the person he most wants to stop seeing him as the own-goal kid is the one who just signed on as his babysitter. Harko comes because Harko reads people better than the system does, and he can see Kes is going with them or without them.

Here’s the confession. I built this universe to be big. An alien system switches on across known space and starts measuring every living mind on six traits, and there’s a whole grown-up world of fallout I was itching to write.

But another idea took control and wouldn’t let go. A small one: a sixteen-year-old who wanted to matter and did something stupid to get there.

Being sixteen survives the system completely intact. What the system adds is a number for the thing every teenager already lies awake over. Am I actually special, or did I just need to be? Does anybody really see me? If I pull off the one impossible thing, will she finally look at me differently?

In our world those fears are invisible, so we get to argue about whether they’re real. In Kes’s world the system prints them on an overlay he can open a hundred times a day. The feeling is identical. It just comes with a scoreboard now.

People ask, and I never have a clean answer ready. The series this belongs to has grown-up machinery in it, the kind with soldiers and colony politics and deaths that don’t reset. A bookstore wants one shelf, and a sixteen-year-old scared his one talent means nothing doesn’t obviously share it with the grown-up sci-fi the rest of the series reads like.

Here’s where I landed. What makes a story young adult is its vantage: it stands with a person doing something for the first time, carrying the stakes only a first time has. The first time you risk the whole crowd watching you fail. The first time you gamble your own safety just to be seen differently.

By that measure Kes is YA to the bone, and the alien overlay clamped over his life never once moves him off it.

People hear “far-future sci-fi” and assume the story must be about the future. The ships, the system, the cold machinery of what’s coming.

The stuff that actually runs a teenager’s life is older than any of it: who’s watching, and whether one bad moment everyone saw gets to be the whole story about you. Kes is chasing a number on a screen. What he’s really doing is trying to be more than the half second the whole school replays when they see him.

Put that kid in any century, with or without an alien overlay clamped over his life, and any reader who has ever been sixteen knows exactly what’s at stake.

First Contact is where it starts. One kid, two friends who should know better, a fence they’re not cleared to cross, and the rift waiting on the other side of it. Read it for free. The next story, Engagement Criteria, picks him up a year into the wait, still hanging on what the system will finally decide about him.

Until next time, thanks for listening.

Last time, I argued that revision is an OODA loop, and that the step most writers skip is Orient — the move where you frame what you’ve read against what the passage is actually for, before you change a single word. That’s easy to assert and harder to show. So this dispatch is one edit from my own work-in-progress, traced through all four stages, start to finish.

Here’s the part that should bother you before we even begin: the paragraph I’m about to fix was already clean. A line editor would have read it and moved on. The best edits often look like that — invisible to the kind of close reading most of us call editing, and visible only once you ask what the passage is supposed to do.

A little context, because the passage comes from a system-driven science-fiction novel and the narrator’s voice is doing something specific. Cade is an operative. His narration is clinical by design — he reads people, files what he finds, and moves on. There’s a hard rule in his voice: his emotions are never named directly in the prose. When he feels something, the text shows it in behavior, never in a label. Hold onto that rule; it does the heavy lifting later.

The scene: Cade has just sprung the trap he spent the whole book sensing. He’s extracted the person he’s guarding, and now he has to seal a woman named Mira out of the safe room — Mira, whom he failed to read for two hundred pages, who may have betrayed them and may simply have been used. Here’s how the chapter ended in the draft:

Before anyone could protest, I hit the close button, then set the security seal.

One anomaly dealt with.

Read that as prose. It’s fine — two clean sentences and a hard, terse button on the chapter. And that’s exactly the trap.

Read what’s on the page, not what I meant to put there. The sealing happens as a sequence of operations: close button, security seal, one anomaly dealt with. Mechanical. Efficient. In character for a man who files things.

And — this is the important part — there’s no prose friction here. Nothing snags. If I were running a line pass, scanning for weak verbs and clutter and repetition, this paragraph would sail through untouched. The signal that something is wrong doesn’t come from the words. It can’t, because the words are good. It shows up only at the next stage — and only if I bother to run it.

Frame what I observed against the structural model. Two facts about the larger book meet at this paragraph.

First: this is the climax of Mira’s entire arc. The book has been one long failure to read her — every chapter, Cade catalogs another anomaly and can’t resolve it. This is the moment that failure stops being a question and becomes irreversible. He seals her out, and he still doesn’t know if he’s right.

Second: the voice rule. Cade’s professional distance is built to crack in exactly two places across the manuscript, and this is one of them. The crack is structural. It’s planned. It’s supposed to happen here.

So the passage’s job is not “end the chapter.” Its job is to register the human cost of an irreversible decision, at an arc climax, inside a narrator who is forbidden from saying what he feels. Hold the draft up against that job and the problem appears instantly: One anomaly dealt with discharges the most important emotional beat in the book as a piece of paperwork. The arc lands structurally — the seal happens, the consequence is real — but the cost never reaches the reader. The beat is doing its plot work and skipping its emotional work, and the cleanliness of the prose is what hid that from me. The diagnosis came from naming the job — not from reading the sentences.

Once Orient is done correctly, the decision is usually fast — and, just as usefully, constrained. The framing tells me what I’m allowed to do.

I can’t name the emotion. The voice rule forbids it, and breaking the rule here would be louder and cheaper than the moment deserves. So the cost has to be carried by behavior, not statement. I considered the alternatives — an italicized line naming what the seal cost him, a closing beat that spelled out the failure — and they all broke the voice by over-naming the very thing the character won’t say. The disciplined choice is the smallest one the voice permits: a single physical beat, placed between the seal and the file, doing the work the label isn’t allowed to do.

Before anyone could protest, I hit the close button, then set the security seal. My hand stayed on the panel a moment too long.

One anomaly dealt with.

Nine words. My hand stayed on the panel a moment too long.

And look at what those nine words do to the line that was already there. One anomaly dealt with used to read as cold — a man closing a file. Now it reads as a man composing himself: the hand betrays him, holds a beat past function, and then he files the feeling away, because filing is what he does instead of feeling. The terse line stopped being coldness and became control. I didn’t just add a beat. I changed the meaning of the sentence underneath it without touching a word of it.

That’s the loop closing on itself — the new sentence became new evidence, and it rippled backward through prose I’d already decided was finished.

The honest caveat: you cannot run this loop on every paragraph. If I stopped to ask “what is this passage’s job at the arc level” on all of them, I’d never finish a draft, and most paragraphs don’t reward the question — they’re connective tissue, and a clean read is genuinely all they need.

The skill is knowing which paragraphs are load-bearing. This one was: an arc climax that doubled as a designated crack in the narrator’s armor. And here’s the tell I’ve learned to watch for — when a paragraph that’s doing structural work goes down easy, the easiness is suspicious. A clean climax, a frictionless turn, a final line that gives you no trouble at all: at the moments that carry weight, smoothness is exactly when to stop and Orient.

I’ll concede the other half too. A writer with the arc fully alive in their head might have written the hesitation the first time and never needed the loop at all. I didn’t — the draft sealed Mira out and moved on, and the loop is what caught it.

A line-read asks one question: is this sentence good? The loop asks a different one: what is this sentence for? At the moments that matter most, those two questions have different answers — and the gap between them is where the edits live that no amount of careful reading will surface, because they were never a problem of the words.

That’s what the last dispatch meant by naming what a passage is trying to do before you touch it. The proof isn’t the nine words I added — it’s that naming the job was the only thing that told me to add them.

So the next time a clean paragraph is sitting at a moment that matters, don’t trust the cleanliness. Ask what it’s for. Sometimes the answer is nothing — it’s doing its job, leave it. And sometimes the answer is the most important beat in the book, hiding behind two good sentences and a hard, terse close.

Until next time, thanks for listening.

When you’re stuck in rewrite hell — version after version, none of them actually better — the problem usually isn’t your writing skill. It’s something quieter that most writers never name.

Most revisions fight themselves. Here’s why.

Every working writer has felt the difference between a revision session that compounded — the draft genuinely got better, structurally, in ways that held — and a session that felt productive in the moment but produced a draft that wasn’t actually any stronger. Same writer. Same craft skill. Two sessions that looked identical from the outside. One worked. One didn’t. Most of us file the difference under mood or fatigue and move on.

It isn’t skill, and it isn’t mood. It’s a missing step in the cognitive operation, and once you can name the step, you can stop skipping it.

This dispatch will do two things. First, show what the conventional “passes” model — dev, line, copy — is hiding from you about what revision actually is. Second, give you a four-stage loop, borrowed from somewhere outside writing entirely, that names the move where craft thinking actually happens — the move most writers cut out of their revision sessions without realizing they’ve cut anything at all.

The pass model wasn’t a mistake. It was a fix for a real problem.

Writers who revise without structure tend to polish surface prose while structural issues sit underneath, untouched. They spend an hour rewriting a paragraph that should have been cut, miss the chapter break that’s in the wrong place, and emerge from the session with a manuscript that reads slightly better at the sentence level and is no closer to working at the book level. The pass model — developmental first, then line, then copy — solves that. It forces big issues to the front, prevents wasted polish on prose that’s about to be deleted, and gives the writer a sequence to follow when instinct won’t say what to fix next.

That’s a real win, and the argument here depends on conceding it. The pass model is genuinely useful, especially for writers who haven’t internalized story structure deeply enough to revise without scaffolding.

But the pass model is a scheduling metaphor. It tells you the order to do things in. It doesn’t tell you what you’re actually doing when you revise — what the cognitive operation looks like underneath the schedule. Writers who stop at the schedule have only modeled half the work, and the half they’ve left unmodeled is exactly where revisions either compound or burn.

The framework I want to borrow comes from a fighter pilot. John Boyd, working on air-combat doctrine in the 1950s, noticed that the pilot whose decision cycle is more accurately oriented — not faster, more accurately oriented — wins, because they consistently make moves that address the actual situation while their opponent is making moves that address an imagined one. He called the cycle the OODA loop: Observe, Orient, Decide, Act. It migrated out of cockpits into business strategy, security operations, anywhere decisions happen under pressure with imperfect information.

Revision is exactly that. Imperfect information. Decisions under pressure. A cognitive cycle the writer runs, often unconsciously, every time they touch a draft.

Walk the four stages, applied to editing:

Observe — Read what’s actually on the page. Not what you intended. Not what you remember writing six months ago. What’s there, on this read, today.

Orient — Frame what you observed against your structural model. What is this scene trying to do? What does the chapter owe the larger arc? What does the genre contract ask of this beat? What does the character’s voice in this passage require? This is the step that does the craft work. This is where structural and prose knowledge gets applied to the raw observation.

Decide — Choose the specific revision move. Once Orient has happened correctly, Decide is usually fast and obvious. The fix is implied by the framing.

Act — Make the change.

Then the loop closes. Observe again. The new prose is new evidence, and the loop runs on the changed material. Orient against it. Decide again. Act again.

The key insight is that Orient is where structural and craft thinking actually happens. It’s where you reach into your knowledge of story, genre, voice, character, and pacing and use it to interpret what you’ve observed. Drop Orient, and revision becomes raw observation feeding directly into raw action — which is exactly what panicked, unstructured revision feels like from the inside. You read a passage, feel friction, change something, read again, feel friction, change something else. No frame. No accumulating model. Just twitching at the prose.

The loop’s other quiet strength is that it delivers its own feedback. You don’t need an editorial letter or a critique partner to tell you what comes next — the change you just made becomes the next thing you observe, and re-orienting against it surfaces the next move. Every turn of the loop generates the input for the turn after it. The feedback is built in.

That self-feedback is also how the loop tells you when to stop. You run it on the scene, then on the chapter, then on the whole book, and you keep running it until a full turn produces no change — until you Observe, Orient, and find nothing the framing asks you to Decide. That’s a real stopping condition, not just fatigue. A finished scene isn’t one you’ve gotten tired of looking at. It’s one where the loop runs clean.

The pass model collapses into this loop, not the other way around. A “dev pass” is a series of OODA loops where Orient is structural. A “line pass” is a series of OODA loops where Orient is prose-level. They’re the same operation at different scales. Pretending they’re separate is what makes the boundaries leak — every line edit can surface a structural issue, every structural fix forces line-level rewriting, and writers who insist on the clean pass boundary end up either ignoring the problems they surface or restarting their pass from scratch.

The pass model schedules revision. The loop describes it. Most writers know the schedule and have never named the operation.

If the operation is the loop, then the failure mode is the missing step. And in my experience, almost every revision that didn’t compound is a revision that collapsed Observe straight into Act and skipped Orient entirely.

Here’s the diagnostic question. Between reading a passage and deciding to change it, can you name what structural model you used to interpret what you read? If the honest answer is I just felt it was off — you’ve skipped Orient. The friction was real. The interpretation was missing.

There are three common shapes the skip takes.

The first is the polish reflex. You read a passage, feel friction, and start tightening sentences. The friction may be prose-level — but it may equally be a structural issue showing up as prose friction. The scene’s job is unclear, the character’s POV obligation isn’t being met, a setup is missing. The friction is real; the location of the cause is somewhere else. Polishing the surface buries the structural signal under cleaner prose, and the next time you read the chapter, the friction will be back, harder to find, because now the surface is smooth.

The second is the tighten reflex. Cutting words feels productive. Word counts go down, red ink goes up, the session feels like it’s accomplishing something. But cutting words before Orient means you may be cutting the very prose that’s load-bearing for a structural beat you haven’t framed yet. The clearest version of this failure is the writer who tightens a long passage to a clean, sharp paragraph and then realizes three chapters later that the cut prose was carrying a setup the payoff now lacks. The tightening was pristine. The structural function was erased.

The third is instinct trust. Experienced writers have internalized Orient enough that it sometimes runs unconsciously — and sometimes the unconscious version is reliable. The trouble is that the writer can’t always tell the difference between I’ve Oriented automatically and I’ve skipped to Decide and called it Orient. Long drafts make this worse. By chapter twenty-two, your unconscious model of what an earlier scene was doing has been corrupted by everything that happened in chapters one through twenty-one, and the unconscious Orient is running on stale framing. The revision feels right. The result contradicts chapter four.

The forced-Orient move is simple and a little annoying. After reading a passage, before changing anything, write one sentence that names what the passage is trying to do at the scene, chapter, and arc level. If you can’t write the sentence, you haven’t Oriented. Don’t decide yet.

In practice, this turns margin notes from fix this into this passage’s job is X; the prose isn’t doing X because Y. The first half forces Orient. The second half feeds Decide. The single discipline — articulating purpose before authorizing change — is the move that turns a revision session from word-shuffling into structural work.

The slow-down rule, if you want a one-liner: if a revision session changed prose without changing your understanding of any scene’s job, you weren’t running a loop. You were polishing.

The honest concession: some writers have internalized story structure so deeply that they Orient unconsciously and reliably, and for them the forced sentence is friction with no added signal.

But most of us — even experienced writers — have patchy Orient, and the forced loop is most valuable exactly when you’re sure you don’t need it. The move is to notice the difference between unconscious Orient that’s reliable and unconscious Orient that you’ve stopped checking. The forced sentence is how you check: twenty seconds on the chapters where your instinct was already right, and on the chapters where it wasn’t, the cost of skipping it is the next three drafts.

Externalizing Orient — putting the framing in language outside your head, in margin notes or a working document or whatever scaffolding helps — is one way to keep the discipline honest. What matters is that it exists somewhere before the first change gets made; the form it takes is up to you.

The pass model schedules revision. The OODA loop describes what revision actually is. Writers who learn only the schedule keep skipping the step where craft happens.

The replacement is the loop. Watch yourself for the Observe-to-Act collapse. Force a one-sentence Orient before any change. Slow down by exactly the amount required to make every change structurally informed — no more, no less. The compound interest pays out across the draft because every change you make is now framed against the same accumulating model of the work, instead of being a series of disconnected reactions to whatever friction the last paragraph happened to produce.

Try one experiment in your next revision session. After reading a passage, before changing anything, write a single sentence naming what the passage is supposed to do. Notice how often you can’t. That gap — between what you’ve read and what you can articulate as its purpose — is the loop you’ve been failing to close. Closing it is the entire game. And when you’ve closed it everywhere — every scene, then every chapter — until a full loop turns up nothing left to change, the loop runs clean. That’s the closest thing you’ll get to the draft telling you it’s done.

Until next time, thanks for listening.

The adverb prohibition was never a rule. It was a Strunk & White nervous tic that became orthodoxy — and our prose got worse for it.

The prohibition isn’t entirely wrong. There’s a real craft problem buried inside it, and the rule was an attempt to solve it. But somewhere between the original target and the modern reflex, the advice generalized from watch this one specific bad habit to cut the entire grammatical class — and most working writers now run a global find-and-delete against any word ending in -ly without ever asking which words actually deserve to go. The result is prose that’s lost its sense of time, its voice modulation, and its precision.

So today I’m going to do two things. First, separate the bad habit the rule was trying to fix from the grammatical class the rule swept up by accident. Second, give you a diagnostic move that’s better than the prohibition it replaces.

The rule started somewhere real. To make the case I want to make, I have to first concede the case the rule was making.

The problem is the she said sadly pattern. Manner adverbs grafted onto dialogue tags to do emotional work the dialogue itself failed to do.

“I don’t think we should see each other anymore,” she said sadly.

That line is doing two jobs and failing at both. The dialogue isn’t carrying the sadness — there’s no fragmentation, no hesitation, no syntactic evidence that the speaker is in pain. The adverb is being asked to label what the line should have rendered. And the label has a specific cost: it makes the writer visible, gesturing at the emotion instead of putting it in the prose.

Compare:

“I don’t think we should see each other anymore.” She didn’t look up from the cup she was holding.

The dialogue and the body language do the work. The reader gets there without being told. The sadly was redundant if the line worked, and a patch over weakness if it didn’t — and either way, it didn’t earn its place.

This is real ground. The dialogue-tag adverb is, most of the time, a writer covering for prose that didn’t do its job. Stephen King’s famous line — the road to hell is paved with adverbs — was diagnosing exactly this pattern, and his diagnosis was correct. The rule was earning its keep. But it was doing that work on one specific habit, in one specific structural position. And the move that came next is where the rule went off the rails.

The prohibition that got encoded into craft orthodoxy didn’t say watch your dialogue tags. It said: cut adverbs. All of them. On sight. The original target was manner adverbs after dialogue attribution — and the rule, somehow, generalized to an entire grammatical class.

There are at least five categories of adverb the rule swept up. Only one of them deserves the blanket treatment.

Manner adverbs in dialogue tags. The original target. She said sadly, he said angrily. Almost always patches over dialogue that should have done the work itself. Cut these.

Manner adverbs outside dialogue. Sometimes redundant, often irreplaceable. He turned slowly and He turned are not the same sentence. The slowness is doing emotional, temporal, and tonal work the verb alone can’t carry. Treating the second as automatically better than the first is a craft failure in the opposite direction — purifying the prose by stripping out the specificity that made it precise.

Temporal adverbs. Eventually. Finally. Soon. Later. These do pacing work that no substitute does as cleanly. He came back to the question is a different statement than Eventually, he came back to the question. The second carries the weight of a span the first doesn’t — and the only way to render that span without the adverb is to add three sentences of intervening time. The adverb is doing the work of three sentences in one word.

Sentence-modifying adverbs. Admittedly. Honestly. Frankly. Presumably. These do voice work, especially in first person. They mark a narrator’s relationship to their own statement. I should have noticed earlier is a fact. Admittedly, I should have noticed earlier is a fact filtered through a narrator who’s conceding something to the reader — and that filtering is the entire texture of the prose. Cut these and you flatten interiority. The narrator stops sounding like a person with a point of view and starts sounding like an annotated box of facts.

Intensifiers — the precise kind. Barely. Scarcely. Narrowly. Exactly. These are arithmetic. She barely finished is a different statement of fact than She finished. The first reports that finishing was contested. Sweeping these out costs precision the prose can’t recover by other means.

And then the lazy intensifiers. Very. Really. Quite. Somewhat. Yes — mostly cut these. The prohibition was right about this category. But it’s the smallest of the five, and the rule’s broad application punishes the other four for the sins of this one.

That’s the shape of the failure. A rule against one specific bad habit generalized into a rule against five distinct grammatical functions. We threw out a structural class to fix a stylistic tic.

So here’s what to actually do when you find an adverb in your draft.

Don’t delete it. The question isn’t should this go? The question is: what is this adverb compensating for? The adverb is a diagnostic marker — a symptom pointing to something else in the prose that may or may not be working. Your job is to figure out which. There are three possible answers.

Nothing. The adverb is doing its own specific work — temporal, sentence-modifying, precise intensifier, or a manner adverb carrying fine-grained character work no substitute would render. Keep it. He turned slowly stays. Eventually she came back to the question stays. You found the adverb, you ran the test, the adverb passed. Move on.

The verb is generic. This is the case the prohibition was right about beyond the dialogue tag. Walked quickly is a sentence asking to be hurried, rushed, strode. The adverb is patching a weak verb, and the fix is upstream, not downstream. Replace the verb with one that already carries the modifier inside it, and the adverb usually falls out on its own. The deletion-on-sight approach gets the right answer here — accidentally, and for the wrong reason. The reason isn’t adverbs bad. The reason is the verb wasn’t pulling its weight. And knowing the reason matters, because when you make this fix you’re not just cutting an adverb — you’re upgrading the verb. That’s where the actual improvement happens.

The dialogue is weak. The original case. “I don’t know,” she said hesitantly is a line where the dialogue itself failed to render hesitation. The fix isn’t a different attribution — it’s rewriting the line so the hesitation lands without needing a label. Add a beat. Fragment the sentence. “I don’t know.” A pause. “I really don’t.” If you can’t get the dialogue to carry the feeling, the dialogue is the problem. Not the adverb.

Three answers, three different fixes — and none of them is delete on sight. The discipline is the pause before the delete key.

One honest concession. There are writers whose prose genuinely improved when they policed adverbs harder. King is the canonical case — On Writing is partly a confession about his own habit and the work he did to break it. For some writers, especially early on, especially in first drafts, the blanket prohibition is useful training wheels for a real problem.

But the question isn’t whether the rule was ever useful. It’s whether you’ve graduated from needing it. Most working writers have — and most don’t notice the rule has stopped earning its keep and started costing them precision, because it operates as a reflex now, not as a question. The honest move is noticing when you’re using a rule as a substitute for thinking. The diagnostic takes more thought than the prohibition does. That’s a feature, not a bug.

The prohibition was always a fix for one specific bad habit. We extended it to a grammatical class, and the prose got blander while the writers who promulgated the rule got famous for breaking it. Read King carefully and you’ll find adverbs everywhere his prose is doing serious work — temporal adverbs holding decades together, sentence modifiers filtering a narrator’s voice, precise intensifiers measuring a moment’s stakes. He never followed his own rule. And he was right not to.

So the next time you find an adverb in your draft, don’t reach for the delete key. Ask what it’s compensating for. Sometimes the answer is a stronger verb. Sometimes it’s a rewritten line of dialogue. And sometimes — more often than the orthodoxy admits — it’s nothing at all, and the adverb stays. Because it was never the problem.What you call a thing is never neutral. It’s the smallest unit of theme your book has. Use it.

Until next time, thanks for listening.

A few episodes ago, I told you about a moment in a short story I wrote called “Signal Zero.” A military sergeant gets ambushed by an alien intelligence — and inside that ambush, the system gives him a designation. It calls him Sentinel. And next to Sentinel, a number: Frame: Seven.

I didn’t say much about that moment in the episode. But it’s been bothering me ever since, in the productive way ideas bother you. Because what the alien system did, in that scene, is the smallest possible unit of theme. It chose a word. And the word was an argument.

Today I want to talk about naming. Not naming as in what should I call my fantasy kingdom — that’s a different episode. I mean naming as theme. The proposition that what you call a person, a place, a system, an event, is never neutral. Every name is a small thesis statement. And when you understand what your names are arguing, you can sharpen them. When you don’t, they argue without you.

Start with Ursula K. Le Guin and the Earthsea cycle. Le Guin built an entire magic system on the proposition that to know a thing’s true name is to have power over it — and that to give your true name to another person is the deepest possible act of trust. Wizards spend their lives learning the secret names of things, in a language that predates lying.

What’s interesting is that Le Guin doesn’t treat this as a gimmick. The true-name doctrine is woven into the moral architecture of the books. A wizard who uses a name to hurt has done a different kind of harm than one who uses a sword. To name a thing wrong is to misunderstand the world. To name a person without knowing them is to assume a power you haven’t earned.

So when the protagonist Ged finally tells his real name to a friend in the second book, that’s not a beat about intimacy. It’s a beat about the cosmology of the entire series. Names bind. Knowing someone’s name commits you. The plot of Earthsea is, in a deep structural sense, the question of what a person owes to the things they have named.

That’s the move I want you to notice. Le Guin didn’t decorate her books with fancy names. She made the act of naming into the thematic engine. Once you’ve done that, every name in the book is doing thematic work. There are no neutral nouns.

Now go to the opposite end of the spectrum. Cormac McCarthy wrote a novel called The Road about a man and a boy walking through a post-apocalyptic landscape. They are the protagonists. They are on every page. And neither of them has a name.

The man is the man. The boy is the boy. Other people they meet are the thief or the woman. There are no proper nouns for the people who matter most. There are barely any proper nouns for the places they pass through.

That’s not a stylistic tic. That’s a thematic argument. McCarthy is saying: in a world this stripped, names are a luxury that the world can no longer afford. Identity is reduced to function. The man is whatever this person is to the boy — protector, provider, dying body — and the boy is whatever this person is to the man — reason, future, soul. The withheld names universalize them. They become every father and every son. The book is doing what a parable does: refusing the specifics that would localize the meaning.

Now hold that against Le Guin, and notice. Le Guin makes naming the engine of theme by showing the act of naming, repeatedly, with reverence. McCarthy makes naming the engine of theme by refusing the act of naming, repeatedly, with severity. Both are using the same craft tool. Different argument, same lever.

This is the thing I want every writer to take away from those two examples. Whether you name something is itself a thematic statement. Whether you name them once or every chapter is a thematic statement. Whether you name them with care or with contempt is a thematic statement. None of these are neutral choices. None of them are stylistic preferences. They are all small claims about what your book thinks names are for.

One more example, and this one is the most useful for the kind of fiction I think most of us are actually writing — not parable, not high fantasy, but something somewhere in the contemporary literary middle.

Kazuo Ishiguro wrote The Remains of the Day. The narrator is an English butler named Stevens. And Stevens has a habit. He almost never uses people’s first names. The aristocrats are referred to by title. The other servants are referred to by surname or position. The American politicians are referred to by their offices. Even the woman he is in love with — and we, as readers, slowly come to realize he has been in love with for thirty years — is referred to throughout most of the book as Miss Kenton. Not Sarah. Not by any first name. Miss Kenton.

Ishiguro is using job titles and surnames as armor. Every time Stevens refers to someone by their title, he is performing a small act of emotional avoidance. The titles are how he keeps himself professional. They are how he keeps himself not in love. The whole book is, structurally, the slow realization that Stevens has named himself out of his own life. He has called everyone around him by their function for so long that he has come to believe his own function is all he is. Mr. Stevens, butler.

The moment in the book where Stevens slips and uses a first name — I won’t spoil which one or where — is the moment the entire psychological architecture cracks. A single proper noun lands like a shot.

That’s how powerful a name can be when you’ve withheld it for three hundred pages.

Which brings me back to Sentinel. Frame: Seven.

When I wrote that moment in “Signal Zero,” I wasn’t thinking about Le Guin or McCarthy or Ishiguro. I was thinking about how to make first contact land in a single sentence. But what I was reaching for, without naming it at the time, is the same craft tool all three of those authors are using. The system gave Voss a name that was true. Sentinel. Twenty-two years of military service, and the alien intelligence designated him for what he was doing when it arrived: standing guard.

And the system gave him a number. Frame: Seven. A category that means almost nothing to him in the moment, but which the reader will eventually understand is a measure of capability the system can see and Voss cannot.

Two designations. Two arguments about what kind of being Voss is. The first is profoundly seen. The second is profoundly mis-seen. The whole story of how Voss relates to the Integration that arrived that day is contained in the gap between Sentinel and Frame: Seven. Names doing thematic compression. Names as the smallest unit of meaning the story can carry.

So here’s what I want you to do. Pull up whatever you’re working on. Pick three names in it. Could be character names, place names, the name of an organization, the name a character calls another character, the name of a magic spell, the name of a piece of technology — any noun that took a choice.

For each one, ask: what is this name arguing?

If the answer is nothing — it just sounded right — that’s fine, but flag it. You have an opportunity there. You can sharpen the name into one that argues for something the rest of the book is also arguing for, and the book will tighten.

If the answer is something I didn’t know it was arguing — that’s the most interesting case. Sometimes the names you chose intuitively are smarter than you are. Don’t fix them yet. Look at what they’re claiming and ask whether the rest of the book is keeping that promise.

If the answer is I know exactly what this name is arguing — congratulations. Now check whether anyone else in the book uses a different name for the same thing. Because the disagreement between names is where theme lives.

Every name in fiction is an argument. What you call a person is a small claim about what kind of person they are. What you call a place is a small claim about what kind of place it is. What you call an event is a small claim about whether it can be understood at all.

Le Guin makes the act of naming sacred. McCarthy refuses it. Ishiguro hides behind it. My alien intelligence in “Signal Zero” deploys it as both a gift and a wound. Different writers, different stakes, same lever — and once you can see the lever, you can’t unsee it.

What you call a thing is never neutral. It’s the smallest unit of theme your book has. Use it.

Until next time, thanks for listening.

Romance writers have it easy in one specific way. The proposal is allowed to land. It can be the spine of the book. Everyone bought the book for it. The whole genre is a delivery mechanism for the moment one person asks another person a question and gets the answer they hoped for.

But what about the rest of us? What about a thriller, or a sci-fi epic, or a generation-spanning alternate history novel — where there’s a romance running through it, but the book is not about whether they end up together? The reader has known they end up together for two hundred pages. There’s no suspense in the question. The yes is in the bag.

So how do you write the proposal? The wedding? The first child? Any milestone the reader has been able to see coming since the first act?

That’s the craft problem today. And I’m going to read you a scene from Book Two of “Another Past,” where my protagonist proposes to a woman everyone in the book — and everyone reading the book — has known he was going to marry since chapter four of book one.

Brief setup. Paul Taylor and Jeryl Salaway have been together since high school. He has surprised her with a Hawaiian vacation for her twenty-first birthday. He has, in the days leading up to this moment, secretly arranged for both sets of their parents to fly out and meet them. He has asked her father for his blessing. He’s been carrying the ring for four days. Now they’ve spent the day on a chartered catamaran sailing from Maui to Molokini, with their families. The sun is going down. The crew is setting up dinner on deck.

The reader has known this is coming since the first chapter of Book Two. The question isn’t whether. The question is what does it cost him to choose, and what does the prose owe the moment when he finally does.

Just looking at her golden skin confirmed I was making a good decision. I knew I’d been granted an incredible second chance at life. I wanted to make the world better, but I could only do that with Jeryl by my side. I had left all the work at home, but that did not mean my mind stopped working. I knew two lines of research were playing out and that business would take a lot more of my time in the coming year. I wanted to make sure Jeryl knew what she meant to me before I got totally consumed with those efforts. That was one of the reasons I had chosen to propose on this trip.

The other was that I knew the world was reaching a turning point. The collapse of the Soviet Union was a catalyst for destabilizing the Mid-East and giving rise to fundamentalism in many flavors. The rise of fundamentalism led to a worldwide decline in the quality of life and the slow death of liberty. If I was going to change that trajectory, it needed to start now. I wasn’t strong enough to undertake such a challenge on my own. I wanted Jeryl with me.

Once we were anchored, the captain and crew began setting out our dinner on deck. A table was set up just in front of the cockpit and chairs were retrieved from the hulls of the catamaran. As the sun dropped to the horizon, the crew lit hurricane lamps and served dinner.

Fresh grilled Mahi Mahi with traditional local vegetables was presented on serving platters as white wine was poured. We had assorted fresh fruits for dessert. The sun slipped below the horizon, leaving us in its warm afterglow, and I decided this was the time.

I took Jeryl’s hand in mine as I tapped on my wine glass. I stood at the head of the table and smiled at everyone.

“Thank you all for coming and spending some time with Jeryl and me. As you know, I told Jeryl this was to celebrate her twenty-first birthday, which it is. It’s also something else.”

I stepped over next to her and dropped to one knee. Her eyes got big as I pulled the ring out of my pocket and held it up to her.

“Jeryl Alison Salaway, I love you with all my heart. Will you do me the honor of becoming my wife?”

Tears came to her eyes as she nodded, unable to say a word. She lunged into my arms, nearly knocking me over.

“Yes. Yes. Yes.” She managed to say before kissing me passionately.

Three things I want to pull out of that scene.

The first is what I think is the most important craft move in the whole passage, and you almost miss it because it doesn’t feel like a craft move. The proposal is the second half of the scene. The first half is Paul on the foredeck, watching Jeryl tan, thinking about geopolitics. He is mentally cataloging the collapse of the Soviet Union and the rise of fundamentalism and his own sense that the world is about to get worse. Inside the most romantic scene in the book, the narrator’s interior is doing macro-historical analysis.

That’s not a flaw. That’s the technique. When the outcome is inevitable, the suspense has to come from somewhere — and the place to put it is inside the protagonist’s reasons. Paul isn’t proposing because he loves her. He’s proposing because he’s about to spend the next decade of his life trying to push back against history, and he can’t do it alone. The proposal isn’t a romantic gesture. It’s a recruitment. The reader feels the weight of the moment because they’re inside a head that has reasons larger than the moment can hold.

The second thing. Notice the prose during the proposal itself. It is not poetic. There is no swelling lyrical paragraph. The sentences are flat and procedural. I took Jeryl’s hand. I stood at the head of the table. I dropped to one knee. Her eyes got big. This is the same writer who two pages earlier wrote a description of the morning that included “the warm sand on our feet” and “warm afterglow.” When the moment arrives, the prose backs off.

That’s deliberate. When you’ve spent the build-up doing the heavy emotional lifting — the foredeck reflection, the chaperone arrival, the day of sailing — the moment itself doesn’t need ornament. The reader brings the ornament. Your job is to not get in the way. Plain prose at the climax of an inevitable scene is almost always the right call. Lyrical prose at the climax of an inevitable scene is almost always reaching for an effect the reader has already supplied.

The third thing. Watch who else is in the scene. Both sets of parents. The boat captain. The crew lighting hurricane lamps. Paul has not staged a private moment. He’s staged a public one, with witnesses he had to lie to for four days to keep the surprise. That choice does enormous work. It tells you, without telling you, that this is a man who understands marriage is not a transaction between two people — it’s an entry into a system of obligation. The proposal with witnesses means something the proposal alone on a beach wouldn’t.

If you take one thing from this scene, take this. The romantic milestone in a non-romance is not the moment. It’s the architecture around the moment. The chaperones, the secret blessing, the four days of activities to keep everyone too tired to spill the surprise — all of that is what makes the moment land. The proposal itself is almost the easiest part to write. The hard part is everything that has to be true about the world for the proposal to feel earned.

Here’s a diagnostic for any inevitable-outcome scene you’re writing. Ask three questions.

One. What is the protagonist privately deciding before the public moment? Not what they say, what they decide. If you can’t name it, the moment hasn’t been earned yet — go back and write the private decision first.

Two. Who else is in the scene who doesn’t have to be? A proposal alone on a beach is the easy version. A proposal with both sets of parents at a dinner you secretly arranged is the version that does work. Scenes are bigger when more people are in them.

Three. When the actual moment arrives — the proposal, the kiss, the I love you — does your prose get plainer or more ornate? If more ornate, look hard at why. The reader probably doesn’t need the help.

The dirty secret of romantic milestones is that they are rarely about romance. They are about a protagonist deciding what kind of person they want to be, who they want next to them while they become that person, and what they’re willing to commit to publicly. Inevitability isn’t the enemy of emotional payoff. It’s the prerequisite. The reader is there for the texture. Spend the build on what the moment costs, not on whether it will arrive.

Next time, we’ll do something a little different — an episode about a single craft technique that runs across half the books on your shelf. Naming. What you call a thing in fiction is never neutral.

Until next time, thanks for listening.

Here’s a problem every writer in deep first person eventually runs into. Your narrator gets ambushed. Or jumped. Or shot at. Suddenly the camera is locked inside a person who can’t pull back, can’t pan, can’t see around the corner — and who, if we’re being honest, can barely see what’s directly in front of them, because their pulse is hammering and the windshield just took two rounds and there’s a hand on the back of their seat trying to tell them to do something they can’t quite parse.

How do you write that scene? How do you write a fight, a chase, an ambush — when your point of view is locked inside the head of someone who is, by definition, not in a position to narrate?

That’s the craft problem today. And I’m going to read you a scene from Book Two of “Another Past,” where my protagonist Paul Taylor — wealthy, well-protected, comfortable in his own life — gets reminded, mid-Friday afternoon, that competent enemies do not care how comfortable you are.

Quick setup. Paul has spent the morning fighting with the Air Force over a leaked materials contract. He’s angry, distracted, and being driven home by Tiffany — his security lead’s most senior agent — through Salt Lake afternoon traffic. He thinks his biggest problem today is the federal government. He’s about to find out his biggest problem is the people who staged a car wreck two intersections ahead.

Anger turned to fear, on the second to last day of spring break. Tiffany was driving me back from the University of Utah after a meeting with Professor Brighton. Traffic was heavy. We chalked it up to an early rush hour on a Friday afternoon. We were a couple of lights away from the highway, and an easy drive home, when the car in front of us ran a red light and was T-boned by oncoming traffic.

Tiffany stepped on the brakes, and I undid my seatbelt to get out and help. Suddenly, we were hit from behind and my head smacked into the back of the front seat.

“Shit! Hang on!” Tiffany stomped on the accelerator and swerved right to go around the accident in front of us.

“Paul, activate your alarm,” Tiffany commanded as she reached for the radio. High-pitched static squelched her signal as she keyed the mic.

I activated my alarm and looked behind us. The rear window had two small starbursts directly behind the driver. Two men stood behind a car at the intersection. A gun flashed.

“Shit, they’re shooting at us!”

Tiffany spun the wheel to get out of the line of fire.

“Get your seatbelt back on,” she commanded. I managed to get buckled in as she swerved down another street and then cut back toward the on-ramp for the highway.

“Are you okay?” Tiffany asked as she kept her eyes scanning the traffic around us while ignoring all the posted speed limits and any stop signs.

“Yes. Shaken up a little.”

She took the on-ramp at speed, and accelerated further once we were on the highway.

“Check yourself over. Make sure nothing got through.”

I checked myself as the radio squelch died. Tiffany grabbed the microphone again.

“This is Romeo-one, sierra foxtrot. I say again, this is Romeo-one, sierra foxtrot, over.”

There was a little crackle on the radio.

“Romeo-one, this is Romeo-castle. What’s your status? Over.”

“Romeo-one in transit. No pursuit evident.”

“Roger. Romeo Castle is calling a code. All other packages are in the castle. Romeo-two will meet you at fly-point one, over.”

She dropped the mic onto the seat and pushed the accelerator down further as we started the steeper climb up Parley’s Canyon.

“Okay, Paul. There is a pistol in the case under the seat. Get it out, check the safety and make sure you have a round chambered.” I did as I was told as she continued to talk. “Sanford will be meeting us in the parking lot just off the exit. I’ll pull up next to him. As soon as I stop, you get out of here and in with him. Keep the gun in your pocket. He’ll take you back to the house.”

So. A few things I want to pull out of that.

The first thing I want you to notice is what’s not there. There’s no description of the gunmen. No description of the second car. No camera-angle establishing shot of the intersection — no ten-yard view of where Paul is in relation to the threat. The narrator can’t see any of that, so you don’t get any of it. The only thing he sees of the actual attack is “two small starbursts directly behind the driver” and “a gun flashed.” Two visual fragments. That’s the whole gunfight.

That’s the craft move. In deep first person, you don’t widen the camera when chaos hits. You narrow it further. The reader’s instinct, your instinct — show me what’s happening — is wrong. Showing what’s happening dilutes the experience. What you want is to show what the narrator can actually perceive, which under threat is almost nothing, and let the reader fill the rest in.

The second thing. Watch what carries the scene once the bullets start flying. It’s not Paul. It’s Tiffany. Every line that moves the action forward is hers. Hang on. Activate your alarm. Get your seatbelt back on. Check yourself over. There’s a pistol in the case under the seat. Paul is reduced to two functions — I did and I checked — and the occasional terrified observation. The action is being narrated to him, not by him.

This is the trick I want every writer to take away. When your first-person narrator is in over their head, give them a competent ally and let that ally drive the prose. The reader doesn’t need the protagonist to know what’s happening. The reader needs someone in the scene to know — and the protagonist’s job is to react to that someone. Tiffany becomes the reader’s compass. Paul becomes the reader’s body. Together they can carry a scene that neither of them could carry alone.

The third thing. Look at the sentence rhythm. Tiffany stepped on the brakes. I undid my seatbelt. Suddenly, we were hit from behind. My head smacked. These are short. Subject-verb-object. There are almost no subordinate clauses in the action sequence — and the few there are show up only when the danger has receded, when Paul has time to think again. When the threat is acute, the prose gets blunt. When the threat lifts, the sentences breathe out. The pulse of the scene is in the syntax.

Here’s the thing I’m still not sure about. There’s a real risk in handing off the action to a competent NPC — your protagonist can come across as passive, even cowardly. I think it works here because Paul is supposed to be out of his depth. He’s a graduate student with a billion-dollar company; he’s never been shot at. The competent ally is the realistic answer. But if you tried this with a protagonist who’s supposed to be the most dangerous person in the room, the same technique would gut your character. So this isn’t a universal law. It’s a tool that fits a specific shape of story.

Here’s the diagnostic. Open whatever fight or chase or ambush you’re working on. Count two things. One: how many sentences run over ten words. Two: how many of the action verbs belong to your POV character versus someone else in the scene.

If too many sentences run long, the prose is moving slower than the events. Cut. If your POV character is doing all the verbs, your scene is probably too clean — too rehearsed, too in-control for what’s happening. Hand half of those verbs to someone else. Let the protagonist receive instructions, react, fail to keep up. Then read it aloud. If your mouth gets ahead of your eyes, you’re close.

The fantasy of the action scene is the protagonist who sees everything, knows everything, moves perfectly. That’s a movie’s job. On the page, in deep first person, the more honest scene is the one where your narrator can barely keep up. Where the windshield takes two rounds before they understand what they’re looking at. Where a calmer voice has to tell them what to do next.

When the bullets are real, your narrator doesn’t get to be the hero of the prose. They just get to live through it. And that’s almost always the better scene.

Next time, we’ll talk about the opposite problem — the moment everyone in the book has been waiting for, where the outcome is inevitable, and the only question is whether the prose can carry the weight of arrival.

Until next time, thanks for listening.

I was seventeen and it was past midnight and I had school in the morning and the book I was reading — Ender’s Game, borrowed from a friend who’d said “just read it” with the intensity of someone trying to share something they couldn’t explain — had done something to me I didn’t have vocabulary for yet. It wasn’t the plot. My friend had spoiled the twist without realizing it, so I’d known the shape of things going in. It wasn’t escape; my life at seventeen wasn’t anything I needed to escape from. What had happened was something else: I had spent three hundred pages inside a child’s mind that was smarter and more isolated and more desperately trying to prove it was sufficient than any mind I’d personally inhabited, and somewhere in those pages I had found something I’d never found anywhere else. The experience had a specific texture — the slight loosening of a knot I hadn’t known was there. The feeling, and I want to name it precisely, of not being the only person who had felt exactly like this, delivered to me by a character who didn’t exist, written by a person I’d never met, thirty years before I read the book.

That’s the phenomenon. That’s what this essay is actually about.

The reader’s side of this transaction is harder to articulate than it appears, partly because we don’t talk honestly about what’s happening when we read. The official account — stories build empathy, they instruct, they entertain — isn’t wrong exactly, but it’s not the thing. It’s the catalog description for an experience that isn’t like other experiences. What I mean by that: when you’re at 1am and you can’t put the book down even though you have to be functional tomorrow, the reason is not that you’re being educated. The reason is that the story has opened an interior room you recognize but have never been in before, and you’re not ready to leave it yet.

The two things stories do that nothing else does — and I’ve never found them substitutable — are these. First: they let you inhabit a consciousness that isn’t yours without losing your own. Not escape. Expansion. What you’re doing inside a novel isn’t becoming someone else; you’re remaining yourself while simultaneously running on a different person’s premises, wiring, and prior damage. After a week inside a particular character’s perspective, you have access to a range of human experience that would have taken real time to accumulate through living, and which living might never have delivered at all — because you will never be a nineteenth-century governess, or an astronaut on a failing ship, or a child soldier in a satellite war, and now you have some working knowledge of what those interiors feel like from the inside. This is not vicarious experience in the diminished sense that phrase usually carries. You return to your own consciousness with more room in it than you had before.

The second thing: stories allow emotions to be felt at full strength. This sounds small and isn’t. Real grief comes with defense mechanisms — you can’t fully feel the loss of someone you love at full intensity for more than short intervals, because full intensity is unsustainable and the psyche protects itself. Fictional grief has no such protection, because the stakes aren’t real and so the defenses don’t trip. When a character you’ve spent three hundred pages with dies, the grief that arrives can be felt at its actual size, unmanaged, unreduced. I have cried at fictional deaths with more emotional completeness than I’ve cried at some real ones. The story makes a safe-enough container that you can finally feel the thing at its full dimensions. That’s not weakness; that’s what the medium is for. When Ender stands at the end of that book, having been exactly what the adults needed him to be and learning only then what it cost — what I was feeling at seventeen wasn’t pity for a fictional character. It was something I recognized about the specific shape of being used well by people who thought they were protecting you. The book had given me access to that feeling, complete and full-size and survivable, and I didn’t have it on my own yet.

The author’s side is different, and it’s worth being honest about both what’s valuable in it and what’s less flattering.

Writing a story is not reading one from the inside. When I’m working on a scene — say, Malachi watching the banks of the Suez Canal go by, letting Set’s territorial resonance slide past like a stranger’s gaze — I am not illustrating something I already understand. I am finding out what I think. The story isn’t the product of the thinking. The story is how the thinking happens. This is the specific utility of fiction that I can’t replicate by journaling or by conversation: the requirement that it be concrete, that an actual character in an actual moment do an actual thing, forces my understanding to become precise in ways that abstraction never demands. I couldn’t have articulated what Malachi’s worldview actually is — what it’s correct about, what it’s categorically unable to see — until I watched him miscalculate Lyssandra. The scene told me what I thought. I didn’t bring the thought to the scene.

There’s a satisfaction in building a system where all the parts eventually mean something — the planted detail that pays off, the character who seemed decorative turning out to be structural — that I’ve only ever felt in writing. It has something in common with mathematical elegance: the sense that the shape of the thing is right, that it couldn’t have been otherwise. I won’t pretend the less flattering motivations aren’t also present. The desire to be seen. The desire to put a version of your understanding into the world that persists after you. The wish, which is almost too honest to write down, to be remembered. These aren’t shameful; they’re just not the reasons I give in interviews. Naming them honestly doesn’t make writing mercenary. It makes it human. Every serious writer has them. They’re not the engine, but they’re part of the fuel.

What happens when a story works — when reader and writer actually meet across the gap — isn’t communication in the ordinary sense. A text message communicates. What stories do is closer to recognition. The reader opens an interior room they’ve always had access to but never fully mapped, finds writing on the walls, and understands that someone else has been in this room. Not by accident — they were in this room because they were trying to find you. Years may have passed between the writing and the reading. The author may be dead. It doesn’t matter. The recognition is immediate: someone has been exactly here, felt exactly this, and decided to mark the walls so you’d know. That’s why oral traditions preceded writing. That’s why the campfire story and the Netflix series are doing the same thing at vastly different scales — both are someone trying to say, before we all go back to our separate interiors, here is what I found in mine. Does any of this match?

What I’m trying to do in Technomancer and Another Past is narrower than that general account. The interior room I’m trying to share is a particular one: what it feels like to be a person who thinks in systems discovering that systems don’t reach all the way down to what matters. Finn Miller can map the nodes, trace the composite paths, model the energy distributions — and keeps running into the wall of a power that requires relationship, not analysis. Paul Taylor knows the history and keeps finding that the future he knew is no longer the future that exists, and the gap between what he expected and what has happened is where he actually has to live. The recognition I’m hoping for is from anyone who has ever been genuinely competent and discovered that competence wasn’t the whole answer — who has understood everything correctly and still missed the point. That room is probably not unique to me. I suspect you’ve been in it.

Until next time, thanks for listening.

The problem had a very specific shape, and I found it by running the math.

Partway through Book 2 of the Technomancer series, I’d established that one day in the realm of Elysia corresponds to roughly π days on Earth — 3.14 to one. I chose π deliberately: it’s irrational, it never repeats, it signals a system operating on different terms than the ordinary world. It felt right in conception. Fourteen chapters later, Pamela — an intelligence analyst on the Earth side of the story — is in a scene I’d written as taking place during the pre-inauguration period, the weeks when a new president-elect’s transition team is vetting appointments and nothing is confirmed yet. I went back and calculated the actual Earth date using the chapter’s Elysia day count and the formula I’d established. The result was unambiguous: we were past the inauguration. By more than a week. Every reference to pending confirmations, to the transition team still operating, to McAlester being “vetted” rather than installed — all of it was wrong.

I had three options. Change the ratio. Change the inauguration date (constitutionally fixed; not a serious option). Or accept what the math was telling me and revise the political language. I kept the rule. And here is the thing I didn’t expect: the rewritten version is better. A tax evasion discovery against a sitting National Security Advisor is a far higher-stakes event than the same discovery made against a nominee. The π days rule, by being inconvenient, forced the scene to become more dangerous. It gave me a story I hadn’t planned.

That crisis is what I actually mean when I say “tracking story timelines.” Most craft advice treats it as a continuity problem — keep a spreadsheet, check your dates, make sure your pregnant character delivers at the right month. That part is real and genuinely mechanical, and getting it wrong produces a specific kind of reader embarrassment. The mechanical problem has solutions: index cards, spreadsheets, a document with a column for Earth dates and a column for Elysia dates and a formula running between them. I built exactly that for Technomancer. But the continuity problem is only the surface of a harder question, which is how the reader experiences time — not whether your dates add up, but whether a decade feels like a decade, whether a morning that takes forty pages justifies its length, whether the reader feels the weight of what has passed when you tell them it has.

These two problems look like the same problem. They’re not. The mechanical one has a solution: be diligent. The craft one has a discipline: every choice about what to show versus what to summarize is a small act of trust between writer and reader. Every skipped period of time is a request — trust me that nothing worth your attention happened here. The reader can feel when that request is false.

Another Past makes this distinction impossible to ignore because the problem is structural. Paul Taylor isn’t just living in a timeline — he’s in conflict with one. He died in a lab explosion and came back fifty-four years earlier in his own body, with everything he’d learned and lost intact. He knows history. Except that knowledge is expiring, progressively and irreversibly, because his interventions are changing things. He keeps a notebook — a physical notebook, with dates and events from what he remembers as “his first trip through” alongside columns for what happened this time. I gave him that notebook because he needed it. He can’t predict stock prices anymore; his disruptions moved those markets years before the companies he remembered ever peaked. He prevented the Challenger explosion — knew the date, knew the O-ring failure, knew the cold morning of January 28, 1986 in a way that gave him enough leverage to change it. “The paths were definitely diverging,” he notes, reading through those columns. “Even if only in small ways so far.”

The craft question his situation raises is one I didn’t have an answer to going in: how do you write a character with foreknowledge without making every scene pure dramatic irony? The instinct is to let the reader watch him see the future and let that double vision carry the weight. But foreknowledge that never fails is omniscience, and omniscience is structurally inert — it can’t be surprised. What makes Paul’s situation interesting is precisely the moments where the foreknowledge fails, where history has moved, where his confidence is a liability. The notebook is not a competence document. It is a reckoning. He is sitting with evidence that the future he knew is no longer the future that exists, and the difference between what he expected and what has happened is the place where the story actually lives. That gap — between the timeline he carried and the timeline that’s actually unfolding — is where I learned something I couldn’t have gotten from the Technomancer spreadsheet: knowing your dates isn’t the same as knowing what your dates mean. Paul knows exactly what day it is. He is still wrong about what that day will bring.

There’s an asymmetry between how an author lives in a manuscript’s timeline and how a reader experiences it that produces a specific kind of failure. I spent months in Book 2 of Technomancer, accumulating a fine-grained sense of how much time had passed for each character. The reader experiences the book in the time it takes to read it — days, not months — and the texture of elapsed time that feels obvious to me has to be built into the prose through accumulated detail, through the physical evidence of change, through characters who feel the weight of what has passed in ways that are visible on the page. The π days rule forced a specific version of this into visibility. At the Book 2 close, Finn and Elara are in the immediate aftermath of the same events, but “immediate” means something different to each of them: he’s two weeks out; she’s four or five Elysia days out. They are asymmetrically wounded by the same story. That asymmetry doesn’t resolve itself just because I know about it. It has to be rendered so the reader feels it.

What both of these books have taught me about time is that how a writer handles it is a statement about what the story believes time does to people. Does it heal? Compress? Bury? The answer shapes everything — pacing, chapter structure, what gets a full scene and what gets a sentence, where the story pauses to let the reader feel the weight of what has passed. For Paul, time is a palimpsest: the original is still visible under the revision, and the story lives in that gap. For Finn and Elara, time is architecture — they are building toward each other across a differential neither of them fully controls, and the structure has to bear the weight of that imbalance before it can carry them anywhere. In both cases, time isn’t neutral infrastructure. It’s the material the story is made of. The continuity spreadsheet is just how you make sure you’re using it correctly.

Until next time, thanks for listening.