Tag Archives: writing tips

Bell Bridge Books, Belle Books, Blogging, D.B. Jackson, David B. Coe, editing, Invasives, The Chalice War, Writing

Professional Wednesday: Another Letter To My Younger Self

Dear Younger Me,

Yes, it’s me again — Middle Aged David. Upper Middle Aged David, actually. I know I wrote to you earlier this week. I remember doing so. I’m not so far gone quite yet. But I thought you might benefit from a second letter focused on the professional side of things. As I told you on Monday, we did wind up having a career in writing, just as we dreamed when we were a kid. And, also as I told you, our professional life hasn’t followed precisely the path we envisioned. That’s fine. We’ve had a good ride so far. But there’s stuff you should know, stuff I wish I had known.

I suppose all of it can be summed up in two words — and I hate to resort to cliché, in a writing post no less, but it really is true. Shit happens. It does, it does, it does. And it has happened to us. More than once.

The biggest mistake I made — we made — early on was assuming our career trajectory would be linear, a progression toward greater and greater success, higher and higher advances, bigger and better sales numbers. That may be true for a select few, but for most writers a career follows a meandering, uncertain path. Some books and series are more successful than others — commercially and critically. I call that early expectation of ever-improving circumstance our biggest mistake not because it somehow led to a disappointing outcome for one project or another, but because it caused me — us — so much pain. When our career hit that first speed bump, I took it personally. I felt I had failed, and also that the industry had failed me. I was confused and angry and sad and, most of all, terrified at the thought that this first disappointment would mean the end of our professional journey. I didn’t yet understand the nature of a creative life.

And so I say to you, Younger Me, learn resilience. Grieve for those lofty unmet ambitions, but then move on and try again. Learn moderation. Don’t let commercial and critical success carry you too high, and don’t let poor results drive you too low. Success will follow failure, which will follow success, and so on. If you can — and I know it’s so, so hard — learn to let go of expectation entirely. We don’t know which books will soar and which will flop. We love them all, which is why we go to the extreme trouble of writing them in the first place. And finally, learn contentment. Love the stories you create on their own terms. Find success in the completion of a good tale, in the realization of an artistic vision.

Take every promise made to you by an editor and publisher with a grain of salt. It’s not that they don’t mean what they say. Okay, SOME of them don’t mean what they say. But mostly, they simply can’t anticipate all that might happen. Producing a book is no small feat. A thousand things can go wrong. Editors and publishers often tell us, as if gospel, that a certain thing is going to happen on a given date. And that is, at the moment, their best guess of what will happen. Pencil in the date. Don’t commit it to ink. Because, as we have established, shit happens.

Thieftaker, by D.B. Jackson (Jacket art by Chris McGrath)All those great ideas you have for jacket art? They’re not as great as you think they are. Seriously. We are a writer. And we’re very, very good at that. We are NOT a graphic artist. We are NOT a marketing expert. I remember when the first Thieftaker novel went into production, I had what I thought was SUCH a wonderful idea for the jacket art. A can’t miss idea. PERFECT for the book. It wasn’t any of those things. The moment I saw Chris McGrath’s image for the book, which WAS brilliant and wonderful and perfect, I understood that no one should ever put me — us — in charge of selecting jacket art.

INVASIVES, by David B. Coe (Jacket art courtesy of Belle Books)On the other hand, do trust in your story ideas. All of them. Even the old ones that haven’t yet gone anywhere. At some point, you’ll have an idea for a story about three kids living in the subway tunnels beneath New York City. And you won’t have any idea what to do with it. You’ll give up on it. Don’t. It will become Invasives. At another time, you’ll write a story about two women interacting with Celtic deities and trying to protect an ancient, transcendently powerful magical artifact. That one, too, will seem to languish. Trust the story. That book just came out. It’s called The Chalice War: Stone. Believe in your vision.

If a publisher promises more than you think they can deliver, under terms that seem way too good to be believed, be skeptical. Very, very skeptical. Chances are, they CAN’T deliver. Chances are those terms can’t be met. We’ve been burned a couple of times. ’Nough said.

Over the past twenty-five-plus years, I have tried to thank Nancy every single day for making our career possible. And I’ll continue to thank her. But I might have missed a few days. Fill in the gaps, will you?

Most of all, keep doing what you’re doing and I’ll do the same. No, we haven’t gotten all we wanted, we haven’t achieved every goal. But we’re doing okay, and as much fun as you’ve been having early in our career, I’m having even more now. It keeps getting better.

And yes, the rumors are true. We’re editing now, and we like it. The dark side really is more powerful . . . .

Best wishes,

Older David

Blogging, D.B. Jackson, David B. Coe, editing, Tor Books, Winds of the Forelands, Writing

Professional Wednesday: Trust Yourself. No, Really.

Rules of Ascension, by David B. Coe (Jacket art by Gary Ruddell)Trust your reader.

This is editor speak for “trust yourself.” It is something I say often to many of the writers I edit.

But what does it mean?

I have had my own lesson in “trust your reader” in recent days as I have begun the long, arduous task of editing for reissue the five volumes of my Winds of the Forelands epic fantasy series, originally published by Tor Books back in the early 2000s, when I was still a relative newbie. My editor at Tor used to tell me all the time to trust my readers, and so I assumed — naïvely, it would seem — that back in the day he and I had caught all the instances where I didn’t trust my reader. But no. It seems there were so many of these moments, that he had to engage in a sort of editorial triage, catching only the most egregious and leaving the rest.

Yes, I know. I still haven’t defined the phrase.

Seeds of Betrayal, by David B. Coe (Jacket art by Gary Ruddell)As I say, “trust your reader” is essentially the same as “trust yourself.” And editors use it to point out all those places where we writers tell our readers stuff that they really don’t have to be told. Writers spend a lot of time setting stuff up — arranging our plot points just so in order to steer our narratives to that grand climax we have planned; building character backgrounds and arcs of character development that carry our heroes from who they are when the story begins to who we want them to be when the story ends; building histories and magic systems and other intricacies into our world so that all the storylines and character arcs fit with the setting we have crafted with such care.

Bonds of Vengeance, by David B. Coe (Jacket art by Romas Kukalis)And because we work so hard on all this stuff (and other narrative elements I haven’t even mentioned) we want to be absolutely certain that our readers get it all. We don’t want them to miss a thing, because then all our Great Work will be for naught. Because maybe, just maybe, if they don’t get it all, then our Wonderful Plot might not come across as quite so wonderful, and our Deep Characters might not come across as quite so deep, and our Spectacular Worlds might not feel quite so spectacular.

And that would be A Tragedy.

Shapers of Darkness, by David B. Coe (Jacket art by Romas Kukalis)Okay, yes, I’m making light, poking fun at myself and my fellow writers. But fears such as these really do lie at the heart of most “trust your reader” moments. And so we fill our stories with unnecessary explanations, with redundancies that are intended to remind, but that wind up serving no purpose, with statements of the obvious and the already-known that serve only to clutter our prose and our storytelling.

The first few hundred pages of Rules of Ascension, the first volume of Winds of the Forelands, is filled to bursting with unnecessary passages of this sort. I explain things again and again. I remind my readers of key points in scenes that took place just a dozen or so pages back. I make absolutely certain that my readers are well versed in every crucial element (“crucial” as determined by me, of course) in my world building and character backgrounds.

Weavers of War, by David B. Coe (Jacket art by Romas Kukalis)As a result, the first volume of the series was originally 220,000 words long. Yes, that’s right. Book II was about 215,000, and the later volumes were each about 160,000. They are big freakin’ books. Now, to be clear, there are other things that make them too wordy, and I’m fixing those as well. And the fact is, these are big stories and even after I have edited them, the first book will still weigh in at well over 200,000 words. My point is, they are longer than they need to be. They are cluttered with stuff my readers don’t need, and all that stuff gets in the way of the many, many good things I have done with my characters and setting and plot and prose.

I have always been proud of these books. I remain so even as I work through this process. People have read and enjoyed all five volumes as originally written despite the “trust your reader” moments. I actually think most readers pass over those redundant, unnecessary passages without really noticing them. They are not horrible or glaring (except to me); they’re just annoying. They are rookie mistakes, and so I find them embarrassing, and I want to eliminate as many as possible before reissuing the books.

But our goal as writers ought to be to produce the best stories we can write, with the clearest, most concise narratives and the cleanest, most readable prose. “Trust your reader” moments are a hindrance — one among many — to the achievement of that goal, and so we should be aware of the tendency and work to eliminate these unnecessary passages from our writing.

Mostly, we should remember the translation — “trust your reader” means “trust yourself.” Chances are we have laid our groundwork effectively, establishing our worlds, developing our characters, setting up our plot points. If we haven’t, a good editor will tell us so and will recommend places where we can clarify matters a bit.

So, remember that less is usually more, that showing is almost always better than telling, that most times when we stop to explain stuff we rob our stories of momentum.

And most of all, remember to trust yourself. You’ve earned it.

Keep writing.

Bell Bridge Books, Belle Books, Blogging, Blood of the Southlands, Case Files of Justis Fearsson, D.B. Jackson, David B. Coe, Islevale Cycle, LonTobyn Chronicle, Radiants, The Chalice War, Thieftaker Chronicles, Winds of the Forelands, Writing, Zombies Need Brains

Professional Wednesday: Learning From Each of Our Projects

Ideally, every new book and story we write is not just an adventure in imagination, a chance to discover new characters and settings and narratives, but also a learning opportunity. I continue to improve my writing with each project, and I try to do at least one thing new with each story or novel. For instance, while working on my short story for the Dragonesque anthology, which will be published later this year by Zombies Need Brains, I was aware that my editors (and good friends), Joshua Palmatier and S.C. Butler, both tend to cut out a few dialog tags from all the stories they edit. I was determined to make that impossible for them. And I wound up managing to write the entire story using only a single instance of “said” or “asked.” Let them find something else to cut! In doing this, I actually made the story leaner, more concise, and more fun to read.

The Chalice War: Stone, by David B. CoeWith this in mind, I thought it might be helpful to list a few things I learned, reminded myself of, and/or tried to do differently while writing my Chalice War trilogy, which debuts on Friday, May 5 (THIS FRIDAY) with the release of The Chalice War: Stone from Bell Bridge Books.

Journal about, well, everything: The first book in the Chalice War series includes a frenzied chase/trek across the U.S., and a series of climactic scenes that are set in Las Vegas. The second book is set in Australia — in Sydney, as well as in the tourist town of Kiama along the Illawarra coast. The third book is set in Ireland. I have driven across this country a few times, and I’ve been to all the places I just mentioned. I have driven into Vegas at night, approaching from the east, as my characters do. I have spent time along the Irish coast (although not quite the same part). I have spent a good deal of time in Kiama.

And I have journaled about all of these experiences. While writing descriptive passages for the books, I drew heavily on old journal entries (and also on my old photographs). I’ll admit this is not the first time I have drawn upon personal experiences and writings for this sort of thing. When I wrote the Fearsson books, I consulted journal entries from visits to the Sonoran Desert. Whenever I write in the Thieftaker world, I draw on old entries from my college years in New England. This is not a new lesson, so much as something I was reminded of while writing the Chalice books. But the value of the point is undeniable. The more we write, the better we get, and journaling helps us keep in practice, which is reason enough to do it. But it can also be a terrific source for material that we can adapt to our fiction, be it in the form of descriptive writing, character development, or even plot points.

Dude, lighten up: My books tend to be very serious. Bad things happen all the time to good people. The fate of the world hangs in the balance again and again and again. It’s kind of like Buffy’s tombstone from the finale of the fifth season of Buffy The Vampire Slayer — “She saved the world. A lot.” I’m not suggesting this is a bad thing. People return to my books because I keep the stakes high, and they like that.

And the stakes could not be higher in the Chalice War books. The fate of our world is balanced on a knife’s edge throughout all three volumes. Serious stuff.

But people who know me know that I enjoy laughing and that I joke around a lot. And in these books, really for the first time in my career, I rely heavily on humor. I won’t go so far as to call the books “light-hearted” or “romps” — the series is action-packed, and, as I say, the stakes could not be higher. Still, there is a lot in these pages that made me laugh as I wrote, and I expect the books will make my readers laugh as well. A lot.

Limit the number of POV characters: Early in my career, when I wrote my big, fat epic fantasies (The LonTobyn Chronicle, Winds of the Forelands, Blood of the Southlands), I used a vast array of point of view characters. I was writing big sweeping stories and had a cast to match. I went from those to Thieftaker and Fearsson, which both had, basically, one POV character (the first chapters of the second and third Fearsson books were written in other POVs, but then both books reverted to Jay). Noir-style mysteries, I felt, worked best when told from the perspective of the investigator. Later books (Islevale, Radiants) fell somewhere in between — more than one, but not as many as those huge stories I told early on.

With this newest trilogy, I tried something a little different. I needed more than one POV character, but I wanted to have a maximum of three in each book. And that’s pretty much what I did. Chapter one of books I and II are from different POVs, but after that I have two POV characters in Stone, the first book, and three POV characters in the others.

And I like the way the novels read with limited casts of this sort. There is enough variety in the voices to propel the books forward with each POV shift, but there are few enough narrators that my readers can grow comfortable with the characters and their personalities. Obviously, every story is different, and what works with one series won’t necessarily work with another, but going forward, I will look for opportunities to limit my cast of narrating characters to more manageable numbers.

I hope you will check out the new series. I really do believe you’ll enjoy the books.

In the meantime, keep writing!

Blogging, D.B. Jackson, David B. Coe, editing, Writing

Professional Wednesday: Eliminating Excess Verbiage, Part II

Last week, I revisited an old Magical Words post I’d done about eliminating excess verbiage in our writing, putting a new spin on the discussion. As promised, I would like to continue that conversation today.

Before I dive back into the topic, though, I would like to address what might seem like a basic question: Is more concise always better? To my mind, concise is ALMOST always better. I can imagine situations — perhaps when writing a period piece, or trying to do something stylistically with a particular narrative voice that we want to be stuffy and verbose, or scattered and therefore wordy — in which concision is not a desired goal. But those are pretty specific instances. For the most part verbosity is not a style, but is rather a hindrance to effective storytelling. In general — and again I will accept that there may be a few exceptions to this — wordiness gets in the way of flow, of clarity, of linguistic precision. Others might disagree, and I would be open to debating the issue over beers. But I am skeptical of any argument that presents excess verbiage as a virtue.

In last week’s post, I covered passive writing, distancing phrases, and using mannerisms of speech in our prose. Let’s move to this week’s topics.

Adverbs: Yes, there are Adverb Authoritarians out there who will tell you that every adverb is an abomination, that none of them is necessary. I disagree. Used sparingly, adverbs can add to our prose, refining the meaning of our sentences and bringing more clarity, not less. Having said that . . . . A few years ago, when I edited the three volumes of my LonTobyn Chronicle in preparation for their re-release, I found way, way too many adverbs in the text, and I eliminated ninety percent of them. For the most part, adverbs add clutter, and often wind up being redundant.

So often, in my own older work as well as in the stories and books that I edit for others, I have found constructions like these: “He glanced at her briefly.” “She tapped lightly on the door.” “They ran quickly across the field.” None of those adverbs (“briefly,” “lightly,” “quickly”) is necessary. A glance is always brief; that’s why it’s a glance. A tap is light by definition, as opposed to a “knock” or a “rap” or a “pound.” And running suggests relative quickness. You rarely hear anyone say, “They ran slowly” (unless they happen to be commenting on my running speed . . .). Again, I would be reluctant to say “never use adverbs.” But I would say before using them, make sure the word is needed. More often than not, I believe you’ll find they add little to your narrative.

Weakening words: I am SO guilty of this one. I constantly need to look through my work to weed out words like “somewhat” and “a bit” and “slightly.” Or else I start phrases with things like “He found that . . .” or “She tended to . . .” All of these words make my prose mealy and soft, wordy and weak. It’s not that EVERY phrase has to be definitive and strong. Of course there are times when we want to soften a statement or qualify it in some way. Words and phrases like these become problematic when they occur as crutch words, as things we throw in without thinking because we can’t find a better way to write the sentence. And all writers do this on occasion. I have a list of manneristic words and phrases that crop up in my prose. When I finish the first draft of a manuscript, I do universal searches for all the crutch words on that list and I do my best to eliminate as many of them as possible. And too many of them are weakening words like these.

Beginnings and starts: These are a bit like passives, in that they clutter up and weaken verb phrases. Instead of “He ran,” we write “He started to run,” which says essentially the same thing with less power and in twice as many words. In almost all instances, we don’t need to be told that a character “started” or “began” to so something. A few sentences ago, they weren’t doing it. Now they are. We can assume that somewhere in the interim, they started doing it. This really isn’t complicated.

Now, as with many of these other issues, some instances of “started” or “began” are necessary. There are moments when the initiation of a certain action is, in fact, significant and worth noting. But those moments are pretty rare. For the most part, in my experience editing other people’s work and revising my own, I find these phrases to be empty and unnecessary.

Dialog tags and name checking: I could devote an entire post to writing decent dialogue and tagging speakers in subtle, effective ways. Actually, I’m sure I have written such a post. Still, it’s worth repeating a few key points. We don’t need tags for every line of dialogue. I often go through early drafts of my work and take out tag after tag after tag. As with other writing “rules,” I don’t subscribe to the “never do this” approach to dialogue tags. There is a place in good writing for “She said” and “He asked.” I’m merely pointing out that we often overuse these phrases. I would suggest you read through your dialogue and remove any tags that are not needed to clarify who is speaking when. In conversations between just two characters, that will be most of the tags. In conversations involving several characters, tags become crucial clarifying tools, requiring us to keep a far higher percentage of them.

“Name checking” refers to having one character address another by name in written dialogue. In most cases, we simply should not do this. Don’t believe me? Go ahead and initiate a conversation right now with a friend or a partner or someone else in your life. And use their name in every other sentence. “How was work today, Nancy? Did you have lots of meetings? Who were they with, Nancy?” Etc. It won’t take you long to realize that you sound ridiculous.

Now try doing it every fifth sentence. That will sound ridiculous, too. Trust me. Aside from moments when we’re calling to one another from another room, or something of that sort, Nancy and I can go for days without using each other’s names. Most of us are like that. Name checking makes our characters sound weird and unrealistic. And it clutters up our prose.

Keep writing, whatever your name might be!

Bell Bridge Books, Belle Books, Blogging, D.B. Jackson, David B. Coe, editing, The Chalice War, Writing, Zombies Need Brains

Professional Wednesday: Eliminating Excess Verbiage, Part I

The Chalice War: Cauldron, by David B. CoeAs I mentioned in a recent post, I have been doing a tremendous amount of editing and revising these past several months. Between co-editing (with Edmund Schubert) the Artifice and Craft anthology for Zombies Need Brains, revising my upcoming Chalice War trilogy, and working on manuscripts for clients of my freelance editing business, I have been through literally half a million words of text! And that is to be expected. Books and stories require careful editing and committed revision to reach their fullest potential.

During this time I have noticed, in my own work and in the prose of others, certain phrases and verbal habits that make our writing wordier, and therefore less effective, than it needs to be. Last week, I drew upon one of my old Magical Words post for inspiration to revisit a writing issue, and I thought I would do the same thing this week. Our topic today: cutting excess verbiage.

Just about all of us use more words than we should in our initial drafts. Hence that need for editing I mentioned above. With experience comes the ability to catch at least some of our worst writing habits. And yet, I have been writing professionally for more than twenty-five years, and I still fail to see all of them on my first revision pass. Fortunately, I have a wonderful editor who catches the wordy constructions I miss. (Be forewarned: She’s not editing this, so . . . well . . . yeah.)

Still, in revising my own work, and editing that of others, I have noticed a few patterns that all of us should watch for in our prose.

Passive constructions: Passing writing takes a number of forms, but at its most basic it uses weak verb constructions that rely on forms of the verb “to be.” These include “is,” “was,” ”are,”“were,” etc. Instead of “He ran” or “she speaks,” passive writers might say, “He was running” or “She is speaking.” Yes, in these examples passive constructions add only one word, but the damage goes far beyond word counts. Passive writing can flatten our prose, making it less powerful and less impactful. Or, put in another, stronger way . . . . Passive writing flattens our prose, robbing it of power, of impact. To state the obvious, we can’t remove every “to be” verb construction from our writing, at least not without relying on tortured syntax. Sometimes there is no other way to say what we want to say. (See what I did there?) We can, however, look for every opportunity to change a weak, passive phrase into a strong, active one.

Distancing phrases: When writing fiction, we should always be in a character’s point of view. Usually I try to avoid blanket statements of hard and fast rules, but I feel strongly about this. Point of view is the greatest tool we possess as writers. We should use it. One reason why? POV makes distancing phrases “he felt,” “she heard,” “they saw,” etc. unnecessary. “She heard cannon fire booming in the distance.” “He felt the house tremble with the rumble of thunder.” Those sentences are fine, but they’re unnecessarily wordy. In each case, we’re in a character’s point of view, and so the “she heard” and the “he felt” are redundant. If she experiences the sound, we KNOW she heard it. If he experiences the movement of the house, we KNOW he felt it. So . . . . “Cannon fire boomed in the distance.” “A rumble of thunder shook the house” or “The house trembled with a rumble of thunder.” Either works. Both are better than the original construction.

How about this one? “They could see dust rising from the road as a company of horsemen approached.” Here we have lots of unnecessary verbiage. Starting with the “They could see.” Again, we’re in a character’s point of view, and that character is part of the “they.” We also have the “as” phrase, which less experienced writers also tend to overuse. If we present cause and effect with clarity, words like “as” and “while” become unnecessary. So . . . “Horsemen approached, dust billowing from the road in their wake.” More concise, more powerful, more evocative. When we use words like “saw,” “felt,” “heard,” we TELL our readers what is happening. With more direct language, we SHOW them, which is always preferable.

Including mannerisms of speech in our prose: Humans are, as a species, remarkably inarticulate creatures. When giving advice on writing dialogue, I often tell writers to have their characters speak not as we do, but as we wish we did. This by way of eliminating “er”s and “um”s, “you know”s and “like”s, and all the repetitions and circularities of everyday speech. But there are other ways in which our speech patterns infect our prose. Just a moment ago, I started a sentence like this: “One thing we can do to improve our writing is . . . .” That is a TERRIBLE phrase. Just awful. I caught myself immediately and rewrote the offending sentence. Often, however, such phrases slip by our internal editors and find their way into early drafts. When we speak, we use roundabout constructions like that one to gather our thoughts, and we do it without even thinking. It’s a way of answering a question or opening a conversation with something other than a) silence, or b) inarticulate rambling. The thing is (and yes, “The thing is” is another example of the same phenomenon) when we write, we don’t need those filler phrases. Indeed, we don’t want them. They add clutter to our writing. We can’t possibly anticipate all the nonsense phrases that might slip into our prose in this way, but we can watch for them, recognize them when they crop up, and eliminate them.

Next week, I will continue this discussion of excess verbiage in our written work.

For now, keep writing!!

Blogging, D.B. Jackson, David B. Coe, Thieftaker Chronicles, Writing

Professional Wednesday: Adding Characters To Spice Up a Story

Many years ago, several of my writer friends and I were involved in a joint online venture — a writing blog called Magical Words, where we offered writing advice for free. We posted new content nearly every day, each of us taking one day out of the workweek to write, we commented on one another’s posts to create a writing dialogue, and we garnered a pretty significant following. The roster included regulars Faith Hunter, Misty Massey, A.J. Hartley, John Hartness, C.E. Murphy, Stuart Jaffe, Edmund Schubert, and me as well as a host of terrific guests including James Tuck, Mindy Klasky, Lucienne Diver, and Gail Martin, to name just a few. I know, quite a line-up, right?

How To Write Magical WordsWe kept the site going for nearly a decade (thanks Todd Massey), and the site still exists, for those interested in wading through the extensive archives. We also produced a writing book, which is still available.

I bring all of this up because recently I have been thinking about the advice I offered on that site, with the idea of revisiting some of the topics. And I’d like to begin doing that today . . . .

I have posted before about different ways we might breathe life into a story, book, or series that has gone a bit stale. This is a fairly common problem, one I have dealt with throughout my career, and one I have thought about recently as I contemplate what I might do with a new Thieftaker installment, or a return to one of my other projects.

A great bit of advice in this regard comes from Faith whose approach to the problem is fairly simple, not to mention ruthless. When your plot starts to feel flat, she has often said (paraphrasing here), kill off a character. This will change your story’s dynamics, give your writing a burst of emotional power, and almost certainly result in shifts in narrative tectonics you can’t even anticipate. And I agree with this: It’s a great way to shake things up. But there is another way to breathe life into an older project, and it’s actually the direct opposite.

One of my favorite characters in the entire Star Trek franchise was Ensign Ro Laren (played by Michelle Forbes), the Bajoran-rebel-turned-Starfleet-officer. She was introduced to viewers of Star Trek: The Next Generation in an outstanding episode that aired in the 5th season, and it was clear from her very first scene that she would be a terrific character. She was surly and abrasive, disdainful of authority and deeply proud of her Bajoran heritage. Starfleet was always portrayed as the ultimate melting pot — characters from different planets were expected to subsume their native cultures to the shared values of the larger organization. She refused, which made her compelling, fascinating even. Adding her to the cast shook up the somewhat tired dynamics of the show and yielded several memorable episodes.

Buffy the Vampire Slayer, another of my favorite series did something similar in its third season, when it introduced a second slayer, Faith Lehane (Eliza Dushku) to the mix. Faith joined Buffy’s Scooby-gang, but she brought a rebellious, morally-ambiguous quality to the show that had been missing previously. She disrupted Zander and Willow’s friendship, defied Giles’s authority, corrupted Buffy, and eventually turned on her, becoming a dangerous rival. Again, the addition of a new character altered familiar dynamics and infused the franchise with new drama and energy and power.

A third example: My favorite show of all time is The West Wing, which, in its second season, introduced a character named Ainsley Hayes (Emily Procter) to the Bartlet White House. Ainsley was a Southern conservative Republican, whose political views were diametrically opposed to those of Josh, Sam, C.J., and Leo, and whose keen intelligence and sharp wit made her a worthy foil for all of them. The West Wing hadn’t had time to grow stale at that point, but Aaron Sorkin, the show’s creator and chief writer, seeing the potential for such a thing, acted preemptively. By adding Ainsley to the cast, he sent the show in new and unexpected directions and brought additional tension, humor, and resonance to a show already brimming with those qualities.

Three different shows, three powerful, dynamic women added to the storylines. In each case, the addition of one character completely altered the tone and feel of the series.

The lesson here should be fairly obvious. Yes, killing a character can jump-start a plot. I use that approach quite often. But adding a character can do much the same thing. And if I am working on a longer project — a multi-book series — I often find that killing off someone important isn’t enough to infuse the franchise with the needed energy. Introducing a new character, however, particularly someone who is going to prove disruptive to my plotting and uncomfortable for my established characters, can really shake things up. And sometimes that’s exactly what we need.

Storytelling is about conflict and tension. When we find a book or series going flat it is usually because those two qualities — conflict and tension — are missing, or at least lagging. That’s why it’s not always enough to add just any new character. Sure, a new love interest or sidekick can spice things up a little. But if this new person fits in too comfortably, the point of adding them might well be lost. If instead we bring in someone who is going roil the metaphorical waters, we stand a much better chance of achieving the desired result: namely more drama, more emotion, more trouble for all concerned. Our readers will eat it up.

Keep writing.

Blogging, D.B. Jackson, David B. Coe, editing, Writing

Professional Wednesday: When To Fight an Edit, and When To Let it Go

I know my knee-jerk response is not always my wisest response.

All of us who have gone through the editorial process are familiar with the conundrum: We want to work with our editors. We want to cultivate reputations for being easy to work with, cooperative, flexible, etc. No one WANTS to be known as a prima donna. At least almost no one. But then we find that our editor (or our copy editor, or our proofer) has altered something we didn’t want altered, killed a darling we weren’t willing to sacrifice. What do we do? Do we dig in our heels in order to keep the original wording, carving “STET” (editorial speak for “let it stand”) into the manuscript with a bloody blade? Or do we give in, though it hurts physically to do so?

Put another way, when do we as writers fight for wording we want, and when do we acquiesce?

Over the past few years, I have been both editor and writer on a number of stories and novels. I have felt the sting of having passages I have written, passages I care about, altered by an editor, and I have also had writers reject editorial feedback I have given that I know, with every fiber of my being, would make their work better. I haven’t enjoyed either experience, yet I have come to see that both are natural, even necessary, outcomes of the literary process.

At its best, the relationship between writer and editor is collaborative, cooperative. It necessitates compromise. Some of our darlings won’t survive the process. Some of the editor’s suggestions will be rejected. Early in my career, I worked with an editor who had far, far more experience than I did, and this editor expected that I would defer in most if not all cases. Our interactions often left me feeling bullied, and there were changes the editor insisted upon that I wish I had rejected. I have also, in my editorial capacity, worked with writers who refuse all suggestions. All of them. Neither extreme is likely to produce the best possible version of the story, which, of course, ought to be the entire point.

So, as writers, how do we decide how hard to push back, when to compromise, when to insist on our wording or approach? And as editors, how insistent should we be?

Let me begin by addressing that last question, because in many respects it’s the easiest to answer. In my capacity as editor, I feel it is my responsibility to point out to my writers anything and everything I can see that I believe needs to be fixed in order to improve the story or book. I will offer possible solutions — alternate wording or potential fixes for narrative issues, but none of what I suggest is meant to be the only possible approach. My purpose is to point out a problem. The author can fix it any way they choose. Or they can decide it’s not a problem. And, generally speaking, if an author decides the problem I have identified is NOT in fact a problem, I will respect that decision. Every now and then, if I believe the issue is serious enough and the author decides initially that they don’t agree, I will mention the issue again and explain why I think it matters, and how it might be addressed without changing too much. After that, I won’t say more. It’s the writer’s story, after all. Their name is on it, not mine.

And in my capacity as writer, I follow the same principle. It is my story. My name is on the byline, not the editor’s. Now, having said that, I also have to add that I accept the vast majority of my editors’ suggested fixes, and I always take seriously any problem they identify. Why? Because my editors are professionals and they know what they’re doing. Because we writers can’t possibly see every flaw in our work; we’re simply too close to it. Because I am far from perfect. And because I trust the process and I understand the editor-writer relationship is not adversarial; my editor’s goal is my goal: to make the story as good as it can be.

So how do I decide when to stick to my guns and when to give in on an issue of wording or style, plotting or character work?

1. I give the matter some time to percolate. The truth is, often when I disagree with something my editor suggests, my first impulse is to resist, to refuse, to insist on having things my way. And so, when reading through an edited manuscript, I will mark the issue as something to return to later. I essentially stick a pin in it. Because I know my knee-jerk response is not always my wisest response.

2. When I return to the issue, I try to see what it is the editor is pointing out. Remember I said earlier, in talking about editing, that editorial suggestions are just that: suggestions. They are a way of saying, “There’s a problem here.” Good editors do not add, “And you need to fix it my way.” So I try to see the issue my editor has identified, and for the moment I ignore their suggested solution. Much of the time, I can find edits that preserve the tone I want while also addressing the problem the editor has identified.

3. If, after some time and some careful consideration, I still find myself disagreeing with the edit, I ask myself how much it matters to the book. Is this issue worth an argument? Quite often, they’re not. I take pride in my writing and I craft each word, because I want my books and stories to read a certain way. But I know many of my readers don’t take the same care in reading a book that I take in writing it. That’s natural. So, are readers likely to notice if I change this in some way? If the answer is no, the issue is probably not worth fighting over. It’s just up to me to get over myself.

It’s worth noting here that, generally speaking, issues related to style and wording are important but not crucial. Questions touching on narrative issues — plotting, pacing, character — are fundamental, and so I am far, far more likely to insist on having my way in these instances. A few series back, I rejected a number of edits suggested by an editor because I knew they were wrong and I felt certain the edits they suggested would ruin the book. I got my way. And I never worked with that editor again.

4. Finally, if I have given myself time to settle down, if I have decided the issue is one I care about, if I have decided that making a change is going to impact materially my readers’ experience, I will insist on keeping the wording or narrative point as I originally wrote it. STET that sucker.

But as you can see, even with my conviction that we authors should always have the final word (It’s. Our. Book.) I do all I can to respect and take seriously the work done by my editors. It’s worth saying again: Editors and writers are allies. We work together to make a manuscript as good as it can be. Editors who push too hard, and authors who are too resistant to changing anything, undermine the editorial process. They may think they are scoring points in some ridiculous battle of ego and control. But all they are doing is hurting the manuscript, which benefits no one.

Keep writing.

Blogging, D.B. Jackson, David B. Coe, Writing

Professional Wednesday: What Holds Me Back, part II — Building a Platform

Last week, I started my newest series for the Professional Wednesday feature: “What Holds Me Back.” My first entry was on life in general, and the ways in which we learn to cope with life’s intrusions on our creative output.

This week I would like to shift my focus a bit to more writing-specific obstacles that can hold us back in one way or another. As it happens, there are a lot of them, so it may be this series will stick around for a while. But let’s begin with all those things that fall under the heading of “building our platform.”

Children of Amarid, by David B. Coe (jacket art by Romas Kukalis)I’ll preface this discussion with the obvious: I’m old. I’ve been in this business for a long time — it’s been nearly three decades since I signed my first contract. When I got started in the business, publishers were just beginning to expect that writers would maintain websites. Websites! Facebook and Twitter and the rest didn’t even exist. And when we signed contracts, writers could rightfully expect that our publishers would handle the bulk of the necessary publicity, which consisted mainly of taking out ads in journals, sending review copies to print magazines (kids, ask your parents) and other critical venues, setting up newspaper, radio, and television interviews, and arranging signing tours and individual store events.

My point being that the days of publisher-centric publicity have long since passed. Our jobs as writers have become far, far more demanding in so many ways. In the age of self-publishing, many of us are now required to get our own jacket artwork, to arrange for our own editing, to typeset our own books. But in today’s marketplace, ALL of us are responsible for creating audiences for our books. We are the ones who advertise our releases, who set up events, who make our marketing decisions. And social media gives us the opportunity to interact with and get to know our fans in ways I never would have dreamed possible at the outset of my career.

More than ever, we are not just writers. We are publicists and advertisers. We maintain our social media presence, and many of us also create additional content for blogs. All of these things can be time-sinks, and therein lies the danger. I know of many writers who, at the outsets of their careers, become so obsessed with “building a platform” or “establishing a fan base” or “finding their readership” that they leave themselves no time to do the one crucial thing all writers have to do to be successful: write their stories.

Yes, I am aware of the irony. Here I am blogging about the perils of spending too much time on one’s blog (among other things). But the danger is real, and it can become a trap for many. After so many years as a professional writer, I have gotten to the point where I can be productive on demand. I can turn out two one-thousand-word blog posts in a day and still have time left over to edit a couple of story manuscripts for the anthology, or I can get a couple of thousand words written on a work-in-progress and then write a thousand words more for the blog. I couldn’t have done this early in my career; writing in volume and switching gears among various professional tasks are skills I have developed over years. I think if I had started my career ten or fifteen years later, I would have struggled mightily to build my audience and simultaneously write my novels.

I have managed to maintain the regular Monday and Wednesday features of this blog, to turn out material on a regular basis, by making blogging a habit. I devote one day a week — usually the same day each week — to getting the posts written. Yes, I am sorry to blow-up such a carefully maintained illusion, but I DON’T write my blog posts on the days they go up. Sometimes, when I know I’ll be traveling during a given week, I will have posts, particularly the Professional Wednesday entries, scheduled a week or two in advance. I try not to allow post deadlines to loom. Why? Because currently I enjoy maintaining this blog and I don’t want it to become A Thing I Dread. And more to the point, I don’t want it ever to get in the way of work I have to do.

The Chalice War-Stone, by David B. CoeBlogging and social media are extras. Yes, in this day and age, they are important extras. Crucial, some might say. We have to publicize our books, or no one will buy them or read them. But as vital as this part of the job might seem, I would once again turn the previous phrase on its head: We have to publicize in order to be read? Yes, we do. But more important by far is this: We have to write the books in order for any of that publicity to be worth a damn.

Writers write. As I said earlier, the single most important thing we can do to further our careers, to build our audiences, to draw the notice of the industry, is write our fiction (or non-fiction, if that’s your thing). If you can maintain your output while also spending time each day blogging and feeding the social media beast, good for you. You’re more accomplished than I am. But if you find that you’re not getting as much done on your stories and books as you would like, check to see if maybe you’re spending too much time on the other stuff. And if you are, make the adjustment.

Platforms are great. But if you don’t have books to sell from them, all you’ve got is a flat expanse of wood.

Keep writing.

Blogging, Case Files of Justis Fearsson, D.B. Jackson, David B. Coe, LonTobyn Chronicle, Writing

Professional Wednesday: My Best Mistakes, Part III — Reviews, Damn Reviews, and More Reviews

Continuing the “My Best Mistakes” series of blog posts . . . .

Children of Amarid, by David B. Coe (jacket art by Romas Kukalis)Very early in my career, when my first book, Children of Amarid, was the only one I had out, I responded publicly to a online review from a less-than-delighted reader. Amazon was still a novelty (no pun intended) as was the notion of online reader reviews. (Hard to imagine, right? That the idea of readers offering reviews of the books they’d read should have been new and different and even a bit odd?) I don’t remember what the reader in question objected to about the book, nor do I remember what I said in my public response. The original book is out of print now — only the 2016 reissues are available on the site, so our exchange is lost to the ages. All I know is that someone criticized the book, I didn’t take the criticism well, and I took it upon myself to write a reply and post it to the Children of Amarid Amazon page.

But that’s not quite what this post is about.

SPELL BLIND, by David B. Coe (Jacket art by Alan Pollack)Some years later, soon after the release of Spell Blind, the first book in The Case Files of Justis Fearsson, another Amazon reviewer panned the book because my book was “a blatant rip-off” of Jim Butcher’s Harry Dresden books, “a ludicrous case of copycatting.” For the record, I didn’t copy Dresden at all. I had only read the first two books of the series, and the “copycatting” the reviewer claimed I’d done amounted to using tropes of the genre, not elements of Butcher’s work. And so I responded to the review, wanting to set the record straight.

But that’s not quite what this post is about.

At this point, you might have sensed that I have a problem. There are writers out there, I know, who couldn’t care less about bad reviews of any sort. Clearly I am not one of them. It’s not that I’m thin-skinned. Well, not really. If people don’t like my books, so be it. I write for me, because I understand that we can never please every reader. Even if ninety-nine readers out of a hundred love our book, there will always be that one reader for whom something just doesn’t work — the characters or the setting or the magic or the prose. Something.

My problem, and I know I am not alone in this regard, is that I can get all those nice reviews, but the one on which I’ll fixate, the one I’ll remember, is the lone bad one. I think it’s tied to imposter syndrome, and to every other insecurity I have as a writer. And as I say, I know I’m not the only professional who is like this. Certainly, when I see a review that misrepresents my work, or impugns my professional integrity, I can’t help but obsess over it a little. That’s what happened with both of the examples I’ve already cited.

That’s what happened with another book in another series, which was reviewed in a fairly high profile publication. As it happens, this third review was mostly positive. The reviewer liked the book. But they also said something about the book, a mild criticism, that I felt was simply untrue. I didn’t respond publicly. I sent the author of the review a private message, thanking them for their kind words about the book, but pointing out that they had gotten it wrong in this one regard.

Why did I do this?

Because I’m an idiot. Because despite my protestations before, I AM thin-skinned about my books. I take editorial feedback really well, but I respond terribly to public criticisms that I feel are unjust or inaccurate. To my mind, reviewers — professional reviewers, those who merely comment on bookseller sites, and all in between — ought to keep in mind that their words can have an impact on people’s livelihoods. If they have legitimate criticisms, so be it. But they need to take care to get their facts straight. Okay, off my soap-box.

Where was I? Oh, right. I sent a private message to the reviewer. I never heard back from this person. But they reviewed my next book, and they took their revenge. Publicly. Brutally. Cruelly. Their review of that next book was one of the most humiliating things that has ever happened to me in my career. It was unfair. It was relentless. It misrepresented the book. The review left me heartbroken, because I loved the book. Still do. And I am certain this review came about as a direct result of that message I sent after the first review. It was my fault. True, the reviewer didn’t have to take their revenge in the way they did, but still, I should have known better.

Because writers are told again and again never to respond to reviews. Most people will tell writers that they shouldn’t even read their reviews. Clearly, I have struggled throughout my career to follow both these bits of advice. In fairness, I have finally gotten better about all of this. I do not respond to reviews anymore. I rarely read them. But as mistakes go, this was a big one, and it is one I’ve made too often.

Don’t do what I did. Write your book and move on to the next. Promote the hell out of every publication. Pay attention to your sales numbers. Don’t worry about your reviews. Don’t go to your Amazon pages and scroll through the ratings. If you have to read your journal reviews, so be it. Who am I to criticize? But don’t obsess over them. Don’t fixate on the negative phrases. And for God’s sake, don’t respond to them.

And if you can do all that, you’re a better person than I am.

Keep writing.

Blogging, D.B. Jackson, David B. Coe, Writing

Professional Wednesday: My Best Mistakes, Part II — A Bad Contract Is Worse Than No Contract

Last week, I kicked off the latest Professional Wednesday blog post series, “My Best Mistakes,” with a humorous story about my behavior at a convention early in my career. I hope you enjoyed it.

This week, I turn to more serious matters, because the fact is certain mistakes can have serious consequences for our careers. Before I begin, let me reiterate something I wrote in last week’s post: Some of the stories I tell in this series of posts will include other people in the business and/or will touch upon published works of mine that I am still seeking to market. In the interest of discretion, I will be keeping some details purposefully vague.

The events I’m going to describe took place many years ago, as I was putting the finishing touches on one of my early epic fantasy series, and I was looking forward to my next project or projects. This is common for writers even today. We are often a book or two ahead of the publishing schedule, particularly if we publish traditionally. And so as we are waiting for the last book or two of a series to wend its/their way through the production process, we are usually turning to the new shiny. And this was especially the case back in the years I’m talking about here, when self-publishing was not yet a Thing, and big-house traditional publishing was excruciatingly slow.

I had recently met a small press publisher at a convention, and this person expressed interest in publishing my next work. This publisher was ambitious, articulate, charming, and seemed to know the business. Put another way, they talked a good game. They had some big name authors writing for them already and they made it very clear they wanted to add me to that mix. It was flattering really, and they probably knew it.

To that point in my career, I had only written for Tor Books. Tor was and is a great house. Their reputation is global, as is their marketing reach. They brought me out in hardcover with all of my early books, as they did almost all their writers. They put out a beautiful product, they took out big, glossy ads in Locus and the Science Fiction Chronicle. They hosted THE big party at WorldCon each year. There was, in short, a certain cachet that came with being a Tor author. And I liked that. On the other hand, even as my star was rising early in my career, I remained a small fish in the big pond that was Tor.

And so, being a relatively big fish in the pond of this small publisher had some appeal. Add to that the fact that this publisher offered to match or beat the numbers in my most recent contracts with Tor, which had been generous, and I was eager to give working with this person a try. Never mind that all of it sounded too good to be true. I wanted in.

I signed a contract for several books. And if the publisher needed a little extra time to come up with the promised advance . . . well, it was a small press after all. It was understandable, right?

No, not right. That was our first warning that all was not as it should be, although it shouldn’t have been.

So far, I have made it seem the only problem with the contract I signed was that the small press publisher couldn’t do all they promised financially. But there was more to this episode than that. The books I sold them weren’t ready either. The concept needed a ton of work, something I didn’t realize at the time, didn’t WANT to realize at the time. But it’s true. I would later publish a much-changed iteration of this concept with a different publisher, but back in the mid-2000s, when all of this took place, the books were a shadow of what they could and should have been. The publisher’s failure to see the flaws in the original concept should have been a warning as well.

All of that said, I eventually did get my initial advance, and I eventually turned in the first book. When I got it back from the publisher, who was now also my editor, the manuscript was very nearly unmarked. “Looks great. Found a few typos and phrases that don’t quite work. Get the revisions back to me as soon as possible.” That’s a paraphrasing of the feedback I received, but it’s an accurate one and it set off alarm bells in my mind. I knew the book needed more. I didn’t yet know how much work it needed, but I knew it wasn’t essentially publication-ready. As it turned out, this was another sign that my publisher’s resources — financial, yes, but also in terms of time and human resources — were spread way too thin.

Within eighteen months of my signing the contract, the small press was on the brink of bankruptcy. We managed to get back the rights to the series, but only because my agent and I acted quickly and decisively. The series could have gotten caught up in the bankruptcy proceedings and then we might never have been able to sell the later iteration of the books to a different publisher. The publishing company folded not too much later. As far as I know, the publisher/editor I worked with briefly is no longer connected to the publishing world.

So, what are the lessons here? Let me start by saying that the lesson is NOT to avoid working with small presses. I have worked with several in recent years and, with one other notable exception, have had great experiences. Small presses are, to my mind, the future of the industry and a wonderful option for writers of every experience level.

No, the lessons are these:

1) If the promises made to you by a publisher (or, for that matter, by an agent) sound too good, too optimistic, too perfect, take a long, close look at the contract and at all the information you can find about the enterprise. Talk to other authors who have worked with them. Learn all you can. We all like to be told what we want to hear. We all want to feel wanted by our publishers. But flattery and rosy scenarios are no substitute for solid information. Because the old adage holds true: If it seems too good to be true, it probably is.

2) Don’t rush into anything. Don’t rush to get that first contract signed, unless you’re truly confident you’re a good match for the publisher. Don’t rush to bring a book or series to press unless you’re certain it’s ready. Don’t hurry into any publishing arrangement because you need the money quickly. Actually, that’s probably good advice for any business venture in any field. But it’s particularly important when we’re peddling our intellectual and creative property. If we rush into selling, say, a car, we might not get as much as we should. But if we rush into a publishing contract we can lose access to our artistic creation. If my agent and I had waited another month or two, that’s what would have happened with this series of books. Better to be patient. Better to delay the realization of our ambitions than to destroy any chance of realizing them.

And 3) Beware, beware, beware. The vast majority of the people I know in the publishing industry — writers, editors, agents, publishers — are honest and hardworking. They are in the business because they’re passionate about books and stories, and they want to do good by the people with whom they work. But there are a few — yes, I could drop names; I won’t — who are in it to make a buck, and don’t care who they hurt along the way. There are others who through malign intent or sheer incompetence seem to turn to shit everything they touch. Before you sign to work with anyone, make certain you know what category they fall into.

Keep writing!