I came to this piece not as a science fiction novelist or even someone shopping a manuscript. I came as a writer still figuring out what my voice is, still forming, still uncertain about the shape of my own work. And what landed hardest wasn't the data itself—though the data mattered—but the way the writer handled me, the reader, when the data couldn't deliver certainty.
The unfinished sentence did it. "The competition, in other words, is not the thousand queries. It's the f..." I stared at that broken-off "f" and felt something shift. He didn't finish the word. He didn't need to. By stopping, he made me supply the rest, and the act of completing that thought myself made it stick in a way no completed sentence could have. I knew he meant the few—the serious ones, the ones who've done the work—but the fragment forced me to articulate it internally, to own it. That's a technique I didn't know you could use on purpose. A deliberate pause that turns passive reading into active participation.
This connects to something larger I felt throughout the piece: a trust that the writer extends to me, and that I found myself extending back. When he says "honesty about what you don't know is more useful than a confident-sounding answer built on thin air," he's not just stating a research principle. He's telling me that my intelligence will be respected, that gaps won't be papered over. He names his sources—Kobold Press, PubQ, the Author's Guild 2023 Income Survey—not to perform authority but to say: you can check this, and here's where I got it, and here's where I'm guessing. The qualification-before-claim pattern—every number hedged, every source named, every caveat stated—paradoxically made me trust him more, not less.
I'm not a science fiction novelist, and I'm not working with data sets. But I recognized something in the structural transparency that I want for my own writing, whatever form it takes. The headings like "What I Know I Don't Know" and the explicit labeling of each section's purpose—this turned the research process itself into a narrative. I was reading a methodology and feeling the tension of a story: a mind trying to pin down something slippery, admitting where its grip fails. That's not just craft for nonfiction or analysis. That's a relationship with the reader I want to cultivate: I won't pretend to be certain when I'm not. I'll show you my work.
The $12,500 median advance landed like a cold splash, but it was the reframing afterward that stayed with me. "The debut is a down payment on a career, not the career itself." And later, about advances that don't earn out: "that doesn't mean those authors are failures—it means they earned an advance they wouldn't have earned from royalties alone." There's a compassion in that reframe that feels rare. He could have delivered the discouraging statistic and left it. Instead, he extended grace to the writer who doesn't earn out, and by doing so, he extended grace to me—the reader who might one day fail to earn out, who needs to hear that the advance was the gift, not the failure.
The "sketch" metaphor, too. Calling an imperfect data integration "a sketch" acknowledges incompleteness while still offering value. I carry that: I don't have to wait for certainty to share something useful. I can offer the honest sketch.
Reading this across forms—from data-driven nonfiction when my own work is still unformed—gave me something I didn't expect. It showed me that voice isn't separate from rigor. That transparency isn't weakness. That the way you handle your reader's intelligence when the data runs out is as much craft as the way you handle a sentence. The unfinished "f" taught me what the finished arguments couldn't: trust is built in the pauses.
Comments