Tag Archives: Galactic Stew

Professional Wednesday: Writing For a Themed Anthology . . . And My Story Idea Revealed!

With the Zombies Need Brains Kickstarter well underway, and our pledges slowly creeping up on our ambitious funding goal (four anthologies instead of three this year, to mark ZNB’s 10th anniversary!), it is time for my yearly “Writing For a Themed Anthology” post. This post, though, has a bit of a twist, which I’ll share with you at the end of the essay.

This year, I am hoping (Kickstarter gods allowing) to co-edit Artifice and Craft, with my dear friend, Edmund R. Schubert. Edmund is an experienced editor, a fantastic writer, and one of my very favorite people in the world. He and I have been friends for a long, long time, and have worked together on many projects. He edited and contributed to How To Write Magical Words, the book on writing I co-wrote with A.J. Hartley, Faith Hunter, Stuart Jaffe, Misty Massey, and C.E. Murphy. He also edited a couple of my short stories when he was lead editor of the Intergalactic Medicine Show. And I edited a story of his for Temporally Deactivated. We have, however, never co-edited before this. I’m excited.

GALACTIC STEW, edited by David B. Coe and Joshua PalmatierThis will be the fifth anthology I have edited for ZNB (after Temporally Deactivated, Galactic Stew, Derelict, and Noir). For each of them, we have had literally hundreds of submissions for about seven open slots. Getting a story into these anthologies is really hard. We editors have the luxury of being highly selective, because we have so many stories from which to choose.

I have found that no matter the theme, there are recurring categories of stories my co-editors and I tend to reject. The first category is fairly obvious, and encompasses the vast majority of rejections: Some stories just don’t work for one of several reasons. The writing might be too rough, the prose unclear and inelegant; the plot might be too hard to follow (or even indecipherable); or the character development might be weak. Put another way, some stories simply aren’t ready for publication. This is fairly self-evident. When reading slush, we expect to encounter a lot of stories that need too much work to be up to standard.

But then there are two other categories that are far more important for our discussion today.

A) Some stories we get are beautifully written and have really fine core ideas. But they fail to move beyond their conceptual strengths and delve into the emotional and narrative potential of those ideas. I can’t tell you how often we read stories like these, and it’s deeply frustrating. Yes, a themed anthology demands stories that have strong conceptual underpinnings. But the idea is only as good as the story it inspires. It’s not enough to show us the great idea. Authors need to develop those ideas, to give them meaning by building compelling characters and creating tension and suspense and all the other emotions that come through in effective storytelling. So if you submit a story, make sure you give us more than an idea. Give us a fully realized story.

B) Some stories we get are brilliantly written AND developed beyond the conceptual to dive into emotion and character arc and all the rest. But they’re not on theme. This year’s theme for our anthology, Artifice and Craft, is pretty simple. The story needs to have at its core some piece of art that has magical or supernatural qualities. It can be any kind of art, from a painting or sculpture, to a theatrical production or musical composition, to a piece of fine furniture or a piece of short fiction. It’s not enough to have the work of art in the story. It needs to be central to the plot, so that if the work of art were taken out, the entire story would collapse. We will make this clear in the call for submissions. And yet, I can guarantee you that we will receive dozens of stories that aren’t at all on theme, or that, for instance, feature a magical artist who creates great art (which is NOT on theme) or that mention a magical novel, but focus on a scheme to steal the book, rather than on the book itself. (Again, that is NOT on theme, because you could replace the book with, say, a diamond, and you’d have the same basic story.)

So make certain you are following the theme as it is described in the guidelines. Make sure you are doing more than just jotting down an idea, that you’re developing that idea with character work and emotion and tension and conflict and all the other good stuff we writers like to do. And then go to town! Because writing for anthologies is really fun.

Finally, allow me to share with you my own story idea. I am editing Artifice and Craft, but I am also an anchor author for Dragonesque, which will be edited by Joshua Palmatier and S.C. Butler. The theme of Dragonesque is dragon stories written from the point of view of the dragon. Fun, right?

So, the dragon in my story is going to a re-enactor, a dragon who does Renaissance Faires and such. Each weekend she allows herself to be “slain” by a knight, and in return she is paid in gold. Except, she’s getting tired of losing all the time, of letting herself be humiliated by these pretend knights. And during the weekend on which my story focuses, she decides to take matters into her own talons, as it were . . . .

Our Kickstarter is going well. We’re about 2/3 of the way to our funding goal. But if I’m going to write my dragon story, and if Edmund and I are going to find the best magical-work-of-art stories available, we first have to fund the anthologies. So if you want to read great short fiction, and/or if you want to have four new anthologies to which to submit your work, please consider supporting the project! Thanks so much!

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: Short Fiction Anthologies — When Does an Idea Become a Story?

Galactic Stew, edited by David B. Coe and Joshua B. Palmatier What is the difference between an idea and a story? It sounds like a basic question, but we have just begun the Zombies Need Brains Kickstarter for the coming year’s anthologies, and once again I am hoping to co-edit one of the collections. (This year, I co-edited the Galactic Stew anthology; last year it was Temporally Deactivated. I also had stories in both, writing as D.B. Jackson.) In past years, one of the most common issues we have found with submitted stories is that they fail to move beyond being an idea. They introduce a concept, often an intriguing one. But that is all they do.

Hence today’s post.

Temporally Deactivated, edited by David B. Coe and Joshua B. Palmatier I have touched on the subject of creative ideas in other Writing-Tip Wednesday posts this year (here and here), and I have also spent a bit of time on tips for short fiction writers (here). Today, though, I would like delve in a bit deeper, in order to spell out what distinguishes a story from a partially developed idea.

Let me begin with this: Every successful fictional story blossomed from an idea. Not every idea yields a story. That’s just fact. Some of the “best” ideas I’ve had kind of fizzled out before becoming anything close to a story. I find this frustrating of course. I expect all writers must. But, as I say, it’s simply the way it is. Some ideas “have legs,” while others don’t.

The problem comes when we write an idea and submit it as a story. Not to be too simplistic, but a story has a beginning, middle, and end. It involves characters and emotion, and it carries those characters through changes that a reader can trace. Too often when reading through submissions for past anthologies, I have encountered pieces that introduce a concept and a set of characters, but do no more than that.

Let’s take a for instance: The theme for this next anthology I’ll be co-editing is “Derelict.” We are looking for stories about abandoned or wrecked ships, be they sailing vessels, spacecraft, or something else that we haven’t even considered. Someone might come up with an idea for, say, a haunted shipwreck (and I would urge you to look beyond this for an idea — we are going to get LOTS of haunted shipwreck stories) that traps the unwitting and makes them permanent members of the ghost crew still onboard. Cool idea, right? But what are we going to do with that idea? It’s not enough simply to show us a character being ensnared in this way. That is no more than an illustration of the idea.

It becomes a story when we follow a character through that transformation in a way that dips into emotion and creates a true character arc. Perhaps an elderly woman has come to an island from which her grandfather once sailed a hundred years before. She was estranged from her parents while they were alive, and has lost her siblings to age and disease. She seeks some connection to the family she has lost. Knowing that her great grandfather died here on the island in a storm a century ago, she goes out to the site of the wreck. While there, she realizes that ghosts still inhabit the ship, and venturing closer, she sees a man she recognizes from ancient family photos or portraits. She makes contact with him, but that isn’t enough for her. In the end, she chooses to join that crew and become a wraith like her grandfather, seeking in that ghostly partnership solace for all she lost in life. THAT would be a story. (In fact, maybe that will be my story for the anthology…) We have taken an idea and turned it into a narrative that has emotional weight, that allows our point of view character to develop and progress.

Coming up with the idea is only step one in a far more complex process. We want to think of the most unusual, emotionally potent way to express that idea. And, I would add that this is not something we can usually do in five hundred words, or a thousand, or even two thousand. I don’t like to say that word count is essential to a story, but the fact is true flash fiction is VERY hard to do well, particularly with intriguing speculative fiction ideas. It CAN be done, of course. But generally speaking, full development of an idea for a themed anthology — into a story that touches on emotion, that traces a meaningful arc for our main character or characters — demands that we write more than a couple of pages.

I would urge you to think about this as August gives way to September, and the open call for the Zombies Need Brains anthologies approaches. In the meantime, the Kickstarter is well underway. In our first week, we have already funded well beyond the halfway mark, which bodes well for the ultimate success of the campaign. But please consider helping us out. We have a great roster of anchor authors, and our list of authors chosen from open submissions could include you!

Best of luck, and keep writing.

Monday Musings: Learning to be an Editor

I’m pretty good at diagnosing both narrative trouble spots and problematic wording. Over the years, I’ve had tons of practice, having found plenty of both in my own work.

As I’ve mentioned here before, I am coediting an anthology, Galactic Stew, with my friend Joshua Palmatier. (The anthology will be out from Zombies Need Brains this summer.)

Joshua and I are done reading slush for the anthology and have selected those stories that will appear in the collection. Now we are on to the actual editing of the individual stories. I’m still relatively new to editing. Stew will be my second anthology, after last year’s Temporally Deactivated (also from Zombies Need Brains, also coedited with Joshua). I am still learning about the process, still gaining confidence in myself. Over the years, I have become pretty good at editing my own work (though NEVER to the exclusion of having outside editors), but editing the work of others is different, and challenging in unique ways.

The edits Joshua and I do on these stories is a combination of developmental editing and line editing. For those unfamiliar with the terms, a brief pair of definitions: Developmental editing focuses on improving story elements and larger narrative issues. Edits of this sort address structure, pacing, character arc, and a host of other matters relating to storytelling. Line edits, on the other hand, deal with issues of prose, syntax, concision, clarity, word choice, etc. It is, in a way, smaller in scope than developmental editing, though it is no less important to the ultimate success of the story.

For me, as a newcomer to editing, the challenge of both line editing and developmental editing does not lie in spotting the things that need fixing. I’m pretty good at diagnosing both narrative trouble spots and problematic wording. Over the years, I’ve had tons of practice, having found plenty of both in my own work.

Rather, the hardest part of editing for me has been trying to help authors fix problems in their stories while preserving their intent and their voice. The best editors I’ve worked with over the course of my writing career are those who help me make my work as strong as possible without making it any less my work. Identifying problems remains roughly the same, whether the issues are in my stories or the stories of others. Sure, it’s possible that a “problem” I see in another author’s fiction might be something they intended to do. The fact is, though, if it doesn’t work, it still needs to be fixed.

And that’s the hard part: coming up with solutions that remain true to the author’s overall intent, finding alternate wording that will fit seamlessly with the author’s style and approach, suggesting changes and fixes that make the story, as conceived, as good as it can be.

I’m still learning to do this well. It takes practice. It demands that I ask myself again and again if the change I’m suggesting is in keeping with the author’s vision and intent. The author-editor relationship is built on trust, and, speaking now as an author, I can say with confidence that nothing undermines that trust faster than the sense that the editor’s comments are making my story into something I don’t want it to be.

Receiving editorial feedback is always hard. As I’ve said before, just once I would love for an editor to come back to me with one of my manuscripts and say, “David this is perfect; don’t change a word.” But that’s never going to happen. I have never seen a perfect published book, much less a perfect manuscript. I’ve certainly never written either. Let’s be frank: It sucks having the flaws of our creative efforts pointed out to us. That, though, is the job of an editor. They/we don’t identify problems to be cruel, or to show how smart we are, or to engage in one-upmanship.

They/we do it to help authors realize the fullest potential of their stories and books. That may sound trite, like the worst sort of cliché, but it’s true. And early in what I hope will be my continuing growth as an editor, I am learning to do this.

Wishing you all a great week.