When the writing stops
For a few weeks now the story writing has stopped. Not slowed, stopped. I open the file, read the last paragraph I wrote, and nothing comes. I feel slightly brain dead. And the reflex, the one I suspect most people who make things share, is to push harder. Don’t stop. Stopping is how projects die.
I’ve come round to thinking the reflex is wrong, and that getting it wrong is how the block goes from a fortnight to a season.
Writer’s block isn’t one condition. It’s at least four wearing the same coat. There’s the block that’s really an undecided story, where the sentences won’t come because the scene doesn’t know what it’s for, and no amount of grinding will fix a structural problem you’re trying to solve at the level of the sentence. There’s the block where your standards have outrun what you can currently do, so the first attempt looks so bad you won’t start. There’s the block that’s just cost. The next thing that must happen in the story is expensive, someone must be hurt or something must be lost, and you’re stalling because you don’t want to spend it.
And then there’s the one I’ve got, which is depletion. Nothing’s wrong with the story. I’m just empty.
The trouble with depletion is that it disguises itself as the other three, and it responds to discipline by getting worse. It is worth being precise about what’s drained, because it isn’t “writing” as a whole. It’s one specific faculty: the generative act. Making new sentences that didn’t exist a second ago, holding a whole scene’s shape in your head while you choose each word. That’s the expensive mode. And it turns out to be the same mode I’ve been running flat out on everything else.
Because the writing was never the load. This year I’ve been migrating a suite of astronomy software into Azure, an environment I’d never touched. Nine applications, not one, each needing its own degree of security and vulnerability management. The codebase has gone from sixty thousand lines to nearly a hundred and thirty thousand. And learning a new cloud at production scale is the most cognitively expensive thing I know how to do, precisely because none of it is automatic yet. In C# I have decades of experience doing the work below conscious effort. In Azure, every identity decision and network boundary is deliberate, novel, and consequential. That’s the same faculty drafting uses, at full draw, all day.
I wasn’t running two budgets, one for code and one for story writing. I was running one, and both projects were billing it.
And then there’s the sky. I test the software locally every clear night, and Australian winter is generous with clear nights. Depletion isn’t caused by expenditure. It’s caused by expenditure without replenishment, and the thing that replenishes it - is sleep. Every night I’m up at the telescopes is a night the deficit doesn’t clear. String a few together, under an unfamiliar-cloud cognitive load, and “slightly brain dead” isn’t a warning sign. It’s just arithmetic.
Which is oddly the best news in all of this. Because it means nothing is wrong with me and nothing is wrong with the book. I’m doing one genuinely enormous thing while structurally under slept, and the story writing is the first thing to switch off because it’s drawing on exactly the reserve the day job has already spent.
So, here’s what I’m doing to do instead of pushing, and why I think it’s the right call.
I’m not stopping. Stopping is how a project gets a flinch. You avoid the file, and reopening it costs more than writing in it ever did. But the daily contact doesn’t have to be creative. Most of the work in a writing life isn’t. Continuity auditing. Running the story linter (I am a C programmer from way back) and clearing what it flags. Reconciling what the chapters did against the plan. Reading my own back-catalogue with an editor’s eye rather than an author’s. That work is real, it advances the book, it feels like being a writer, and it costs a fraction of what drafting does, because it’s recognition rather than creation. Recognition is nearly free when you’re tired. Creation isn’t. So, for the next stretch I’ll keep my hands on the material and stop asking it to produce anything new.
The fear underneath “I don’t want to stop” is that the pause becomes permanent. It doesn’t. Creative capacity isn’t a character trait, it’s a resource level, and resource levels recover the moment you stop overdrawing them. What breaks writers isn’t a few weeks of maintenance work. It’s grinding through depletion, producing work below their own standard, and then quietly losing faith in the project.
If you’re where I am, flat, avoiding the page, certain that stopping means failing, I’d offer you the same advice I’ve had to tell myself. Look at the whole load, not just the writing.
Count the clear nights or whatever keeps you busy at night. Count the things that are novel enough to demand your full attention and give nothing automatic back. Then be honest about whether you’re blocked or simply spent.
Because those want opposite treatments. And there’s nothing wrong with you.