It’s All in Your Head

Or too much of it is, anyway.  When it comes to stating — or not stating — the obvious, it’s possible to be too subtle for your own good.

I’m talking here about the kind of excessive subtlety that leads to what are sometimes called “head stories” — which is to say, the particular kind of flawed story you get when there are elements of it that are so obvious to the writer that they aren’t mentioned in the text.  They never make it out of the writer’s head; hence the name.

But readers can only read texts, not minds.  If you don’t put that material down on the page — or don’t at least put down enough of it that they can reasonably infer the rest — then they won’t ever know that it’s there.

If you’ve got something crucial to your story that you want the reader to work out by inference from the clues supplied, then you need to, first, make certain that you have in fact supplied enough clues for the reader to draw the desired inference; and second, make certain that you give the reader confirmation at some point that he or she has interpreted the matter correctly.  (This confirmation is one of the strings that can be usefully tied up in the story’s denouement.)

How many hints or clues are enough?  As always with writing, it depends — but three is a nice round number.  Western-influenced people tend to regard three as significant and memorable; we show it in sayings like “Third time’s the charm” or “Once is happenstance; twice is coincidence; three times is enemy action.”  If something is called to our attention three times, we’re going to assume that the writer had a reason for waving it in our faces like that.  Also — when supplying the clues, remember that you have privileged knowledge that the reader does not; therefore, what is screamingly obvious to you may not be so to anybody else.

As a general rule, the answer to the question, “Am I being too obvious here?” is usually, “No.”  If you are being too obvious, your first reader or your editor will probably tell you.

Thought for the Day

The shape of a good story in usually implied in all of its parts, including the beginning.

It’s always a good sign when the reader is able to guess at that ultimate shape from reading the first two or three chapters, rather like a paleontologist inferring the shape of a T-Rex from a couple of bones.  Conversely, if the animal as ultimately reconstructed turns out to be wildly different from the one suggested by that first handful of bones, an acute observer may well conclude that something went wrong — either in the final assembly, or in the selection of parts.

Most readers are more acute observers than you might think.  And writing a story whose front end promises something that the rest of the story doesn’t deliver is a prime route to reader disgruntlement.

The Return of Pie

We had apple pie for dessert tonight.  My husband and co-author is the household’s designated piemaker, and he does a mean apple pie.  One of his secrets: using two or more different types of apple.  Tonight’s pie featured a couple of Granny Smiths, a Macintosh, and two large Rome apples.  Why more than one type of apple?  Because it give a depth and complexity of flavor that you just don’t get in pies made with a single variety of apple.

And this is related to writing, how?

Just as a pie is better when it’s made with more than one variety of apple, a novel is better when it doesn’t just have a single mood or tone.  Horror is made more frightening by being lightened from time to time with humor; adventure and mystery can often benefit from a dollop of romance.  The contrast works to add depth, and the relief of tension lures readers into a momentary security.  And it’s the momentary security that makes them jump even higher when the surprise twist comes around.

Stet

Stet is Latin for “let it stand.”  It’s also a word of power for dealing with copyeditors who have — in the author’s opinion — overstepped the limits of their job.

A good copyeditor is the author’s friend.  He or she will do things like keeping track of a whole extended family of fictional characters across a multi-volume series, with accompanying fictional place-names and scraps of invented language, so that even if the author fails to do the math and accidentally keeps the same minor character twenty-five years old for almost a decade, the mistake will be fixed before the book hits print.   Characters who enter a scene wearing a t-shirt and jeans will not leave it wearing khaki cargo pants and a flannel button-down, unless they’ve been witnessed changing clothes in the interim.  The setting sun will not shine in through what can only be an eastward-facing window (if the author has supplied enough detail for a reader to infer the layout of the manor house, a good copyeditor will keep that layout in mind.)

In short, a good copyeditor will make you look smarter than you really are, and will ensure that your book is as good as it deserves to be.  If you get a particularly good or face-saving copyedit, it’s a kindness to tell your editor to pass along your thanks to the copyeditor — rather like sending your compliments to the chef — and to mention that if they’re free the next time you have a book come up on the schedule, you’d love to work with them again.

Bad copyedits . . . let’s just say that it’s almost impossible to be a professional writer and not fall victim to at least one staggeringly awful copyedit.    Authors gather in bars and tell copyeditor horror stories.  (To be fair, the group at the other end of the bar is a gang of copyeditors, telling author horror stories.  If no man is a hero to his valet, no author is a hero to his copyeditor.)  At times like these, it helps to keep in mind that the book is, in the end, your book, and to remember the magic word.

Stet.

Mirror, Mirror

One of the hardest things to do with first-person narration (apart from the problem of how to tell the reader about important things that happen where the POV character can’t see them) is describing the narrator’s appearance. With third person, it’s relatively easy — you can slip in a detail here and a detail there as the opportunity arises, or you can say the heck with subtlety and provide a couple of descriptive sentences about the character shortly after he or she is introduced.  But with first person, you’re not just following the character around and eavesdropping on their thoughts when it’s convenient.  You’re inside their head all the time . . . and most people, unless they’re either really vain or really insecure, don’t spend that much time thinking about the fact that they have, say, brown hair and hazel eyes and a nose that’s just slightly crooked because they broke it falling off a seesaw back in second grade.

So what can you do?

Well, you can always not bother with physical description of your first person narrator.  It’s surprising, really, how irrelevant brown hair and hazel eyes are to a lot of story lines.  (For the story lines where they are relevant, the narrator will tell you about them — in fact, if he or she thinks that the crooked nose and the unexceptional hair and eye color are why they are still tragically without a date for the senior prom, they  are probably not going to shut up about it.)

But what you don’t do (and don’t do it with third person narrators, either) is have your first-person narrator look at themselves in a mirror and describe what they’re seeing.  And for “mirror” read also lake, pond, mud puddle, silver bowl, shop window, the eyes of the beloved, or any other reflective surface.  Because that has been done.

A Plaintive Query

Doesn’t anybody know how to use the past perfect any more?

(I’m reading slush these days, along with everything else.  All aspiring writers should do some slush reading if they get the chance.  It’s an enlightening experience, and far more entertaining than, say, grading freshman essays, which I’ve also done in my time.  Even the worst slush in the world was written by somebody who actively wanted to be putting words on paper, or pixels on screen; even the very best freshman essays, on the other hand, have a certain forced, gun-to-the-temple quality about them.  Also, when you’re reading slush, once you get to the point where you’re convinced that a piece is hopeless, you can stop.  With freshman essays, there’s no such release.)

Another Thing Not to Do

If you’ve got a character speaking a line of dialogue and also performing an action, don’t get into the habit of always putting the action into a participial phrase  tacked on after the dialogue tag:

“This is an important announcement,” she said, taking her place at the podium and opening her notebook.

No.  It needs to be either:

“This is an important announcement.”  She took her place at the podium and opened her notebook.

or

She took her place at the podium and opened her notebook.  “This is an important announcement.”

Save the participial phrases for occasions when the dialogue and the action are truly simultaneous:

“Listen up, people!” she snapped, slamming the notebook down on the podium.

or when the action’s mostly a bit of stage business, there for characterization or setting-establishment or pacing:

“Listen up, people,” she said, shooing away a moth that was trying to fly into the Coleman lantern.

(Who gets to decide what’s important and what’s stage-dressing?  You do.  It’s your story.  Just remember to keep on listening to what it’s telling you.  And remember, audiences like variation.)

Leftovers

We roasted a leg of lamb for Easter dinner.  It would have been a half-leg of lamb — which is more in line with the number of people in the house these days — but the grocery store didn’t have any half-legs left by the time we did our shopping, so a whole leg of lamb it was.  We stabbed it with a knife and put in slivers of garlic, then laid rosemary sprigs on top of it and cooked it at 325F for 25 minutes per pound, and served it up with mint sauce and roasted potatoes and asparagus in hollandaise.

The potatoes and the asparagus are gone, along with the hollandaise, but we’ve still got half the lamb in the refrigerator, and now I’m thinking about leftovers.  Lamb sandwiches, probably, and maybe a shepherd’s pie.

It isn’t just cooking that has me thinking about leftovers.  Writing jobs have leftovers, too — the paths the story tried to take that turned out to be dead ends; the bits of other as-yet-unwritten stories that cropped up in the current project by mistake; the occasional perfectly good, yes-it-really-happened scene that nevertheless had to be excised from the finished text because it slowed things down at a point when they needed to be moving fast, or because it threw unwanted emphasis on something that needed to be kept in the background, or because the book had a firm word count requirement and was already threatening to run long.

But the dead-end paths and the outcroppings of other narratives can often be reworked into fully realized stories in their own right.  In fact, their appearance in a story where they don’t fit can often mean that your subconscious muse is telling you something about what your next project ought to be.  As for those snippets that were removed in the service of the greater good — it used to be, there wasn’t much a writer could do with them except put the pages away in a desk drawer with a sigh of regret, but the internet has helped us with that as it has helped us with so many other things.   Those snippets can now be posted on a novel’s web page as extra treats for faithful readers, or turned into Kickstarter rewards, or compiled into a self-published chapbook and put up for sale by the author.

So don’t throw out those leftovers, any more than you’d throw out a perfectly good half-eaten leg of lamb.

Fillers and Placeholders

When you’re hard at work on the first draft and running for daylight, you can’t afford to lose your forward momentum.  The first draft isn’t the time and place to spend fifteen minutes looking for the perfect name for that minor character who steps onto the page long enough to deliver a crucial bit of plot development before vanishing.

For the first draft, it’s often enough to have [CharacterName] appear from [NameOfPlace] with the necessary plot element in hand.  Just remember to search on the square brackets during the second-draft revisions, when you’re putting in that perfect name you finally came up with when you were drifting off to sleep the night before.

What’s in a Name?

It’s a sad fact that short stories and novels have to have titles.  If they didn’t, then there’d be nothing to put on the spine of the book, or in the table of contents for the magazine or the anthology.

This means that the unfortunate writer, after having labored for weeks or months on something that may have lived quite happily with the designation “NewNovel.doc” or “short story in progress” or even “that thing in the green notebook”, now has to give his or her brainchild an actual name.  Cue angst, flailing, and general unhappiness.

Composers have it easy by comparison.  They call a project “Concerto Number 3 for Xylophone and Orchestra in B-flat Minor” and get away with it, where a writer who tried to run “Space Opera Volume Three with Blasters and Scaly Aliens” past an editor would only get laughed at.  (Oddly enough, though, the same writer could probably get away with using that title for a short story — there’s a lot more room for weirdness and wordplay in short story titles — but not more than once.)

Desperate writers do have a few resources they can turn to in their quest for a title.  Quotations from Shakespeare are always good; likewise, quotes from the Bible.  And if the Bible and Shakespeare don’t come through, there’s always Bartlett’s Familiar Quotations.  Pulling a relevant or evocative phrase from the book itself also sometimes works.

If all else fails . . . console yourself with the thought that most editors know that thinking up titles is not necessarily a part of the common writer’s toolkit.  If an editor likes your book or story, but thinks that the title sucks, he or she will tell you so.  And at that point, it’s perfectly okay to turn the job over to a professional ask the editor for suggestions.