So why am I revisiting the topic now?
The short answer is it’s Joshua Palmatier’s fault.
Maybe I should give you the long answer.
Back in the early spring — it feels like a hundred years ago now — I wrote a pair of Writing-Tip Wednesday posts about dialogue and dialogue attribution. The post about attribution was particularly involved and long, and, to my mind, was one of the best writing advice posts I wrote this whole year.
So why am I revisiting the topic now?
The short answer is it’s Joshua Palmatier’s fault.
Maybe I should give you the long answer.
I have just finished writing my short story for the DERELICT anthology, the collection of stories Joshua and I are co-editing for his imprint, Zombies Need Brains. That’s right: I’m editing the anthology (as David B. Coe) and writing a story for it as an anchor author (as D.B. Jackson). The story is set in my Thieftaker universe and it’s titled (for now) “The Wreck of the Sarah Mohr.”
Writing for an anthology I’m also editing is something I’ve done with the other anthologies I’ve edited for ZNB, and each year Joshua has been pleased with my stories, except with regard to my dialogue attribution. He doesn’t like dialogue tags — “he said,” “she asked,” etc. I mean, he really doesn’t like them. And so every year, he goes through my stories and marks a bunch of them that he’d like me to cut.
Fine.
But not this year. This year, with this story, I was determined to preempt his edits. As I said in my post back in April, I am not one of those writers/editors who feels that all writing tags ought to be cut. I believe good dialogue attribution demands a mix of simple attribution, use of mannerism, gesture, and description to indicate who is speaking, and a few lines of straight dialogue with no tags. (I do suggest you go back and read that attribution post from the spring.) But for this story, I tried to use as few tags as possible.
And I found that imposing this limitation improved my storytelling. I really hate it when Joshua is right, so this is hard for me to admit. But it’s the truth. In trying to avoid the use of direct dialogue tags, I had to find other ways to keep clear in my readers’ minds who is speaking at any given time. In part that meant finding different ways to describe what my characters are doing or feeling. That, though, can carry risks. Too much description of that sort can sound clunky, and overuse of character mannerisms can make them seem twitchy.
So, the other thing I did was trust my dialogue more. In effect, I allowed my characters to speak for themselves, and I trusted my reader to be able to follow the course of their interactions. Now, when I say I trusted my reader, I am quoting an old editor of mine who used to say that whenever he thought I was explaining too much. “Trust your reader to understand,” he would scrawl in the margin. And what he really meant was, “Trust yourself. You’ve done the work. You’ve introduced your characters and established your narrative. Trust in that work and stop slowing down to explain stuff.”
“Trust your reader” equals “Trust yourself.”
So with this story, I trusted myself.
Here is a quick sample from the story:
Kannice sat in the chair adjacent to his. “I didn’t expect to see you here so early.”
“I had a good day.”
Her eyes fell to his jaw, which, no doubt, had already begun to darken. Ethan meant to heal himself before entering the tavern.
“Why do all your good days consist of beatings at the hands of Sephira Pryce’s ruffians?”
He grinned, winced. The skin around the bruise felt tight and tender. “In fairness, not all of them do. You and I have passed some very pleasant days without laying eyes on Sephira or her toughs. Or anyone else, for that matter.”
A reluctant smile crept over her features. “You found the gems you were seeking.”
“Aye, and was paid handsomely for their return.”
“And now you have a bit of coin to spend on me?”
“On you, on my rent, on the excellent chowders served here at the Dowsing Rod.”
“Well, I’d like a bit more spent on me.” She pulled from her bodice a folded scrap of paper, and held it out for him. When he reached for it, she pulled it back beyond reach. “Promise me.”
His smile returned. “I promise that all the coin—” He frowned. “Or at least most of the coin I make as a result of whatever you’ve scrawled on that parchment you’re holding, will be spent on you.”
Eyes narrowed, she handed him the paper. He unfolded it and read what was written in her neat, slanted hand.
There is not a single dialogue tag in that exchange. Yet you should have been able to follow the entire conversation, knowing at all times who was speaking, and understanding as well the dynamics at play.
I would suggest that you give this a try as well. Write a scene, or a story, or a chapter, and try not to use a single direct dialogue tag. If you hate the way it comes out, so be it. But you might find, as I did, that it does unexpected things for your prose.
Look, I have not allowed Joshua to lure me to the dark side. I still believe there is a place for dialogue tags in our writing. And I do use a few in the course of this story. Nevertheless, in forcing myself to use as few of them as possible — to avoid “he said,” “she said,” “he asked,” “she asked,” whenever I could — I actually improved the flow of my story and made it more concise.
Which is good, because in spite of this I managed to go over the word limit just a little. I guess Joshua will ding me on that…
Keep writing!

For the Winds of the Forelands series (Rules of Ascension, Seeds of Betrayal, Bonds of Vengeance, Shapers of Darkness, Weavers of War) , I created what is without a doubt the most complex “calendar” I’ve ever undertaken for any project. For those of you not familiar with the world, I’ll give a very brief description. The world has two moons, Ilias and Panya, the Lovers, who chase each other across the sky. Each turn (month) has one night when both moons are full (the Night of Two Moons) and one night when both moons are dark (Pitch Night). Each turn is also named for a god or goddess, and so each Night of Two Moons and each Pitch Night has a special meaning.
I did something similar for the Islevale Cycle novels (Time’s Children, Time’s Demon, Time’s Assassin). In this world there are two primary deities, Kheraya (female) and Sipar (male), and the calendar is structured around them. It begins with the spring equinox — Kheraya’s Emergence, a day and night of enhanced magickal power and sensuality. The spring months are known as Kheraya’s Stirring, Kheraya’s Waking, Kheraya’s Ascent. The summer solstice is called Kheraya Ascendent, a day of feasts, celebration, and gift-giving. This is followed by the hot months of summer: Kheraya’s Descent, Fading, and Settling.
And I’ll start with this: Joshua and I are generous readers. We will read an entire story, even when it’s pretty clear halfway in (or a quarter in…) that the story probably won’t make the cut. Your goal as a writer is to sell us a story, obviously. But really your goal is to make us consider your story on your terms. Here’s what I mean by that: We are expecting to get somewhere between 300 and 400 submissions, for a total of 6 or 7 slots. (Last year, for GALACTIC STEW, we received 409 and selected 7.) Read those sentences again; I’ll wait.
Then there are people like me. Some books, I outline in a good deal of detail. The Thieftaker novels demand preparation of this sort because I am tying together fictional and historical timelines, trying to make my story meld with established events. The Islevale books — time-travel epic fantasies — should have demanded similar planning. But for reasons I still have not fully grasped, all three books defied my efforts to outline. I simply couldn’t plot the books ahead of time. I tried for months (literally) to outline the first book, Time’s Children, and finally my wife said, “Maybe you just need to write it.”
That’s what I did, and the result was a first draft that needed extensive reworking. When I began book II, Time’s Demon, I ran into the same problem. I didn’t even try to outline Time’s Assassin, the third and final volume. I knew it would be a waste of time. All three books needed extensive editing, more than I usually need to do. But they wound up being far and away the finest books I’ve written.