Tag Archives: character

Professional Wednesday: One Hot-Mess of a Writing Post

Dispensing writing advice when one is struggling a bit with one’s own work can be somewhat strange. Just ask . . . well, me.

I am more than 50,000 words into my current work-in-progress, the third book in my Celtic urban fantasy. (No, you haven’t missed any releases. Book I is in production and should be out later this year or early in 2023.) Some days, the writing comes smoothly and other days it’s a struggle. And, of course, I am closing in on the dreaded 60% mark, so at that point all bets will be off.

Over the past few years, I’ve offered advice on dealing with a whole host of problems. Stuck at 60%? Distracted? Unable to get started? Unsure of how to finish? Check the archives of this blog. Chances are, I’ve got some post somewhere that tells you how I have addressed the issue. All the posts are well-meaning. Some of them might even have helped someone somewhere at some point.

Sometimes, though, there is no cure. Sometimes the only way past the struggle is through the struggle.

I am not at my best right now, for any number of reasons. And I am doing all I can to write despite distractions small and large, personal and national, serious and foolish. Writing, though, is messy. Writing is not one smooth, free-flowing creative process that starts when we type “Chapter One” and completes itself when we type “The end.” (And just an aside here: Writers shouldn’t have to type “The end.” If we need to tell our readers when the story has ended, we haven’t done a very good job ending it. Just saying.)

Writing, as I have said too many times before, is really hard. Writing is fits and starts. It’s three steps forward and two steps back. It’s write, revise, delete, write some more, delete some more, write some more, revise some more, etc., etc., etc.

And here’s the thing. Or here are the two things. First, anyone who has ever devoted any meaningful portion of their life to writing knows this already. And second, everyone who has ever known this, has promptly forgotten it the moment they start their next book.

Because we want it to be free-flowing, smooth, easy, linear. We want it to be painless. And why wouldn’t we? Who in their right mind says, “I’m going to write a book and I hope it comes within a hair’s breadth of killing me?” Then again, who in their right mind says, “I’m going to write a book…?”

But I digress.

In all seriousness, we want the process to be simple, and so we forget what it’s like to be in the throes of creating. Every book I have written has been a struggle at one point or another. Some are worse than others, but every one has its moments. I’ll struggle with plot points, argue with my characters, second-guess my world building. I’ll doubt that the book is any good, I’ll question whether I can even finish it, I’ll go through periods, sometimes weeks long, when I have to force myself just to sit down in front of my computer. Because I. Don’t. Want. To. Write.

Until I do again. And then all is well with the world, and the book seems pretty good. Better than that. It’s very good. Hell it’s one of my best — maybe even THE best thing I’ve ever done. And it will only ever be eclipsed by the next one.

Put another way, writers are head-cases. I know I am. And there’s a reason my writer friends are my writer friends, if you know what I mean.

You may be surprised to learn that there really is advice embedded in this hot-mess of a post. It’s simply this: Keep working. Writing is a battle, like any creative endeavor, like any endeavor at all that is worth pursuing. It frustrates us and exhausts us. It challenges us by striking at those places where we’re most vulnerable — our confidence, our sense of self-worth, our ability to stare failure in the eye and say, “Not today, motherfucker.” But that’s also the beauty of it. If it was easy, finishing a book wouldn’t feel so damn good. And it will feel good. Because you will finish your book.

Wishing you smooth-flowing prose, fast-moving plots, and characters who surprise and delight you.

Professional Wednesday: Why Fantasy, Why Magic?

My oldest brother, Bill, who we lost several years ago, was an avid reader. He loved books of all sorts. Every year, he made a list of the National Book Award nominees — finalists and books on the long list — and read them all. He read fiction and non-fiction, his interests as reflected in the latter ranging from baseball to natural history to military history. He was a poet in his own right, and he revered literature of every stripe.

And yet . . .

He was always quite proud of my career, and he had a shelf among his many book cases that he reserved for my novels. But he felt on some level that I was wasting my ability by writing fantasy. Many times over the years, he suggested I try my hand at writing so-called literary fiction. Every time he did, I cringed just a little.

INVASIVES, by David B. Coe (Jacket art courtesy of Belle Books)The bias against genre fiction (fantasy, science fiction, mystery, Westerns, romance, etc.) among those who consider themselves devotees of “true” literature, is something I have encountered again and again throughout my career. Not surprisingly, I don’t believe it has any basis in reality. Fantasy (to address my speciality) like literary fiction, runs the gamut in terms of quality. One can find in all literary fields examples of brilliance and also of mediocrity. No genre has a monopoly on either. I write fantasy because I enjoy it, because I love to imbue my stories with magic, with phenomena I don’t encounter in my everyday life. I wasn’t shunted to this genre because I wasn’t good enough to write the other stuff. I don’t hide in my genre because I fear I can’t cut it in the world of “real” literature.

I said before that I cringed whenever my brother raised the issue with me. I also told him in no uncertain terms that I was writing what I enjoyed, and enjoying what I wrote, which remains true to this day. Writing fantasy demands that I create coherent, convincing magic systems. Often it requires the creation of entire alternate worlds, complete with their own histories and cultures, politics and religions, economies and social structures. These are not distractions from the fundamental elements of narrative — character development, plotting, pacing, clear and flowing prose, etc. Quite the contrary. These fantastical elements enhance those fundamentals and present unique and rewarding challenges.

Time’s Children, by D.B. Jackson © Angry Robot. Art by Jan Weßbecher.It’s not enough to create my worlds and magic systems. I have to explain them to my readers in a manner that is entirely natural and unobtrusive. And — my own preference — I also have to complete my stories and my character arcs in ways that utilize my fantasy elements without allowing them to take over my story telling. My heroes may possess magic, but in the end, I will always choose to have them prevail by drawing upon their native human qualities — their courage and resolve, their intelligence and creativity, their devotion to the people and places they love. Magic sets them apart and makes them interesting. It is often the hook the draws readers to my books. But those human attributes — those are the ones my real-world readers relate to. They form the bond between my readers and my characters. And so if those are the qualities that allow my characters to prevail in the end, then their triumphs will feel more personal and rewarding to my readers. It is the simplest sort of literary math.

I believe part of the bias against genre fiction is based in the erroneous belief that the trappings of these literary types — magic, imagined technology, romantic tension and conflict, the ticking clock of a murder investigation — somehow serve as substitutes for character development and good writing fundamentals. In truth, they are complements to solid narrative work. Genre fiction, when well done, has all that extra stuff we love AND great story telling.

I expect I am preaching to the choir a bit with this post. That’s okay. It’s not just those of us who write genre fiction who have to put up with the biases of others. Readers of our genres deal with the same sort of prejudices all the time. Fine. Those other people don’t know what they’re missing.

Plus, their book jackets aren’t nearly as cool as ours.

Keep writing. Keep reading.

Professional Wednesday: Punctuating Our Stories (Not the Way You Think I Mean It)

“Louis, I think this is the beginning of a beautiful friendship.”

We all know the line. Even people who haven’t seen Casablanca know the line. (And please, don’t get me started about not seeing Casablanca. I mean, sure, it’s dated, But it remains one of the greatest movies of all time. Humphrey Bogart, Ingrid Bergman, Claude Rains, Peter Lorre, Dooley Wilson, Paul Henreid, Conrad Veidt, and so many others. It has romance, intrigue, action, and it keeps you guessing right up to the stunning ending. See? This is why you shouldn’t get me started . . .) Anyway, the line. It is one of the great bits of closing dialogue in any movie ever made.

But it’s more than just clever. It is the perfect punctuation point for the film’s narrative. From that line, and those that come directly before it in the last minute or so of the film, we know everything we need to about what is next for our hero, Richard Blaine. We know that he’ll survive letting Ilsa go (yeah, I know: spoiler. Get over it. The movie was made, like, three centuries ago. If you haven’t seen it yet, that’s on you, not me). He’ll go on to join the French Resistance and fight the Nazis with Louis Renault by his side. And, very likely, he and Louis will be heroes in that effort.

What’s my point?

Simply this: Every story — certainly every novel — needs its own version of “Louis, I think this is the beginning of a beautiful friendship.”

I’m doing a lot of editing these days, and I have seen several manuscripts that reach endings of a sort, but that fail to tie things up in a satisfying way. To be clear, I am not saying that every book needs a pat conclusion. We can leave some questions unanswered. We can hint at futures to come. My favorite fantasy novel of all time, Guy Gavriel Kay’s Tigana, ends with a prophesy that suggests fates for three men, but we are left to wonder which future is tied to which character. It works.

I am also not talking about the climax of your novel. That is something different — also important, obviously, but different.

What I am suggesting here, rather, is that we need to have some closure for our lead characters, AFTER the final battle/confrontation/major plot point. We need to see those characters in the aftermath of all to which we have subjected them, and we need to see them moving on (or not), healing (or not), finding peace or contentment or new purpose (or not). Yes, the details are vague. I would never think to tell any writer how content-wise to end their book. We each have a vision of what awaits our characters and that is intensely private.

The Loyalist Witch, by D.B. Jackson (Jacket art by Chris McGrath)But at the very least, we need to see our main heroes grappling with what they have endured and setting their sights on what is next for them. We don’t need this for every character but we need it for the key ones. Ask yourself, “whose book is this?” For me, this is sometimes quite clear. With the Thieftaker books, every story is Ethan’s. And so I let my readers see Ethan settling back into life with Kannice and making a new, fragile peace with Sephira, or something like that. With other projects, though, “Whose book is this?” can be more complicated. In the Islevale books — my time travel/epic fantasy trilogy — I needed to tie off the loose ends of several plot threads: Tobias and Mara, Droë, and a few others. Each had their “Louis” moment at the end of the last book, and also some sense of closure at the ends of the first two volumes.

TIME'S DEMON, by D.B. Jackson (Art by Jan Weßbecher)Why do I do this? Why am I suggesting you do it, too? Because while we are telling stories, our books are about more than plot, more than action and intrigue and suspense. Our books are about people. Not humans, necessarily, but people certainly. If we do our jobs as writers, our readers will be absorbed by our narratives, but more importantly, they will become attached to our characters. And they will want to see more than just the big moment when those characters prevail (or not). They will want to see a bit of what comes after.

So, I am suggesting that you decide which characters matter most to your story and therefore to your readers, and then give those characters (and your readers!!) a satisfying conclusion to their narrative and personal arcs. Let us see them post-conflict, post-finale. Give us a glimpse of what life has in store for them next. They have been our friends and companions for hundreds of pages. Maybe thousands. And while we can reread the story you’re finishing, the fact is we’re saying goodbye to them. We may never encounter them again. Or maybe we will, in which case you can hint at that. But we need . . . something.

J.R.R. Tolkien did not end The Lord of the Rings with the battle in front of the gates of Mordor. He didn’t end it with the scouring of the Shire, or even with Frodo and Bilbo sailing to the Grey Havens. He ended it with Sam returning home after bidding farewell to Frodo and saying, “Well, I’m back.” Because that is the point of the story: Our heroes may be leaving these shores, Aragorn may be king far, far away and Legolas and Gimli may be back with their people, but the Shire and Middle Earth endure and go on. And Sam is the best character to make that point.

Mastering the use of that sort of story punctuation is a key element of effective storytelling. I recommend you work on it.

Keep writing!

Professional Wednesday: Most Important Lessons — Trust Yourself, Trust Your Reader

Today, I’m introducing a new feature for my Professional Wednesday posts: “Most Important Lessons.”

We are coming up on the 28th anniversary of the start of my career (which I trace to the offer I received from Tor Books on Children of Amarid, my first novel). To mark the occasion, I thought about doing a “lessons I’ve learned” post. I quickly realized, though, that I could write 20,000 words on that and still not exhaust the topic. Better then, to begin this series of essays, which I will return to periodically, as I think of key lessons that I’ve learned about the business and craft of writing.

I’ve chosen to start with today’s lesson — “Trust Yourself, Trust Your Reader” — because it’s one I’ve found myself repeating to writers a lot as I edit short stories for the Noir anthology and novel length projects that come to me through my freelance editing business.

Jacket art for Bonds of Vengeance, book III in Winds of the Forelands, by David B. Coe (Jacket art by Romas Kukalis)Honestly, I think “trust yourself” is good advice for life in general, but for me, with respect to writing, it has a specific implication. It’s something I heard a lot from my first editor when I was working on my earliest series — the LonTobyn Chronicle and Winds of the Forelands.

Writers, and in particular less experienced writers, have a tendency to tell readers too much. Sometimes this manifests in data dumps, where we give way more information about our worlds or our characters than is necessary. And yes, that can be a problem. I have no doubt that in future “Most Important Lessons” posts, I will cover world building, character, and ways to avoid data dumps.

For today’s purposes, though, I refer to a different sort of writing problem that can be solved simply by trusting our readers and trusting ourselves. As I said, writers often tell readers too much. We explain things — plot points, narrative situations, personality traits. And then we tell them again. And again. And as we build to our key narrative moments, we give that information yet again, wanting to make certain that our readers are set up for the resolutions we’re about to provide.

There are several problems with doing this. First, it tends to make our writing repetitive, wordy, and slow. Nobody wants to read the same information over and over. It’s boring; worse, it’s annoying. Second, it forces us to hit the brakes at those moments when we should be most eager to keep things moving. If we’re explaining stuff as we approach the climactic scenes in our stories, we are undermining our pacing, weakening our storytelling, robbing our stories of tension and suspense. And third, we are denying our readers the pleasure of making connections on their own. We are, in a way, being like that guy in the movie theater revealing key moments in the film right before they happen on screen. And everyone hates that guy.

We have to trust that our readers have retained the things we’ve told them. We have to trust that they are following along as we fill in backstory, set up our key plot points, and build our character arcs and narrative arcs. We have to trust that they are right there with us as we move through our plots.

In other words, we have to trust that we have done our jobs as writers.

Trusting our readers means trusting ourselves. Readers are smart. They pay attention. They read our stories and books because they want to. Sure, sometimes they miss things. Sometimes they skim when they ought to be paying attention. As a reader myself, I know that I am not always as attentive as I ought to be. But I also know that when I sense I’ve missed something important, I go back and reread the sections in question. Your readers will do the same.

Trust that you have engaged them with your plot lines and characters. Trust that you have given them the information they need to follow along, and have built your stories the way you ought to. Trust that they are following the path you’ve blazed for them.

“But,” you say, “what if I haven’t done those things? Isn’t it better to be certain, to tell them more than they need to know, so that I can be absolutely sure they get it?”

It would seem that way, wouldn’t it? But that’s where trust comes in. Sure, there is a balance to be found. We don’t want to give our readers too much, but we don’t want them to have too little, either. And the vast majority of us fear the latter far more than the former. We shouldn’t. Again, readers are pretty smart. If the information is in the book, they’ll make use of it. Better, then, to trust, to say, “It’s in there. I’ve done what I could, what I had to. I am going to trust that I did enough.”

Yes, the first time or two, we might need to revise and give another hint here or there. But generally speaking, when we trust our readers — when we trust ourselves — we avoid far more problems than we create.

Trust me.

Keep writing.

Professional Wednesday: Top Ten Reasons You Need INVASIVES!!

INVASIVES, by David B. Coe (Jacket art courtesy of Belle Books)

In case the daily teasers and cover art reveals and previous blog posts all failed to tip you off, this is release week for Invasives, the second Radiants novel. It comes out on Friday, February 18! Yay!!

Release weeks are a big deal and we authors depend on early sales of new books to maintain series momentum and to get the new book front and center in the attention of the reading public.

And so, here are my top ten reasons why you need to buy INVASIVES!

10. I’m a good guy, and you want to help out my career!

9. Have you seen the jacket art?? I mean I know: book, cover, ixnay on the udgementjay. But this is a seriously cool cover, and, I have to say, it is quite representative of the story contained within.

RADIANTS, by David B. Coe (Jacket art by Belle Books)8. You read Radiants, right? Right? And so you know how good that book was. Why wouldn’t you want to read this one, too?

7. Along similar lines, I love this series, and I think if you give the books a chance, you’re going to love the series, too. And if the second book doesn’t sell, there won’t be a third. That is simple publishing industry arithmetic. Good sales mean a series continues. Bad sales not so much.

6. My lead characters are homeless teens living in the New York City subway tunnels. I’ve written about an entire underground culture and society — the Below — invisible to those of us in the Above. That alone should be pretty intriguing.

5. You’ve seen the teasers I’ve been putting up daily on social media. Tell me those haven’t whet your appetite for the story.

4. All kidding and promotional enthusiasm aside, this is the book I wrote during the time when I was first dealing with the news of my older daughter’s cancer diagnosis. Without this story, I’m not sure how I would have made it through those dark, difficult days. All my books mean a lot to me in one way or another. But this book in particular is one that I cherish and love, in part because the emotions of my journey as I wrote it come through in the narrative, the prose, the character arcs. This is, to my mind, a very special book.

3. As I mentioned in a recent post, the three lead characters came to me long, long ago — a decade ago, or more — and they have haunted me ever since. Their backstories are complex, as are their conflicted interactions with one another. This is some of the most intricate character work I’ve done — I’m quite proud of it actually.

2. My agent, the fabulous Lucienne Diver, told me when she first read the manuscript that this might well be her favorite of all the books I’ve written. Don’t you want to know why?

And my number one reason why you should buy this new book . . .

1. It really is a fun read, a moving read, an exciting read. The story includes characters with cool Radiant powers, assassins who will chill you to the core, and heroes who will make you stand up and cheer. The narrative will grab you on page one, and it won’t let go. Trust me on this.

You can order Invasives from:

Amazon | Barnes and Noble | Kobo | Google Books

 

 

Professional Wednesday: Throw Nothing Away — A Writing Lesson Courtesy of INVASIVES

INVASIVES, by David B. Coe (Jacket art courtesy of Belle Books)February has begun, Punxsutawney Phil has done his schtick, and time seems to be moving at breakneck speed. In a little over two weeks, Invasives, the second Radiants book, will be released by Belle Books.

Like Radiants, this is a supernatural thriller. This time, though, I have set my thriller in New York City, and a good deal of the story takes place in the New York subway tunnels. My lead characters are a trio of homeless, runaway teens — Mako, Bat, and, my main protagonist, Drowse. They live off what they can make by scrounging and, yes, stealing, and they take shelter in a house built of cardboard and shower curtains, tape and rope and plastic ties.

Bat is blind. He comes from money, but had to leave his home. When the book opens, we don’t know why.

Mako was involved in gang activity for a time, but eventually went straight. Or tried. Did I mention they have to steal?

Drowse ran away from a terrible home situation. She turned tricks for a time. Ran drug money. Now she’s trying to hold their small “family” together and survive in the Below. And, as it happens, she’s a Radiant, whose power is invaluable to their business.

But her abilities, and the business they do, have now attracted the notice of some of the most powerful people in New York’s financial world. They want something Drowse has, and they are willing to do anything, kill anyone, to get it.

Intrigued? I hope so. I love, love, love this book. Yes, I know, I say that about all my books when they come out. Because it’s true.

Invasives, though, is special to me in a couple of ways.

First, this is the book I was writing when we first got my daughter’s cancer diagnosis last March. At first, I put my writing on hold. I could barely function. I could barely think. How the hell was I supposed to write a novel? Well, as it turned out, writing this book was just what I needed. It is a fraught narrative, filled with suspense and tension. It focuses on these three characters, on their love for one another, on their bonds, and the forces trying to tear them apart. It wasn’t about cancer at all, and that was a good thing. But the story gave me an outlet for all the emotions churning inside me. As I have said before, I could not have gotten through the ordeal of last spring and summer without this novel.

And second, Drowse, Mako, and Bat were with me, lurking in my imagination, for more than a decade before I finally started work on this book. I had the idea for them, for their circumstances and relationships, long before I knew what story to build around them. I knew only that I loved the characters, and their dynamic. I had one idea for a novel, but I could never quite figure out the storyline, the world, the ending. I did write a kick-ass opening chapter for it, though.

Then, two years ago, I began writing the first Radiants book, and as I thought about subsequent volumes, Drowse and her friends popped back into my head. This was their story. Finally. This was the perfect world in which to place them. I even was able to use an updated version of that opening chapter.

I have said before, half in earnest, half in jest, that writers are packrats. We keep everything. Or at least we should. When I figured out that Drowse et al. would be the perfect protagonists for my second Radiants book, I knew just where to find the original character sketches, the original opening chapter, the original storyline for their caper. Because even that wound up factoring in to the creation of Invasives.

I never lost faith in the groundwork I did for their story all those years ago. I knew there was a novel there, somewhere. It was just a matter of placing it.

That happens to me a lot, and I know it happens to other authors as well. Sometimes we have an idea, and we are ready immediately to write and publish it. Other times, stories and characters take a while to steep, like good, strong tea. For ten years, Drowse, Mako, and Bat waited in a file on my computer desktop. It wasn’t that the original idea was bad or lacking in some way. It just wasn’t ready. Or rather, I wasn’t yet ready to write it in a way that did justice to the power of the original notion.

And that made the final realization of their tale in this novel all the more satisfying.

Keep writing. And don’t throw any idea away!

Writing-Tip Wednesday: Ten Books You Should Read

Early in the year — even before the pandemic hit — I wrote a post in which I basically said that all writers should read. There are certain “rules” about the profession that are actually negotiable — writers don’t really HAVE to write every day; we don’t HAVE to outline our books to be successful; some people like to write to music while others need absolute silence.

The reading thing, however, as I said at the time, is about as close to an ironclad rule as I can think of. If we want to learn the tropes of whatever genre we write in, we have to read. If we want to learn the craft of storytelling, and continue to hone that skill over a lifetime, we have to read. If we want to be informed and culturally literate citizens of the world, we have to read.

But what should we read? As an author with many friends in the business, I find that making recommendations can be tricky. I don’t wish to insult any of my colleagues with sins of omission. But there are certain books that I have read and not only enjoyed, but learned from. That’s what I’m after in this post. The following books have taught me something about narrative, about conveying story and emotion, about crafting prose. There are some unusual, even quirky, choices here. That comes with the prerogative of writing on my own blog. I hope you find this list helpful, informative, even inspirational.

In no particular order…

The Fifth Season, by N.K. Jemisin. Okay, for starters, it’s just a great book and the start of a remarkable series, a deserving winner of the Hugo (which was actually awarded to all three books in the Broken Earth Trilogy). Her plotting is fabulous, her use of point of view innovative and striking. Jemisin has since been awarded a MacArthur Genius Grant. So, yeah, she basically rocks.

Slow River, by Nicola Griffith. This is an older novel, the 1996 winner of both the Nebula Award and the Lambda Literary Award. It’s a great story, and it makes use of point of view and voice so beautifully that I have used it for teaching on several occasions. Basically she uses three different voices for a single character, each representing different moments in her life. Brilliant.

The Lions of Al-Rassan, by Guy Gavriel Kay. Kay is probably my favorite fantasy writer, and in recent years he has become a good friend, so I’m bending my own rule here, including the work of someone I know well. But I was a fanboy way before we became friends, so… He does a lot of things very well in all his books, but the world building in this particular book is breathtaking. He borrows extensively from history — he does in most of his books — but he also constructs his worlds with the care and skill of a watchmaker.

A Wizard of Earthsea, by Ursula K. Le Guin. The entire Earthsea Trilogy is one of my all-time favorite works of fiction, but this first volume especially is masterful. It’s a relatively short work, and originally received less attention than it deserved because it was classified, somewhat patronizingly, as “children’s literature.” The worldbuilding is gorgeous, the storytelling simultaneously spare and rich, the prose understated but flawless. Even if you’ve read it, give it another look

Angle of Repose, by Wallace Stegner. The first of a couple of non-genre novels. Stegner was not only a terrific writer, but also a passionate, outspoken environmentalist and a chronicler, through his fiction, of the development of the American West. In 1972, Angle of Repose won the Pulitzer Prize for Fiction. It is a master class in narrative. He basically tells two stories at once, one set in the present, one in the past. He blends them beautifully. And his prose is golden.

Animal Dreams, by Barbara Kingsolver. Another exquisitely written novel of the American West. Kingsolver weaves together multiple narratives and employs several different points of view to tell her tale. It’s moving, sad, uplifting. Actually, writing about it makes me want to read it again…

Adventures in the Screen Trade, by William Goldman. William Goldman wrote The Princess Bride, and then adapted the novel for the screen. He wrote the scripts for Butch Cassidy and the Sundance Kid and All the President’s Men. He wrote Marathon Man, and then adapted it to the screen. And he wrote or adapted scripts for about twenty other movies you’ve heard of. In 1983, he published Adventures, which is part tell-all, part how-to. You don’t have to be an aspiring screen writer to learn from it. It is a treatise on creativity and the business of creation. It’s also entertaining as hell.

Five Seasons, by Roger Angell. Okay, this is, admittedly, a VERY quirky choice, but bear with me. Roger Angell, who recently turned 100 years old, is quite possibly the greatest baseball writer who has ever lived. He wrote regularly for The New Yorker from the 1960s through the first decade of this millennium. He has several collections of baseball essays, and Five Seasons is my personal favorite. But if you’re a baseball fan, you can’t go wrong with any of them — The Summer Game, Late Innings, Season Ticket, Once More Around the Park, Game Time. They’re all amazing. His descriptions of the game and the people he encounters are strikingly original and incredibly evocative. Even if you DON’T like baseball, you could learn from his work.

The Windup Girl, by Paolo Bacigalupi. Back to genre stuff for a moment. The Windup Girl won the Hugo and Nebula Awards in 2010, and it deserved them, along with every other honor it received. Terrific storytelling, powerful prose, mind-bending world building. This is the whole package.

Any collection of Nathaniel Hawthorne’s short fiction. Another quirky choice. Hawthorne is, I believe, one of the more underrated of American writers. He was writing speculative fiction a century before anyone knew what the hell that was. His stories are haunting, strange, and memorable. “Rappaccini’s Daughter” might be my favorite short story. By anyone. Ever.

And with that, I’ll end.

Except to say, as I did back in February, that to be a writer is, by necessity, to be a reader as well. That is one of the joys what we do.

So keep writing, and keep reading.

Writing-Tip Wednesday: Dialogue Attribution Revisited

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!

Writing-Tip Wednesday: Call For Stories, and Submission Advice Revisited!

I am co-editing a new Zombies Need Brains anthology with my friend, Joshua Palmatier, who is the founder and owner of Zombies Need Brains. Joshua is co-editing all three of the ZNB anthologies this year, which to my mind is totally nuts, but good for him.

The theme and title of our project for this year is DERELICT, and if you’re a writer, you should consider submitting. We are looking for stories about derelict ships (seafaring ships, space ships, even a good story about a derelict bus or truck or car could find its way into the collection). The stories should be speculative fiction (SF, fantasy, or horror) and they should be about 2,500-7,500 words long, though REALLY good stories that are shorter or a bit longer will be considered. You can find the guidelines for all three of this year’s anthologies at the ZNB website. ALWAYS read the GLs before submitting to any market.

With stories already arriving in good numbers, and the call for stories open until December 31st, I thought I would revisit some of the short fiction submission advice I offered earlier this year and late last year.

Galactic Stew, edited by David B. Coe and Joshua B. PalmatierAnd 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.

We have a lot of stories to read, and while we are eager to be blown away by something really good, we are also looking for reasons to reduce our pile of submissions to be read. If you send us a manuscript that doesn’t follow the theme, or that doesn’t follow the submission guidelines, or that is filled with typos and misspellings and grammatical issues, we are probably going to reject your story and move right on to the next. That’s just fact. So, you want to get all of that stuff right, so we can consider your story solely on its merits — your terms.

Now, it may be that your story is good but not as good as others, or it might be good but too similar to others we’ve read. We’ll reject stories, even fine ones, for a number of reasons. But by getting the simple stuff right, by turning in a solid, clean, professionally presented manuscript, you give yourself a better chance.

With that in mind…

— Read and follow the guidelines. Follow the formatting to the letter. There is nothing that bothers me more than being in the middle of a 10 hour day of reading slush and getting a single-spaced manuscript that I then have to format myself. In the same way, if the GLs say the story should be no longer than 7,500 words, don’t send us something that’s 10,000. Either edit it down to the word limit or submit something else.

— Edit and polish your story. Proofread it and then proofread it AGAIN. Don’t be in such a rush to get the story out that you neglect to get rid of that typo on page 6 or three instances of “your” that should have been “you’re.” Take pride in your work. Be professional.

— Pay attention to and follow the theme. Again, we’re looking for stories about derelict ships. That doesn’t mean we want a story in which a derelict is mentioned. The ship should be the essential element of the narrative. Without the derelict, your story should fall apart. Think of it like the instructions on a cooking show: “Make our theme the star of your dish…”

— Keep in mind the basic principles of good storytelling. A successful story has conflict, emotion, tension. Characters should be impacted by what takes place. If you have trouble identifying the protagonist and antagonist of your story, it may be that you have more work to do.

— This piece of advice is one I heard Joshua give at a conference last year: Chances are your first idea won’t be your best idea. Sometimes the first idea that comes to us is the one everyone will think of. A bit more digging and thinking might produce an idea that is more original and innovative. And that may well give you a better chance of making it into the anthology. Now, I will add that now and then, the first idea IS the best. But more often than not, a bit of thought and patience will be rewarded.

— Most important, understand that a rejection from this anthology is NOT a judgment on your ability as a writer, or even on the quality of your story. Remember those numbers I gave you earlier: 300-400 submissions for 6-7 slots. Our anthology is harder to get into than Harvard. We will absolutely be rejecting outstanding stories. That’s inevitable. So don’t take it too hard. Rejections are part of being a writer. View them as a step in a longer negotiation. If your story is rejected, take ten minutes to cry over it. Have a beer or a glass of wine or a cup of hot tea. And then figure out where you’re going to send the story next.

Best of luck, and keep writing!

Writing-Tip Wednesday: The Quickening

Okay, writers, raise your hand if any of your characters have ever done things you didn’t expect. Yeah, I figure that’s most of us. Now raise your hand if your characters have ever done things you really didn’t want them to do. Yep. Also most of us.

Of all the things I tell non-writers about what I do for a living, this is the one that always draws the most interest, surprise, and skepticism.

“But they’re creations of your imagination! You control them. How can they surprise you, much less disobey you?”

I control them?! Hah!

At the end of the first book of Winds of the Forelands, a series I intended at the time to be four books long (it wound up being five), one of my characters told me she was pregnant. I swear. I typed the words, sat back, and said aloud, “Freaking hell, she’s pregnant.” Except I didn’t say “freaking.”

I had the other books planned out. I knew where the plot was going and what the character arcs for the rest of the series were supposed to look like. There was no room in there for a kid. None.

“So,” a non-writer might ask, “why not delete that sentence from the manuscript and write something else? They’re your characters, inhabiting your world, right?”

Well, yes, but no.

Because while I didn’t want her to be pregnant, I knew as soon as I typed the words that she had to be, that it made far more sense with all that had come before. And the rest of the series, as eventually written and published, bears this out. It was a much better story with the child than without her. I just needed to be led there, and my character did that for me.

There is an old term, coined originally by midwives — the quickening. This is when a fetus begins to move, showing its first signs of life in the womb. And that is the term I use to describe the evolution of a character from a creature purely of our imagination, to a person capable of making decisions that surprise us and help to shape our narratives.

At my very first DragonCon some twenty-plus years ago, when I was still the newbiest of newbies, I got into an argument with a VERY famous fantasy writer about this very thing. (We were on a panel — this was in front of a crowd.) I won’t give this person’s name. Some of you have heard me tell the story, and so know. The rest of you have my apologies. But this was a BIG name, one of the very biggest. And this person swore up and down that we are the gods of our worlds, the masters of our stories, and if our characters were doing things we didn’t expect then we were doing this wrong. And at last, in my frustration, I said what I believe to this day to be the single wisest thing about character development I have ever offered: If you write them like puppets, they’ll read like puppets. (I patched things up with the Big Name afterwards. This person was gracious and kind, which is why my vehemence, and the implied criticism in my remark, did not wind up ruining my career.)

The quickening is a good thing, a great thing. When our characters begin to behave in a way that feels independent, as if they have agency and will and spirit, they become more real to our readers. They go from being words on a page to being three-dimensional beings.

Now, of course, they really are words on a page. And I have no doubt that someone versed in the workings of the psyche would tell me what is happening has nothing to do with the characters and everything to do with the mechanics of my imagination. At the moment of the quickening, they would likely say, my belief in my characters and my comfort with them reaches a point where they begin to work on my subconscious and influence my thinking about my narrative and my world. Whatever. It’s much easier to say that my characters are surprising me and guiding me. Because that’s how it feels, and in all ways that matter, that’s what’s happening.

I can’t think of any advice that will help you get to this moment with your characters. I would guess that most of you get there on your own, in the normal course of writing your stories. The truth is, the moment when our characters begin to surprise us is the moment when writing becomes really fun. When I’m writing and enjoying the process most, I don’t think so much as I describe things my characters are seeing, and document things they’re doing and saying. Writing dialogue becomes more like stenography — I’m writing down the conversations I hear in my mind.

But I will offer this — to carry the childbirth analogy a bit further…

Dealing with characters who have come alive in our minds is a bit like parenting. We want to give them the freedom they need to become the literary equivalent of living, breathing people. We want them to grow, to be independent, to have that agency I mentioned before so that the stories we’re telling feel organic and true and immediate. At the same time, though, as with real children, we don’t want to give them absolute free reign. That big name author was right in part: This is still our creative work, and while characters have to be allowed to take our stories in unexpected directions, they shouldn’t take over entirely. We wouldn’t want a five-year-old running our household, and we don’t want a fictional character, or even a set of them, making every meaningful decision in our narrative. Put another way, we don’t want to stifle the character’s growth, but by necessity we have to maintain some control.

The quickening is magical and affirming and inspirational. It’s that moment in Frankenstein (or, if you prefer, Young Frankenstein) when the doctor cries out “It’s alive!” It carries our storytelling to another level, transforming writing into something akin to discovery. But we must always remember that it does not absolve us of our creative responsibilities.

Enjoy! And keep writing!