Apr 16

Technique: Parallel Stories, Slow Reveal

I review books from Netgalley, and I recently got two significant short story collections: Writers of the Future Volume 30 and Best Science Fiction and Fantasy of the Year: Volume Eight. So far, I’ve only read the first one, but it’s taught me something.

Of course, that’s exactly why I read it; I wanted to see what is considered really good spec-fic short story writing these days, rather than just reading classic short stories. I’ve been writing a few short stories lately, mostly for the collection I’m doing with HDWP Press, and based on the feedback I’ve had I seem to be getting better. I’m yet to sell a story to a major magazine, but I’ve had a very encouraging personalised rejection from Strange Horizons and some good comments from critique groups.

Part of the point of writing short stories is to improve my craft by working at the short length, and then take those lessons into my novels. Here’s the lesson I learned from several of the stories in Writers of the Future, which I call “parallel stories, slow reveal”.

The clearest and best use of the technique is in Shauna O’Meara‘s story “Beneath the Surface of Two Kills”. At the opening of this story, we learn that the narrator, a professional hunter, is hunting a rare animal for the last meal of a convicted felon on death row. As the story progresses, we discover more about the “two kills”: the one which the hunter is working towards, and the one which we know occurred in the past to place the killer in prison awaiting execution. The hunter thinks about the news coverage he has read of the killer’s stalking of his victim as he, in turn, stalks the rare beast.

This works for a few reasons. Firstly, the parallel stories obviously reflect on each other (and the conclusion differentiates the two characters). Secondly, as also happens with several other stories in the same collection, we start out knowing the ending of a story that occurred earlier, and gradually learn how that outcome occurred.

Now, given how some people react to “spoilers”, you’d think that would be a problem, but done well it actually keeps the reader’s interest. We know the outcome, but we don’t know how it came to be, and we want to.

Here are some ways I can think of to use the slow reveal:

  • Hint at something surprising about the character early on that doesn’t match up with what you’ve revealed about them so far.
  • Let the reader see a terrible (or wonderful) outcome looming, of which the characters remain ignorant until it happens.
  • As the story opens, let the reader know that the character feels a strong emotion (fear, anger, sadness) about something that happened, but don’t tell them why (or what) until later.
  • Show a character learning something that another character has already learned, and tell their stories in parallel.
  • This is a classic: Start the character out in a fix. Gradually show how they got into it as they struggle to get out of it.

Like any technique, this can be done badly and fail. Used well, though, it holds the reader’s attention and keeps them reading. Watch out for it in my future stories.

Mar 07

UPDATE: Anthology Plans

This is an update to my previous post, in which I announced a small short story collection.

I’ve now pulled that collection off Amazon, for the best possible reason. I’ve agreed with Charles Barouch of the small press HDWP Books to issue a solo anthology later this year under the HDWP imprint, including my contributions to HDWP’s Theme-Thology collections.

Charles’s vision for the anthology is that it’ll have 10 stories in total (there may be more). Here’s a partial summary of the contents, which includes the three stories I mentioned last time:

Good Neighbours: An elderly woman must answer the classic question: Who is my neighbour? (Formerly appeared in New Realm magazine in December 2013.)
2700 words.

Vegetation: In an old Elvish city, plants are everywhere. And goodness knows, someone has to look after them. A lighthearted, Wodehousian piece involving the petty politics of volunteer organisations.
2300 words.

Gnome Day: An idealistic young clerk helps out on the night the gnomes are freed, and meets three people who will change his life: the woman who will become his wife, the gnome man who will become his best friend, and the gnome woman with whom he’ll share a tragedy.
6000 words. (This story is available for free to subscribers to my mailing list.)

Not Like Us: A beasthead clan leader contends with the botched Human Purity invasion of her village (as mentioned in Realmgolds), and must decide how much she wants to resemble the invaders. (Originally appeared in Theme-Thology: Invasion.)

Brothers: When a highly literate Asterist scholar meets a smelly Earthist shaman, things don’t go the way anyone expects. (Scheduled to appear in Theme-Thology: New Myths.)

Weave: (Non-Gryphon Clerks.) All of a sudden, everyone in the world is connected in strange and frightening ways. (In progress; for submission to Theme-Thology: Real World Unreal.)

Intrusion: The story of the dwarven hack of the farspeakers in Hope and the Clever Man, told from the dwarven side. (In progress; for submission to Theme-Thology: Mad Science.)

Names: (Non-Gryphon Clerks.) In an afterlife in which everyone is a collective being, made up of everyone who’s ever lived who has the same name, a person with a unique name has an advantage. But what advantage? (Currently on submission to a well-known genre magazine.)

Fixer: The man called Fixer knows everyone, and helps connect people with needs to those who can meet them. What happens when a confidence man wants to exploit Fixer’s network? (In progress.)

You’ll note that’s only nine. I’m sure another will come to me in due time. (It might be that noir dwarf detective story in the style of Damon Runyon that I started once, in frustration at the story of a noir dwarf detective that was so clod-hopping and ponderous that I just couldn’t stand it. Or not.)

Earliest publication date is probably around June for this one, assuming I sell “Names” to the magazine I’m targeting. They gave me a very positive personalised rejection for another story which was all about why that particular story didn’t quite work for them, despite its many good qualities, so I’m having another go. Their exclusive period is two months from date of publication.

More bulletins as events warrant.

Feb 24

Short Stories, and an Announcement

I’ve put three short stories up on Amazon as a collection for 99c. I plan to publish more short stories this year – potentially, I’ll add them to this same collection, and get Amazon to alert purchasers to an “update” so that people who’ve already bought them get more stories at no extra charge. (Edited to say: There’s at least a possibility that the small press HDWP Books will bring out an anthology collecting the stories I’ve done for their Theme-Thology volumes as well as some other short stories of mine later this year, so I’ve pulled the mini-collection. Further details in this follow-up post.)

The three stories are:

Good Neighbours: An elderly woman must answer the classic question: Who is my neighbour? (Formerly appeared in New Realm magazine in December 2013.)
2700 words.

Vegetation: In an old Elvish city, plants are everywhere. And goodness knows, someone has to look after them. A lighthearted, Wodehousian piece.
2300 words.

Gnome Day: An idealistic young clerk helps out on the night the gnomes are freed, and meets three people who will change his life.
6000 words. (This story is available for free to subscribers to my mailing list.)

Speaking of writing, I’ve been accepted as a contributor to the popular Fantasy Faction fansite. I’ll be sharing some of my reviews there, and I also hope to publish some blog posts. These will be posts that I would previously have put up here with the category “Manifesto-esque Rantings” or “Craft”. Instead of publishing those posts here, I’ll focus more on making this a site for my readers, not so much for fellow writers. I’ll share any Fantasy Faction posts as they’re published, via my Google+ profile. I may also make a page on here as a directory to them.

Fantasy Faction gets about 2000 visitors a day and has already won a couple of minor awards, so I’m pleased to be writing for them. Since what I write for them will be reviews and posts I was going to write anyway, I promise it won’t slow down the production of Gryphon Clerks fiction.

 

Jan 21

Short Story Challenge begins

Something new today. I’ve decided to do a Short Story Challenge this year, which works as follows:

  1. I read and analyse a classic short story each month.
  2. I take what I learned and write a short story of my own.
  3. I submit it to magazines and anthologies until it sells, or until I run out of markets.
  4. Once the rights revert, I publish it on Amazon, either alone or as part of a collection, and/or make it one of the membership bonuses for my mailing list.

Several people I know on Google+ are joining me (some of them are doing slightly different versions), and you can follow along with the hashtag #shortstorychallenge.

I’m working, at least initially, from the Oxford Book of Fantasy Stories, selected by Tom Shippey. It’s a collection I own, I’ve read it before, and I know it has a lot of good stories in it, drawn from just over a century of fantasy literature (1888-1992).

I’m not planning to analyse every story in it, because I know I wouldn’t follow through on that. Besides, I only need a dozen, and I want to throw some SF stories in later on as well (probably from the companion Oxford Book of Science Fiction Stories, also selected by Shippey, and which I also own). I may look at a detective story or two – my wife has about 30 mystery anthologies, including a couple of Oxford ones that she says are good – and possibly some mainstream short fiction, of which I also have a couple of collections. It’s generally good to read outside your genre. It can freshen things up.

Here’s my first analysis, then. It happens to be of a story that’s freely available on the web: Lord Dunsany’s “The Fortress Unvanquishable, Save for Sacnoth“. I’ll analyse it under a number of headings, which I’m making up as I go along, and italicise the things I take as lessons. Future analyses may differ in approach. In fact, that’s highly likely.

Subgenre: Somewhere between Sword and Sorcery and Weird Tales. The events are S&S, the tone is Weird, and the combination works well. Crossing a couple of subgenres can have the effect of adding their strengths together.

Type of story: The plot has a strong Adventure core, but it’s not just an adventure. It’s also a Creepy Mood/Bizarre Experience story, like the ones that Lovecraft and co. wrote (going back at least to Poe). It has a Switch-up at the end, when the narrator questions whether it’s an Hallucination or even a complete False Legend. This kind of category questioning is part of the Weird Tales genre, I think, and contributes to the genre’s sense of confusion and fear.

Why the story works: It works more because of the atmosphere, the language and the tone than because of the plot, which is straightforward, with a minimal amount of tension in it (see analysis below). The adventure part would have made a decent story, perhaps a bit disappointing because the protagonist wins too easily. Those additional aspects make a great one. If you sizzle loud enough, you may not need as much sausage.

Language Elements: The names are the first thing to notice. The story itself is named after the fortress in it: The Fortress Unvanquishable, Save for Sacnoth. Even its door has a wonderful name: The Porte Resonant, the Way of Egress for War. Then there are the names of the other places, people, and enemies: the town of Allathurion, its lord Lorendiac, and his son Leothric (the first two sound more-or-less Norman French, the third Saxon, and all of them Arthurian); the dragons Tharagavverug, Thok, Lunk, and Wong Bongerok, whose resonant, clanking names reflect their metallic nature; the evil magician Gaznak, who sounds like a Tolkien orc;  The Land Where No Man Goeth. Take the opportunity that names provide to evoke atmosphere.

Then there are the descriptions. “Then Leothric advanced towards a door, and it was mightier than the marble quarry, Sacremona, from which of old men cut enormous slabs to build the Abbey of the Holy Tears. Day after day they wrenched out the very ribs of the hill until the Abbey was builded, and it was more beautiful than anything in stone. Then the priests blessed Sacremona, and it had rest, and no more stone was ever taken from it to build the houses of men. And the hill stood looking southwards lonely in the sunlight, defaced by that mighty scar. So vast was the door of steel.” That kind of description is hard to pull off, comparing something mythical to something else mythical that you have to explain, but if you can do it, you can convey a sense of a world that extends beyond the edge of this story; that’s being shot on location, not in a sound stage. Give the audience something that only appears in the corner of their eye to make the world more real.

A number of the descriptions of the evil things mention Satan. This not only gives a context (Christianity) but also ties them together through the repetition.

Dragon
wili_hybrid / Foter.com / CC BY-NC

The whole story uses an “elevated” and pseudo-antique style, the kind of style William Morris pioneered (following Spenser’s Faerie Queene): “unvanquishable” rather than “unconquerable” or even “impregnable”; “save for” rather than “except for”. This is incredibly hard to pull off (judging from the number of people who fail at it). You need a very large vocabulary and a good ear. All too many writers who attempt it have a much smaller vocabulary than they think they do, so they use the wrong word and make themselves look like idiots, and are prone to dropping modern colloquialisms into the middle of the high-flown prose at intervals and completely spoiling the effect. Dunsany has the linguistic chops to make it work. He knew what he was doing, and he could probably have explained it if he had to. Unless you can explain how and why this works, don’t try it.

Plot: Let’s attempt to apply the Seven-Point Story Structure and see where we get to.

Hook: The village by the dark forest full of fae is peaceful (paragraph 1). A little… too peaceful, if you know what I mean. Already, we’re waiting for the other shoe to drop. Hint at trouble as early as you can.

Plot Turn 1: The village becomes troubled by evil dreams (paragraph 2). There we go. Don’t hold off too long on the plot turn.

Pinch 1: The magician can’t defeat them with his best spell. (There’s actually a brief try-fail cycle here, by a minor character, the magician, who doesn’t reappear later, and the protagonist isn’t even introduced until it’s over.) The protagonist doesn’t have to do everything.

This sequence also does a lot to establish both the tone and the world: there is magic, there’s a culture that crosses various kinds of landscape containing camels, elephants and whales, even a village magician commands great power. Make the minor details work to establish world and tone.

Midpoint: Leothric steps up and volunteers to go and defeat the dragon-crocodile Tharagavverug in order to get the sword Sacnoth, so that he can defeat the sender of evil dreams. We have a sub-quest. Arguably, the whole sub-quest, in which he must demonstrate tenacity and courage and therefore his worthiness for the main quest, is part of the midpoint. The points can be extended sequences, not just moments; the midpoint is a demonstration of fitness to be the hero, not just a decision.

Pinch 2: Leothric fights his way into the Fortress Unvanquishable, Save for Sacnoth. This is a kind of try-fail cycle, the kind that looks like success. He keeps achieving tasks (break down the door; scare off the camel-riders; get past the spider; pass through the hall of princes and queens; resist the temptation of the dream-women; cross the abyss; fight the dragon; fight the other, more dangerous dragon), but none of them are the task he wants to achieve: fighting and defeating Gaznak. In his talks on the Seven Points, Dan Wells alludes to the example of The Princess Bride, where the Man in Black’s contests with Inigo, Fezzik and the Sicilian, and the encounters in the Fire Swamp, are “try-fail” cycles. He wins, he progresses, but he doesn’t yet achieve his ultimate objective: to escape to his ship with Buttercup. Try-fail cycles can involve the protagonist winning.

Leothric doesn’t have any serious trouble with any of these obstacles, yet the story remains interesting, because they’re so beautifully described and everything is so evocative. This is similar to Dunsany’s models, the Arthurian quests (Gawain and the Green Knight, for example, which also gets echoed later with the detachable head). Success against opposition, even easy success, doesn’t have to be boring, as long as the opposition is interesting and the success isn’t instantaneous.

Plot turn 2: Leothric finally confronts Gaznak, and just when it looks like he will lose (because Gaznak’s sword can destroy Leothric’s armour, but not vice versa, and Gaznak’s detachable head trick prevents Leothric from beheading him), he figures out that Gaznak has another point of vulnerability: his wrist. This has been set up in advance, so it doesn’t feel like it comes out of nowhere, and in exploiting it he adds intelligence to his already-demonstrated virtues of courage and tenacity. Set up the solution, even if only half a dozen paragraphs before. Have the hero snatch victory from the jaws of defeat. It’s never too late to have the hero show another quality that’s consistent with his character.

Resolution: The evil dissipates, Leothric returns home and the village is again at peace. Return to status quo ante is an acceptable resolution; the hero has changed, but the world may be back to how it was. 

After the resolution comes the little twisty doubty thing in the last four paragraphs. If anything, this makes the story more of a legend, claims for it the status of a traditional tale rather than a newly-made-up story, as well as raising the epistemological question of what is true, what is real, and how we know. Those are questions academics ask more often than ordinary people, and perhaps they were preoccupations of earlier generations more than our own. It’s not necessarily something to imitate, but I think it works for this story.

So there’s my analysis. Now I need to write my story. I have a story in progress, but I’m not sure that the lessons I’ve learned here are directly applicable to it, so I may need to start another.