I said YES. Wait, you want me to say no? Okay, then it’s no — and other less-than-stellar argumentative techniques of fictional characters.

I was thinking about you, dear readers, earlier today at an opera rehearsal — hey, I move in some pretty rarified circles. Specifically, I found myself musing about our recent discussions of plausibility in interview technique — as the singers belted their characters’ deepest and darkest toward the back wall of the auditorium. I must have been giggling under my breath, for in the middle of an aria, my SO leaned over to me and whispered, “They can’t have been reading your blog lately.”

Obviously, the composer hadn’t — not entirely surprising, as the music in question first hit the pop charts in the middle of the 17th century; I doubt its author blog-surfed much.

The moment I got home, I rushed straight to my computer and started rifling through my archives — a practice I highly encourage; there’s quite a bit of information stacked in the back room of this blog, you know — because I had a distinct recollection of having written on this very topic sometime last year.

As it turned out, I was right: my last spring’s opera intake included sitting through a classic bad interview scene. Take a listen:

The brave knight Ruggiero, ensnared by the love spells of the evil sorceress Alcina (who had a nasty habit of turning her exes into trees; opera gives one a lot of room for imaginative touches), has deserted both his fighting obligations and his warrior girlfriend, Bradamante. So another sorceress, Melissa, turns herself into an image of Ruggiero’s father, Atlante, to try to free him. Dressed as Atlante (and turning from an alto into a baritone for the occasion, a nifty trick), Melissa berates Ruggiero for lying around in sensual bliss when there’s work to be done.

A single three-minute solo later, Ruggiero’s mind is changed, with no argument from the big guy himself: he is free from the spell, and goes on to bellow some extraordinarily nasty insults at Alcina while Punchinello dances around with a squid.

You had to be there, I guess. It was quite entertaining; the squid was played by a hand puppet. It was also not very good storytelling — and even worse character development.

This type of persuasion in an interview scene — where the protagonist’s mind is changed on an issue about which he is supposedly passionate simply because someone TELLS him he’s wrong, without engaging in convincing argument — occurs in novel submissions more often than you might think. Many a protagonist who is downright tigerish in defense of his ideals elsewhere in the book is positively lamblike when confronted by a boss, a lover, a child, etc. who points out his flaws.

And that, unfortunately, makes the conflict seem much less important than if the characters argue the pros and cons at least a little. Usually, the result is a more compelling scene — and better character development for the arguers.

Oh, heck, I’ll go out on a limb here: it’s almost always better storytelling.

Why? Everybody chant it together now: because conflict is more interesting in a scene than agreement. Unending harmony, as delightful (and rare) as it may be in real life, can be a real snooze-fest on the page.

Even the injection of just a little good, old-fashioned passive-aggression can ginger up a scene no end.

Nor does being easily persuaded, non-confrontational, or generally — brace yourself — nice necessarily render a protagonist (or any other character) more likeable to the reader. No, not even if the reader happens to enjoy the company of such sterling souls in real life.

Why, you cry? Because endlessly making nice tends to kill dramatic tension dead, dead, dead.

That seems to come as a surprise to many aspiring writers, judging by the number of first novels and memoirs where the protagonist bends over backwards never to offend anyone — especially common in manuscripts where the protagonist happens to be female, I notice. Butter wouldn’t melt in some of these ladies’ mouths, as the saying goes.

Which pretty much inevitably results in either a relatively conflict-free plot or a passive protagonist who stands on the sidelines while the less scrupulous (and more interesting) characters act.

To give you some time to digest that particularly bitter little pill — don’t worry; I shall be returning to the problems of the passive protagonist next week — allow me to turn my opera example to another use: to show yet another way in which a screener might read an opening scene differently than another reader.

This object lesson should be a bit easier to swallow. Take this little test: quick, without re-scanning the paragraphs where I glossed over the opera’s plot, try to name as many of its characters as you can.

How did you do?

I originally mentioned six, but don’t be hard on yourself if you only came up with one or two. Most readers would have experienced some difficulty keeping all of those sketchily-defined characters straight.

Heck, seeing them introduced en masse like that, I would have trouble remembering who was who, and I’ve seen the opera!

Introducing too many characters too fast for any of them to make a strong impression upon the reader is EXTREMELY common in the opening few pages of novel submissions. Indeed, sometimes there are so many people lurching around that the reader does not know for several paragraphs, or even several pages, which one is the protagonist.

Why might confusion on this point be problematic? In a word: Millicent.

Agency screeners read fast; if they aren’t sure what’s going on and who the book is about by the middle of page 1 (which is, unfortunately, how they would tend to diagnose the paragraphs above), they generally stop reading.

To use Millie’s favorite word: next!

So strategically, you might want to limit the number of characters introduced within the first couple of pages of your submission. If you’re in doubt about how many is too many — no, Virginia, there is no hard-and-fast rule — there are a couple of tests I like to use.

The first, and the simplest, is a modification of the one I used above: hand the first page to a non-writer. (NOT a relative, lover, or someone with whom you interact on a daily basis, please; these folks’ desire to see you happy may well skew the results of the test.) Ask her to read through it as quickly as possible. As soon as she’s finished, reclaim the manuscript. Then take her out to coffee and ask her to tell you who the main character is and what the book is about.

Why did I specify a non-writer, you ask? Because writers tend to be unusually good at absorbing character names; the average reader is not. Thus, the latter is a better barometer for submission purposes, at least for this particular issue.

Seem counter-intuitive? Think about it: your garden-variety agency screener scans far too rapidly, and reads far too many submissions in a given day, to retain the name of any character who has not either been the subject of extensive description — which, as we’ve been seeing over the past few days, can be problematic in itself — or a mover or shaker in the plot.

Oh, look: the question of protagonist passivity has popped its winsome little head out of its gopher hole again. Can’t imagine how that happened.

I sense some discomfort out there, don’t I? “But Anne,” some intrepid submitters protest, “weren’t you telling us just the other day that professional readers resent having things over-explained? Assuming that they’re smart enough to follow a complex plot, wouldn’t they be able to remember any character I’ve named? After all, even if Millicent forgot who Nicodemus was by the bottom of page 5, she’d merely have to flip back to page 1 to remind herself.”

Oh, I’m glad you asked this question, intrepid submitters. If you take nothing else from today’s post, cling to what I’m about to say next with the tenacity of an unusually stubborn leech:

In preparing ANY manuscript for professional submission, make it your mission to assure that a screener NEVER has to flip back to remind herself who was who or what just happened.

The simple fact is that very few professional readers will take the time to do it. Our old pal Millicent has a lot on her mind, you know — like that too-hot latte that just burned her full pink lip. (You’d think, after how long I have been writing about her, that she would have learned by now to let it cool, wouldn’t you? But that’s an agency screener for you: time is of the essence.)

No, but seriously, folks, most aspiring writers make the mistake of assuming that their submissions will be read slowly, with meticulous care. But Millicent might have 50 submissions to screen between now and the end of the day — you do the math.

The other test for a reasonable character-to-page ratio — and perhaps a better one, as it is also useful to see how well your storytelling skills are coming across: hand the entire first scene to that non-writer and ask her to read it as quickly as possible, to reproduce Millicent’s likely rate of scanning. Then take away the pages and talk with her about something else entirely for ten minutes.

In minute eleven, ask her to tell you the story of that first scene with as much specificity as possible. Note which names she can and cannot remember — if she’s like 99% of skimmers, she will probably remember only the two primary ones.

After thanking her profusely, sit down with your list of passed-over names and the manuscript: do all of these folks really HAVE to make an appearance in the opening scene? Could some of them be consolidated into a single character, to reduce the barrage of names the reader will have to remember?

Or could any of them be there, but not mentioned until later in the book, where the protagonist encounters that character again? (A simple statement along the lines of, “Hey, Clarence, weren’t you one of the thugs who beat me to a pulp last month?” is usually sufficient for later identification, I find.)

Alternatively, are some of the characters mentioned here for purely photographic reasons? In other words, is their being there integral to the ACTION of the scene, or are the extraneous many named or described simply because they are in the area, and an outside observer glancing at the center of action would have seen them lurking?

In a screenplay, you would have to mention their presence, of course — but in a crowd scene in a novel, describing the mob as monolithic can have a greater impact. For instance, which sounds scarier to you, Mr. Big threatening Our Hero while surrounded by his henchmen, Mannie, Moe, and Ambrose — or surrounded by an undifferentiated wall of well-armed baddies?

Personally, I would rather take my chances with Ambrose and Co. than with the faceless line of thugs, wouldn’t you? My imagination can conjure a much scarier array of henchmen than the named three.

I know, I know: when you create a novel, you create the world in which your characters live. And that world is peopled. But in the interest of grabbing an agency screener’s often mercurial attention, would a smaller cast of characters, at least at the outset, render your book more compelling?

Sometimes, less is more. Or at any rate, fewer. Keep up the good work!

Like I said, yeah: more perils of lifting dialogue from real life

Are my eyes ever bloodshot today! With good reason, too: I’ve been reading up a storm for the past couple of days, in order to polish off some promised reviews. Everything I’ve been reading has been quite well written, thank goodness — although reading a bad review can sometimes be fun, writing one seldom is — but a certain type of repetition has been making me feel an unusually high level for Millicent.

What species of repetition am I complaining about now, you ask? Let me answer that with an appeal to you: as a reader, have you ever had one of those weeks where every piece of dialogue you scan seems to be a lightly-disguised monologue? Running, perhaps, a little something like this:

“I can’t believe how arrogant that car dealer was!” Sandy fumed. “You’d think he’d never met a woman who wanted to buy a car.”

“Yeah,” Jeff replied.

“I should have told him that I was going home to e-mail the National Organization of Women, to get them to issue a general boycott of his lot.” Angrily, she wrestled to undo the bungee cords that held the driver’s side door onto her 1978 Saab, provided that she never attempted to accelerate above thirty miles per hour. “Did you see how surprised he was that we left?”

“Um-hm.”

“You don’t suppose his telling me that women don’t know anything about cars is his standard sales technique, do you? Other women can’t actually have bought cars after a line like that.”

“No,” Jeff said, crawling into the passenger seat via the smashed back window. “I imagine not.”

Sandy dug under the visor to retrieve the seatbelt. “Well, I wouldn’t be so sure. It’s like those construction workers who yell disgusting things at women walking by their worksites: if it didn’t provoke a positive response at least once every 10,000 times, would they keep doing it? Or do you think that’s just blaming the victims?”

“Could be.”

“Anyway,” she concluded after she had successfully hot-wired the car, so she would not have to force the mangled key into the half-melted ignition, “I guess he won’t be offering five dollars on a trade-in again!”

“Absolutely,” Jeff said, clinging for dear life to what was left of the dashboard.

I ask you: what purpose is Jeff serving in this conversation, other than listener? And if he isn’t in the scene for any other reason, why doesn’t he just shut up and let Sandy blurt out her entire speech, instead of adding line after excisable line of entirely colorless dialogue?

Not to mention repetitious.

As you may have picked up from the subtle clues I’ve left lying around over the past week, dialogue has been on my mind for the past couple of days, because I recently enjoyed a long, gossipy conversation with a very old friend of mine with a very distinctive speech pattern: she says, “Like I said…” every other minute or so. In a long anecdote — to which she is quite addicted, as a world traveler with unusual tastes in traveling companions — she often uses this phrase ten or fifteen times.

Since we grew up together, you would think I would know where she had picked up this rare trope, but I don’t; it’s an adult acquisition. We have both wandered far from home, evidently. But still, you’d think I would have some inkling as to its origin: she and I were so closely allied in high school that at her wedding, her father spent 45 minutes grilling my boyfriend about his prospects and intentions toward me.

You might say that we come from a close-knit community.

Our hometown does in fact have a distinct speech pattern, a mixture of the lilt remaining when a small town in Switzerland (cow and wine country) picked up and became a small town in California (wine and cow country), certain Mexican-influenced words, a smattering of barrel-related French, and a linguistically inexplicable tendency to pronounce “mirror” as “meer.”

Being a farming community (the aforementioned wine), of course, certain agricultural tropes abound in season, such as, “How about this rain? Sure do need it,” “The grapes would have been in by now, 20 years ago” (untrue, incidentally), “Did you hear that bears have been at Farmer X’s grapes?” (true, incidentally; brown bears like expensive fruit), and “Damned drunken tourists have been at my vines again. They think every grape in sight is a free sample.”

But “like I said,” no.

Now, being a sharp-eyed writer with a strong sense of verisimilitude in dialogue, you may have noticed something about all of these phrases, real-life tropes that actual people say quite bloody often in my native neck of the woods. Chant it with me now: they would be DEADLY dull in written dialogue.

As would a character who constantly punctuated her personal stories with “like I said…” Or indeed, almost any of the small talk which acquaintances exchange when they bump into one another at the grocery store. Take this sterling piece of Americana, overheard in Sunshine Foods in my hometown not so long ago:

A: “See you got some sun today, Rosemary.”

B: “I was picking peaches. How did your dentist appointment go?”

A: (Laughs.) “The dentist won’t be buying his new boat on my dime. Was that the Mini girl who just dashed by?”

B: (Craning her head around the end of the aisle.) “Could be. She was supposed to be visiting her mother sometime soon. She’s not married yet, is she?”

A: (Shakes her head.) “Oh, hi, Annie. Visiting your mother?”

Me: (Seeking escape route.) “Yes. How’s your son? I haven’t seen him since high school.” (Murmurs to boyfriend, covered by Mrs. A’s lengthy description of the relative heights, ages, and weights of her grandchildren.) “Thank God.”

A: “And how’s your mother?”

Me: “Oh, fine, fine. I’d better be going. Nice to see you.”

B: “Give my regards to your mother.”

Me: (Wheeling cart away.) “I will. Remember me to Bobby.”

A: “Well?”

B: (Sighing.) “Still no wedding ring.”

Okay, what’s wrong with this scene as dialogue on the page, over and above its repetition? You can hardly fault this exchange for verisimilitude — it not only is a transcript of an actual conversation, but it sounds like one, literary traits that do not necessarily go hand-in-hand — but it’s missing something, right?

Any guesses, wild or otherwise?

Give yourself three gold stars if you yelled, “Well, it’s hardly character-revealing, is it? Who are these people as individuals, as opposed to representatives of a collective small-town mentality?”

See it now? This exchange might as well have been said by actors, rather than specific people with personal quirks. Granted, as is, it might tell you a little something about the spying capability of my home town’s feared and respected Little Old Lady Mafia, but it doesn’t tell you much about the speakers as human beings, or our relative positions within society.

And if there was a plot (other than to get me married off to someone with whom I might produce more little winemakers, a quest that is ongoing and perpetual), its intricacies are not particularly well revealed by this slice o’life.

Oh, how often writers forget that real-life dialogue generally does not reproduce well on the page! If I had a nickel for every time I’ve heard a writer say, “But s/he really said that!” or “But that’s what people really sound like!” I would buy my own Caribbean island and send the entire Little Old Lady Mafia on annual vacations there.

Do I see a raised hand or two out there? “But Anne,” I hear some of you protest, “haven’t we already talked about this, and recently? Just as real-life events often don’t translate well into fiction, neither does most dialogue. Am I missing a nuance here?”

Perhaps one: aspiring writers also tend to forget that real-life dialogue is SELDOM character-revealing — and thus reproducing it in a manuscript will often not convey as much about a character as we sometimes expect.

Take, for instance, the oh-so-common writerly habit of placing the speeches of an annoying co-worker, relative, ex-lover, nasty dental receptionist, etc. into fictional mouth of a minor novel character as a passive-aggressive form of revenge. (Come on, every writer’s at least thought about it.) To a professional reader, the very plausibility of this type dialogue often labels it as lifted from real life:

“Oh, wait a minute, Sarah.” Pausing in mid-gossip, Theresa picked up the overturned plastic cup before anyone else could step on it, placing it neatly on the dining hall checker’s desk.

Dina the checker glared at it as if it was covered in baboon’s spit. “Don’t you dare leave your trash on my desk. Do you think I have nothing to do but clean up your messes?”

“It was on the floor,” Theresa stammered awkwardly.

“Don’t you give me your excuses.” Dina grew large in her seat, like a bullfrog about to emit a great big ribbet. “You walk that right over to the trash can. Now, missie.”

“I thought you had dropped it.”

“Go!”

“I’ll save you a seat,” Sarah offered, embarrassed.

Inwardly seething and repenting of her Good Samaritanism, Theresa obediently gave up her place in the block-long lunch line in order to take the walk of shame to the garbage receptacles on the far end of the dining hall. How quickly a good mood could evaporate.

Tell me: what about this scene would tip off Millicent that this really happened, and that Dina is a character from the author’s past? And why would her being able to tell this be a liability? Why, in fact, would Millicent be surprised if Dina ever showed later in the book any side other than the touchy one displayed here — or, indeed, if she ever appeared again?

Actually, that was a trick set of questions, because the answer to each part is the same: because the narrative doesn’t provide enough motivation for the intensity of Dina’s response — and fairly clearly, the writer doesn’t think that any such explanation is necessary. That’s usually an indication that the writer has a fully-formed mental image (negative, in this case) of the villain in question.

In other words, this is a rather subtle manifestation of the telling, rather than showing phenomenon: because the writer experienced this exchange as nasty because Dina was nasty, she has assumed that the reader will perceive it that way as well.

But without more character development for Dina — or indeed, some indication of whether this kind of insistence was typical for her — the reader isn’t really getting enough information to draw that conclusion…or any other. It’s just an anecdote.

Without reader feedback, the writer almost certainly wouldn’t notice this narrative lack — any guesses why?

If you said it was due to the fact that his memory of Dina the real person is so strong, run out and get yourself a chocolate sundae with jimmies on top. In his mind, her character is so well established that he can just write about her, rather than helping the reader get to know her.

The other tip-off that this was a real exchange, in case you were wondering, is that Theresa is presented as a completely innocent victim of an unprovoked attack. The pure villain vs. completely blameless protagonist is a dead giveaway that dear self is concerned.

And yes, I WAS darned annoyed when Dina — in real life, a very nice woman named Ellen who happened to be having a spectacularly bad day — misinterpreted my act of good citizenship. But if I crave well-deserved vindication from the total strangers who might conceivably read this story, I’m going to have to do quite a bit more character development.

Not to mention integrating the incident into the storyline well enough that it’s actually interesting to read.

Of course, we want to be true-to-life in our dialogue: as Virginia Woolf wrote, “fiction must stick to the facts, and the truer the facts, the better the fiction.” But let’s not forget that in order to maintain a reader’s interest, a book has to have entertainment value, too — and that however amusing a verbal tic might be in person, repetition is often annoying in a book.

This is especially true when a character is tired, angry, or in pain, I notice: all of a sudden, the dialogue sounds as though all of the characters are trapped in one of those interminable Samuel Beckett plays where the people are doomed to move immense piles of sand from one end of the stage to the other with teaspoons. See if this dialogue sounds familiar, theatre-goers:

A: “Oh. You’re home.”

B: (nursing the thumb the elephant trod upon in the last scene) “Yeah.”

A: “Have a nice day?”

B: “Um-hm.”

A: “I was cleaning out the attic today, and I came across that picnic blanket we used when we went out to Goat’s Rock Beach to scatter Father’s ashes. How it rained that day, and then the sun broke out as if Father and God had joined forces to drag the clouds aside to smile upon our picnic.”

B: “Yeah.”

A: “Ham sound good for dinner?”

B: “Yeah.”

As a general rule of thumb, I like to flag any piece of dialogue that contains more than one use of yeah, really, yes, no, uh-huh, um, or a linguistic trope such as our old pal “like I said…” Almost invariably, these are an indication that the dialogue could either be tightened considerably or needs to be pepped up.

“Like I said…” would be a particularly easy edit, because it would be a pretty sure indicator that the speaker is repeating herself (although interestingly enough, my old friend habitually uses this phrase when she ISN’T repeating herself, I notice). Yes, people do repeat themselves all the time in spoken English. Is it boring on the page? You bet.

Similarly, anyway and however in dialogue are pretty reliable flares, indicating that the speaker has gotten off-topic and is trying to regain his point — thus warning the manuscript reviser that perhaps this dialogue could be tightened so that it stays ON point.

My fictional characters tend to be chatty (dialogue is action, right?), and I was once taken to task for it by a fairly well-known writer of short stories. She had just managed to crank out her first novella — 48 pages typeset, so possibly 70 in standard manuscript format — so perhaps unsurprisingly, she found my style a trifle generous with words.

“Only show the dialogue that is absolutely necessary,” she advised me, “and is character-revealing.”

Now, since the dialogue in her published works has seldom, if ever, strayed beyond three lines, regardless of situation or character, I was not particularly inclined to heed this advice — have you noticed how often it’s true that established writers with little or no teaching background spout aphorisms that all boil down to “Write as I do”? — but I have to say, it has been useful in editing, both for others’ work and my own.

I can even derive an axiom of my own from it: if a person said it in real life, think twice before including it. Because, like I said, if it isn’t either interesting or character-revealing, does it really need to be there?

Keep up the good work!

L’amour, l’amour…wait, did I just doze off amid all that harmony?

\"If you call me darling ONE more time, I\'ll turn you into lover tartare.\"

For the last week or so, I have been yammering on about the dangers of including too much physical description of your characters and/or backstory in your interview scenes, particularly in ones near the opening of the book. (If you have not given a physical description of your protagonist or some insight into her primary relationships by page 182, the manuscript has a different problem.) Within this context, I asserted — perhaps rashly — that conversation where Person A describes Person B’s physical attributes TO Person B are relatively rare.

It hit me in the wee hours, however, that I had neglected to mention the primary real-life situation where speakers ROUTINELY engage in this sort of banter: people in the first throes of being in love. Especially if one or both are in love for the first time, their vocal cords are likely to emit some otherwise pretty unlikely dialogue. As in:

“Wow, your eyes are SO blue, Snuggums!” (Giggle.)

“Your nose is adorable, Muffin. I love that little freckle right there especially.” (Smack.)

“Who’s a little snuggle bunny? Is it you? Is it?”

Or the ever-popular:

“Do you love me?”

“Of course I love you. Do YOU love ME?”

“How can you even doubt it? I love you twice as much every time I blink. You can’t possibly love me even half as much as I love you.”

“That can’t be true, because I already love you five times more than anyone has ever loved anyone else.”

“Oh, darling, what a wonderful thing to say. I love you so much.”

“And you know what? I love you.”

Zzzz…oh, pardon me; I must have been indulging in a well-deserved nap until something actually happened during this love scene.

Do I sound cynical? Actually, I have nothing against love, in principle — truly, I don’t. It has produced some fairly spectacular poetry, and most of the human race.

But allow me to suggest that this particular species of conversation, even when spoken live, is properly only interesting to Snuggums and Muffin themselves.

Why? Well, it’s just a TAD conceptually repetitious, is it not? Not to mention the fact that entirely self-referential dialogue becomes intensely boring to any third-party listener with a rapidity that makes the average roller coaster ride seem languid by comparison.

Don’t believe me? Tag along on a date with two people (or heck, three or four) deep in the grip of the early stages of infatuation with each other and count the seconds until the quotidian problems of which way to hang the toilet paper roll and not being able to sleep for more than five consecutive minutes before being awakened by a snore that would put Godzilla to shame have reared their ugly heads.

And I would bet as much as a nickel that the rest of the conversation won’t be significantly more scintillating.

It can be equally deadly on the page — but naturally, as writers, when we write about the enamored, we want to capture that breathless feeling of discovery inherent in infatuation.

Nothing wrong with that, if it’s done well. Yet in print, rhapsodies on eyes of blue all too often produce prose of purple:

“Tiffany, your eyes are the most astonishing color, blue like Lake Tahoe on a cloudless day. Not a cloudless day in midwinter, mind you, when you might drive by the lake on your way to a ski slope, but the blue of midsummer, of long, dreamy days on Grandfather’s boat. Or still later, when you and I were in junior high school, and our parents shipped us off to that Episcopalian summer camp — the one that used the 1929 prayer book, not the modern edition — when we swam beneath skies of azure…”

True, someone MIGHT conceivably say something like this in real life, but let’s not kid ourselves here: you’d have to be Charles Boyer to pull off a speech like this without prompting gales of laughter in Tiffany and bystander alike.

Generally speaking, extensive physical descriptions like this work far, far better in narration than as dialogue. Most people already have some fair idea what they look like: while it’s always nice to be told that one is pretty (anyone? anyone?), one seldom needs to be told that one is 5’6″, even if that is indeed the case.

In fact, mentioning the latter fact in real life might actually engender some resentment. Height and weight are the two self-descriptors about which the average person is most likely to — well, let’s be generous and not call it lying; how about equivocating?

I find this kind of misrepresentation fascinating, as it so seldom fools anyone. Most people would never dream of perjuring themselves about their eye color on a driver’s license application— but don’t most people subtract a few pounds, or perhaps 30 or 40, on general principle, on the same form?

While we’re on the subject of doubting self-serving statements, aren’t personal ads living proof that many people are, at best, rather optimistic about their height? Don’t we all get at least a vague sense that the average movie star’s date of birth is somewhat variable, when she admitted to being five years older than we are when her first movie came out, and yet asserts that she is three years younger now?

Can’t we all live with that? I mean, River Phoenix’s four years at nineteen were good years for all of us, weren’t they?

Ethically, I don’t have much of a problem with these harmless little pieces of self-aggrandizement; for the most part, they’re victimless crimes. (“That’s he, officer — he says he’s six feet tall, but he’s 5’9″ in his stocking feet!”) In fact, being aware of this tendency can add a certain piquancy to an interview scene.

Love scenes in particular. I hate to seem cynical, but is it entirely beyond the bounds of probability the Boyer-wannabe above might have slightly exaggerated the blueness of Tiffany’s eyes for romantic effect?

In other words, what if instead of depicting your infatuated lovers commenting upon the REAL physical attributes of one another, the dialogue made it plain that a certain amount of hyperbole was going on? Or if one professed blindness to a physical defect in the other?

Such a scene might not provide just-the-facts-ma’am physical descriptions of the characters, but it might conceivably be more character-revealing — and more interesting to the reader — than the transcripts of either sweet nothings or undiluted praise.

If a writer REALLY wanted to get tricky, the narrative might not even make it clear in the moment precisely how and why Lover A is choosing to lie to Lover B. Conveying a subtle sense that there’s something more going on in this scene than meets the enamored eye is a great to increase tension.

Provided, of course, that the narrative doesn’t immediately stab the rising conflict in the heart by explaining in minute detail precisely what’s going on. This has been the death blow to many a promising love scene.

What do I mean by this, you ask? Let’s take a look at a scene where mixed motives have been handled with restraint.

Angelica backed off slightly, instinctively when Desmond kissed her, but lips pressed to hers, he failed to notice. Or if he did, any qualms he may have had were soon quelled by her enthusiastic embraces.

After a few minutes’ slurping passion, she loosed her lips enough to ask, “When do you need to be back at the White House, darling?”

He toyed with the come-hither straps of her meter maid uniform. “Not until half-past one. And even if I’m late, the republic won’t fall if the President gets his security briefing is a few minutes behind schedule.”

Angelica sighed, pulling him closer. “Promise me that I’ll always be more important to you than national security.” She glanced over his shoulder at the alarm clock. “Right now, I feel as though we’re the only two human beings left on earth.”

“Oh, sweetheart,” he murmured into her shapely neck.

Gives a pretty strong impression that Angelica’s motives in pursuing the tryst might not be identical to his, doesn’t it? The slight tension between her actions and her words convey that easily, without a lot of heavy-handed justification or acres of internal monologue.

Which, alas, is how many manuscript submissions would have approached it. Here’s a sample — note all of the named emotions, explanations through thought, and just how quickly the reader’s ability to speculate about what might be going on evaporates:

Oh, God, Angelica thought, stunned by the onslaught of Desmond’s cologne, not again. Didn’t this lummox ever think of anything but sex, sex, sex? Still, she had been ordered to keep him here until after the President had been assassinated, and if a little nookie was the most pleasant way to achieve that, well, so be it.

She hoped that it would not take very long; her husband, Ivan, would be expecting her home soon.. “When do you need to be back at the White House, darling?”

“Not until half-past one,” Desmond panted. “And even if I’m late, the republic won’t fall if the President gets his security briefing is a few minutes behind schedule. It’s not as though anyone out there is planning to perch atop the Washington Monument during his speech on the Mall and shoot him with a crossbow in front of 210,000 people!”

Angelica stiffened with fear. How on earth had he ferreted out the details of their plan? Had she been betrayed by a careless or treacherous fellow spy? Was Desmond merely toying with her, in order to extract further information?

She pulled him close. “Promise me that I’ll always be more important to you than national security,” she whispered, shuddering inwardly at the irony of her own words. She glanced over his shoulder at the alarm clock; if only she could keep him here until after Reginald had charged the herd of maddened elephants into the assembled throng, all might still be well. “Right now, I feel as though we’re the only two human beings left on earth.”

“Oh, sweetheart,” he murmured into her shapely neck.

Kind of stops the tension dead in its tracks, doesn’t it? See how the suspense builds naturally when the narrative merely hints at the underlying plot, rather than screams it from the rooftops?

The same technique also works beautifully in anti-love scenes, by the way: if you want to ramp up the tension, try both muddying the players’ motivations a little and conveying those mixed emotions through action, rather than having them say precisely what they mean at all times.

Yes, yes, I know: your tenth-grade composition teacher told you that good dialogue should be able to convey all of the emotional nuances of a scene without additional narration. Let me guess — s/he came up with that pearl of wisdom while either trying get you to read Hemingway or to stop relying so heavily upon adverbs to express a character’s feelings, right?

I tend to doubt that s/he intended it as a lifetime embargo upon certain parts of speech. Adults don’t let ten-year-olds drive Mac trucks, either; one needs to be trained to use dangerous tools safely before running amok with them. In case you’re curious, The kind writing s/he was trying to avoid with her prohibition probably ran a little something like this:

“I can’t pay the rent!” Polly exclaimed distressedly.

“But you must pay the rent,” dastardly Donald declaimed determinedly.

“But I can’t pay the rent!” she wailed helplessly.

“But you must pay the rent,” Donald insisted violently.

“But I can’t pay the rent!” she sobbed unhappily.

“I’ll pay the rent!” nattily-dressed Nathan called helpfully.

“My hero!” Polly cried relievedly.

“Curses,” Donald said morosely, “foiled again.”

I seriously doubt that s/he was hoping you would never use another adverb as long as you lived, just that you would use them with discretion.

But as with so many of the old writing saws, the creaky old chestnut has mutated over time in the conversation of the literal-minded from don’t use adverbs to describe how every speech was said; how about letting the dialogue itself show tone? to it’s bad writing to use an adverb ever, under any circumstances. Purge your manuscript NOW of all -ly verbs, or you’ll tumble into a pit of burning pitch.

Just a SLIGHT different between those two iterations of that rule of thumb.

I know I’m going out on an editorial limb here, but I suspect you’ve progressed enough as a writer to be trusted not to over-use adverbs, don’t you? There, I absolve you: from now on, you’re allowed to use all available parts of speech, if you do it with discretion. Fly on your merry way, allowing your shackles to fall to the ground.

Just don’t start using adverbs to describe how every character says every speech, okay? Oh, and while you’re at it, you don’t need to add a tag line (he said, she avered, they bellowed) to every line with quotation marks. Use them sparingly, just enough to keep the reader abreast of who is speaking when.

Which means, in case your tenth-grade composition teacher forgot to mention it to you, that in a two-person exchange where the opinions expressed are not identical, simply alternating speeches after the text identifies who is saying what initially is usually sufficient.

If you feel ready to implement a more advanced writing technique, try varying the tone a little throughout confrontation scenes; watching two characters spit vitriol at each other unceasingly can get a little old rather fast. For instance:

“I hate you, Ted Fairfax, more than any human being I’ve ever known in my life.”

“Yeah? Well, I’ve got a message for you, Tammy: I haven’t been able to stand you since high school.”

“But you and I dated in high school!”

“Precisely.”

“Ooh, you’re a jerk, Ted.”

Perhaps I’m an overly-critical reader (actually, I’d better be, or I wouldn’t be good at my job), but a little bit of barb-trading goes a long way for me. Call me zany, but I would rather be shown Tammy and Ted’s mutual loathing through action, rather than merely hearing it in their words.

Ted could, for instance, be lying about his feelings in high school. That would automatically render their relationship more complex — and thus more interesting — than simple mutual hatred. In fact, mixed emotions are almost always more intriguing on the page than simple, straightforward feelings.

Especially if, as we’ve seen in pretty much all of today’s examples, the characters are going around bellowing about their feelings as if they were traipsing about in the last act of La Bohème — and expressing those emotions with a pinpoint accuracy that would make living and dead poets alike turn bright green with envy.

Allow me to make a subversive suggestion: people aren’t always telling the truth when they say that they’re in love. Or in hate, for that matter.

Occasionally, they have been known to change their minds on the subject. Some are reluctant to name their emotions at all, and still others are prone to aping the emotion that they believe the person sitting across from them expects them to be feeling.

Here’s a shocker of a revelation: human beings are complex critters, far more so than they appear in the average interview scene in a manuscript submission. Individuals have even been known — sacre bleu! — to mislead total strangers who show up, demanding information about that set of sextuplets who fell down the well thirty years ago.

Or DID they?

Actually, in any interview scene, it’s worth giving some serious thought to having the information-imparter lie, distort, or soften the facts he’s conveying. If the protagonist has to guess what is and is not true, the scene automatically becomes more dynamic than if she’s just nodding and saying, “Oh, that must be so hard for you,” or “What do you mean, Uncle George has left me his once-lucrative sheep ranch in Bolivia?”

After all, logically speaking, in scenes where the protagonist is extracting information from a stranger, why SHOULD the imparter tell the absolute and complete truth? Would you tell your deepest, darkest secret to a complete stranger who showed up on YOUR doorstep demanding answers?

I ask this rhetorically, coming from a family where total strangers regularly show up on our respective doorsteps and demand answers about what certain well-known deceased writers were REALLY like.

But even among those not used to being trapped into impromptu interviews, I would suspect that compulsive truth-telling to strangers is not the norm. People have been known to equivocate a bit when someone they’ve never seen before abruptly appears and demands to be told intimate life details. Even very nice people.

I know; shocking.

But such a possibility amazingly seldom seems to trouble the daydreams of your garden-variety protagonist. A good 90%, interviewers in novel submissions just accept that they are being told the truth, the whole truth, and nothing but the truth.

Yet in an interview scene — again, especially one that opens a book — certainty is almost always less interesting than doubt, just as reading about complete amity is less gripping than interpersonal friction. And in the real world, complete understanding, let alone agreement, between two people is rare enough that I think it should be regarded as remarkable.

There’s a reason that most professional readers will advise against writing much in the first person plural, after all, despite the success of the Greek chorus narration in Jeffrey Eugenides’ THE VIRGIN SUICIDES: interpersonal conflict is, generally speaking, far more interesting than pages at a time of harmonious agreement.

Let your characters disagree; let them quibble. And let them lie to one another occasionally. Both your plot and your characters will thank you for allowing them to be more complex.

Keep up the good work!

Avoiding the bad laughter, as well as a few more good choice words about Hollywood Narration

    

Before I launch back into dissection of the all-too-pervasive Hollywood narration phenomenon, I should amend an oversight from last time: I brought up the concept of bad laughter without really talking about why it can be death to a manuscript submission. Rather than leaving those new to the concept whimpering in confusion, I’m going to revisit it briefly now.

A bad laugh, for those of you who missed yesterday’s post, is a giggle that the author did not intend for the reader to enjoy, but arise from the narrative anyway. It typically arises when the reader (or audience member; it’s originally a moviemaker’s term) is knocked out of the story by a glaring narrative problem: an obvious anachronism in a historical piece, for instance, or a too-hackneyed stereotype, continuity problem, or unbelievable plot twist.

Or, most commonly, just a really, really bad line of dialogue. It can spring from many sources, but in the moment it occurs, it invariably shatters the reader or viewer’s willing suspension of disbelief, causing her to stand, however briefly, outside the world created by the story.

That’s bad.

Hollywood narration is NOTORIOUS for provoking bad laughter, because by this late date in storytelling history, the talkative villain, the super-informative coworker, and the married couple who congratulate themselves on their collective history have appeared so often that even if what they’re saying isn’t a cliché, the convention of having them say it is.

Take it from a familiar narrator-disguised-as-onlooker: “But wait! Up in the sky! Is it a bird? Is it a plane? No, it’s Superman!”

Openings of novels are more likely to contain Hollywood narration than any other point in a book, because of the writer’s perceived imperative to provide all necessary backstory — and usually physical description of the main characters and environment as well — the nanosecond that the story begins. Here again, we see the influence of film upon writing norms: since film is a visual medium, we audience members have grown accustomed to learning PRECISELY what a character looks like within seconds of his first appearance.

We’ve all grown accustomed to this, right? Yet there’s actually seldom a good narrative reason to provide all of this information to the reader right off the bat.

Listen: as I have undoubtedly pointed out before, TV and movies are technically constrained media; they rely upon only the senses of sight and sound to tell their stories. While a novelist can use scents, tastes, or physical sensations to evoke memories and reactions in her characters as well, a screenwriter can only use visual and auditory cues. A radio writer is even more limited, because ALL of the information has to be conveyed through sound.

So writers for film, TV, and radio have a pretty good excuse for utilizing Hollywood narration, right? Whatever they cannot show, they must perforce have a character (or a voice-over) tell. Generally speaking — fasten your seatbelts; this is going to be a pretty sweeping generalization, and I don’t want any of you to be washed overboard by it — a screenplay that can tell its story through sight and sound with little or no unobtrusive Hollywood narration is going to speak to the viewer better than, to put it bluntly, characters launching upon long lectures about what happened when.

Unfortunately, I gather that my view on the subject is not shared by all movie producers.

How many times, for instance, have you spent the first twenty minutes of a film either listening to voice-over narration setting up the premise (do I hear a cheer for the otherwise excellent THE ROYAL TENENBAUMS, where an unseen but undoubtedly huge and Godlike Alec Baldwin in the Sky told us all we needed to know? Anybody?) or listening to the protagonist fill in the nearest total stranger on his background and goals? Here’s a very common gambit:

Pretty neighbor (noticing the fact that our hero is toting several boxes clearly marked ACME MOVING AND STORAGE): “So, are you just moving into the building?”

Hunky hero (leaning against the nearest doorjamb, which happens to be beautifully lit, as doorjambs so frequently are): “Yeah, I just drove in from Tulsa today. This is my first time living in the big city. When my girlfriend left me, I just tossed everything I owned into the car and drove as far as I could.”

Pretty neighbor (stepping into his good lighting as much as possible): “Well, I’m a New York native. Maybe I could show you around town.”

Hunky hero: “Well, since you’re the first kind face I’ve seen here, let me take you to dinner. I haven’t eaten anything but truck stop food in days.”

Now, this economical (if trite) little exchange conveyed a heck of a lot of information, didn’t it? It established that both Hunky and Pretty live in the same building in New York, that he is from the Midwest and she from the aforementioned big city (setting up an automatic source of conflict in ideas of how life should be lived, if they should get romantically involved), that he has a car (not a foregone conclusion in NYC), that they are attracted to each other, and that he, at least, is romantically available.

What will happen? Oh, WHAT will happen?

When the scene is actually filmed, call me nutty, but I suspect that this chunk of dialogue will be accompanied by visual clues to establish that these two people are rather attractive as well; their clothing, hairstyles, and accents will give hints as to their respective professions, upbringings, socioeconomic status, and educational attainments.

Writers of books, having been steeped for so many years in the TV/movie/radio culture, tend to think such terse conveyance of information is nifty — especially the part where the audience learns everything relevant about the couple within the first couple of minutes of the story. They wish to emulate it, and where restraint is used, delivering information through dialogue is a legitimate technique.

The problem is, on film, it often isn’t used with restraint — and writers of books have caught that, too.

I’m not talking about when voice-overs are added to movies out of fear that the audience might not be able to follow the plot otherwise — although, having been angry since 1982 about that ridiculous voice-over tacked onto BLADE RUNNER, I’m certainly not about to forgive its producers now. (If you’ve never seen either of the released versions of the director’s cut, knock over anybody you have to at the video store to grab it from the shelf, proto. It’s immeasurably better.)

No, I’m talking about where characters suddenly start talking about their background information, for no apparent reason other than that the plot or character development requires that the audience learn about the past.

If you have ever seen any of the many films of Steven Spielberg, you must know what I mean. Time and time again, his movies stop cold so some crusty old-timer, sympathetic matron, or Richard Dreyfus can do a little expository spouting of backstory. You can always tell who the editors in the audience are at a screening of a Spielberg film, by the say; we’re the ones hunched over in our seats, muttering, “Show, don’t tell. Show, don’t tell!” like demented fiends.

I probably shouldn’t pick on Spielberg (but then, speaking of films based on my friend Philip’s work, have I ever forgiven him for changing the ending of MINORITY REPORT?), because this technique is so common in films and television that it’s downright hackneyed. Sometimes, there’s even a character whose sole function in the plot is to be a sort of dictionary of historical information.

For my nickel, the greatest example of this by far was the Arthur Dietrich character on the old BARNEY MILLER television show. Dietrich was a humanoid NEW YORK TIMES, PSYCHOLOGY TODAY, SCIENTIFIC AMERICAN, and KNOW YOUR CONSTITUTION rolled up into one. (He also, several episodes suggested, had a passing familiarity with the KAMA SUTRA as well — but then, it was the ’70s.) Whenever anything needed explaining, up popped Dietrich, armed with the facts: the more obscure the better.

The best thing about the Dietrich device is that the show’s writers used it very self-consciously as a device. The other characters relied upon Dietrich’s knowledge to save them research time, but visibly resented it as well. After a season or so, the writers started using the pause where the other characters realize that they should ask Dietrich to regurgitate as a comic moment.

(From a writer’s perspective, though, the best thing about the show in general was the Ron Harris character, an aspiring writer stuck in a day job he both hates and enjoys. Even when I was in junior high school, I identified with Harris.)

Unfortunately, human encyclopedia characters are seldom handled this well, nor is conveying information through dialogue. Still, we’ve all become accustomed to it, so people who point it out seem sort of like the kid in THE EMPEROR’S NEW CLOTHES:

“Why has Mr. Spielberg stopped the action to let that man talk for three solid minutes about backstory, Mommy?”

“Hush, child. There’s nothing odd about that.”

Well, in a book, there’s PLENTY odd about that, and professional readers are not slow to point it out. It may seem strange that prose stylists would be more responsible than screenwriters for reproducing conversations as they might plausibly be spoken, but as I keep pointing out, I don’t run the universe. I can’t make screenwriters do as I wish; I have accepted that, and have moved on.

However, as a writer and editor, I can occasionally make the emperor put some clothes on.

By and large, agents, editors, and contest judges share this preference for seeing their regents garbed. It pains me to tell you this, but I have actually heard professional readers quote Hollywood narration found in a submitted manuscript aloud, much to the disgusted delight of their confreres.

What may we learn from this degrading spectacle? At minimum, that an over-reliance upon Hollywood narration is not going to win your manuscript any friends if your characters tell one another things they already know.

There’s a lesson about bad laughter to be learned here as well: if a device is over-used in submissions — as Hollywood narration undoubtedly is — using it too broadly or too often in a manuscript can in and of itself provoke a bad laugh from a pro.

And that, too, is bad, at least for your manuscript’s prospects of making it past Millicent.

This danger looms particularly heavily over first-person narratives, especially ones that aspire to a funny voice. All too often, first-person narratives will rely upon the kind of humor that works when spoken — the anecdotal kind, the kind so frequently used in onscreen Hollywood narration — not realizing that pretty much by definition, a spoken joke does not contain sufficient detail to be funny on the printed page.

Especially on a printed page where the narrator is simultaneously trying to sound as if he’s engaging the reader in everyday conversation and provide the necessary backstory for the reader to follow what’s going on. Think, for instance, of the stereotypical voice-over in a film noir:

Someone kicked my office door down, and this blonde walked in on legs that could have stretched from here to Frisco and back twice, given the proper incentive. She looked like a lady it wouldn’t be hard to incite.

Now, that would be funny spoken aloud, wouldn’t it? On the page, though, the reader would expect more than just a visual description — or at any rate, a more complex one.

To professional readers, humor is often a voice issue. Not many books have genuinely amusing narrative voices, and so a good comic touch here and there can be a definite selling point for a book. The industry truism claims that one good laugh can kick a door open; in my experience, that isn’t always true, but if you can make an agency screener laugh out loud within the first page or two, chances are good that the agency is going to ask to see the rest of the submission.

But think about why the example above made you smile, if it did: was if because the writing itself was amusing, or because it was a parody of a well-known kind of Hollywood narration?

More to the point, if you were Millicent, fated to screen 50 manuscripts before she can take the long subway ride home to her dinner, would you be more likely to read that passage as thigh-slapping, or just another tired piece of dialogue borrowed from the late-night movie?

The moral, should you care to know it: just because a writer intends a particular piece of Hollywood narration to be funny doesn’t mean that it won’t push the usual Hollywood narration buttons.

I shudder to tell you this, but the costs of such narrative experimentation can be high. If a submission TRIES to be funny and fails — especially if the dead-on-arrival joke is in the exposition, rather than the dialogue — most agents and editors will fault the author’s voice, dismissing it (often unfairly) as not being fully developed enough to have a sense of its impact upon the reader. It usually doesn’t take more than a couple of defunct ducks in a manuscript to move it into the rejection pile.

I hear some resigned sighing out there. “Okay, Anne,” a few weary voices pipe, “you’ve scared me out of the DELIBERATE use of Hollywood narration. But if it’s as culturally pervasive as you say it is, am I not in danger of using it, you know, inadvertently?”

The short answer is yes.

The long answer is that you’re absolutely right, weary questioners: we’ve all heard so much Hollywood Narration in our lives that it is often hard for the author to realize she’s reproducing it. Here is where a writers’ group or editor can really come in handy: before you submit your manuscript, it might behoove you to have an eagle-eyed friend read through it, ready to scrawl in the margins, “Wait — doesn’t the other guy already know this?”

For self-editing, try this little trick: flag any statement that any character makes that could logically be preceded by variations upon the popular phrases, “as you know,” “as I told you,” “don’t you remember that,” and/or “how many times do I have to tell you that. Reexamine these sentences to see whether they should be cut, or at any rate reworked into more natural dialogue.

Another good indicator: if a character asks a question to which s/he already knows the answer (“Didn’t your brother also die of lockjaw, Aunt Barb?”), what follows is pretty sure to be Hollywood narration.

Naturally, not all instances will be this cut-and-dried, but these tests will at least give you a start. When in doubt, reread the sentence in question and ask yourself: “What is this character getting out making this statement, OTHER than doing me the favor of conveying this information to the reader?”

And while you’re at it, would you do me a favor, please, novelists? Run, don’t walk, to the opening scene of your novel (or the first five pages, whichever is longer) and highlight all of the backstory presented there. Then reread the scene WITHOUT any of the highlighted text.

Tell me — does it still hang together dramatically? Does the scene still make sense? Is there any dialogue left in it at all?

If you answered no to any or all of these questions, sit down and ponder one more: does the reader REALLY need to have all of the highlighted information from the get-go? Or am I just so used to voice-overs and characters spouting Hollywood narration that I thought it was necessary when I first drafted it but actually isn’t?

Worth a bit of mulling over, isn’t it? Keep up the good work!

In which I lose my struggle to stop myself from condemning Hollywood Narration yet again

Before I justify that rather Dickensian title, allow me to a little something to those of you reading this outside the confines of the United States, its territories, and wherever its military happen to be traipsing about these days: today is Memorial Day, the national holiday originally established to honor the dead of our Civil War, but expanded in an effort to conserve holiday time after World War I to include perished servicepeople of all of our wars and police actions.

In a similar conservation push, the birthdays of Presidents Washington and Lincoln were collapsed into a single day in February. And nowhere is the birthday of the late Millard Fillmore celebrated at all, except perhaps in his hometown.

So why, you may be wondering — and who could blame you? — have I seen fit to commemorate the day with a close-up shot of Montana ledge stone?

Because, it may shock you to learn, people who don’t happen to be addicted to writing frequently use three-day weekends for home improvement projects. And mattress sales, apparently.

Anyway, it’s pretty, isn’t it? What more do you people want from me?

Last time, I introduced you to the Short Road Home’s glamorous first cousin, Hollywood Narration, the all-too-common phenomenon of one character’s telling another things they already both know, purely for the sake of filling in the reader. Hollywood Narration is when information is conveyed by dialogue between persons who both already know the information perfectly well — and thus have absolutely no legitimate reason to be having this conversation at all.

As in this little gem of human interaction:

“So, Tim, how was your work at the steel mill today?” Sally asked, drying her rough hands on the fraying dishtowel that served her as a makeshift apron. “Having worked there for fifteen years — one before we married, two more before the twins were born, and five years since our youngest girl, Sammy, fell off the handlebars of Tim Junior’s bike and sustained brain damage, forcing me to quit my beloved teaching job and stay home to help her re-learn basic life skills — I imagine you sometimes get sick of the daily grind. But you are my husband, my former high school sweetheart, so I try to be supportive of all you do, just like that time I went down to the police station in the middle of the night in my pink flannel nightgown to bail you and your lifetime best friend, Owen Filch, out after you two drank too much near-beer and stole us the biggest Sequoia in the local national park — renowned for its geysers — for our Christmas tree.”

Tim shook his graying head ruefully. “Ah, I remember; I had gotten you that nightgown for Valentine’s Day the year that little Betty, then aged six, played Anne Frank in the school play. As you know, Sally, I am committed to working hard to support you and the kids. But since our eldest daughter, the lovely and talented Selma, won that baton-twirling scholarship to State, I have felt that something was lacking in my life.”

“Why don’t you go downstairs to the workshop you built in the basement with the money from that car-crash settlement? You know how much you enjoy handcrafting animals of the African veldt in balsa wood.”

“What would I do without you, honey?” Tim put his arms around her ample form. “I’ve loved you since the moment I first saw you, clutching a test tube over a Bunsen burner in Mr. Jones’ chemistry class in the tenth grade. That was when the high school was housed in the old building, you recall, before they had to move us all out for retrofitting.”

“Oh, Tim, I’d had a crush on you for six months by then, even though I was going out with my next-door-neighbor, Biff Grimley, at the time! Isn’t it funny how he so suddenly moved back to town, after all those years working as an archeologist in the Sudan?” Tim did not respond; he was kissing her reddish neck. “But you always were an unobservant boy, as your mother Gladys, all sixty-four years of her, always points out when she drops by for her weekly cup of Sanka and leftover cookies from my Tuesday night Episcopalian Women’s Empowerment Group social.”

Okay, so this is a pretty extreme example — but honestly, anyone who has read manuscripts professionally for more than a few weeks has seen Hollywood Narration almost this bald. Make no mistake: this is telling, not showing in its baldest form.

The term Hollywood Narration is mine, of course; due to its widespread unpopularity, it is cursed under many names throughout the publishing world. My personal favorite is the SF/fantasy moniker, as you know, Bob… dialogue. Whatever you like to call it, as far as I’m concerned, it’s one of the scourges of both the modern publishing industry AND the screenwriters’ guild.

For today, I had planned to leave my brief warning to this: when you are scanning your submission for this type of dialogue — and you most assuredly should; I’m not the only professional reader it drives completely nuts — try VERY hard, please, not to imagine those fine actors you’ve mentally cast in the movie version of your book (c’mon, every writer does that) reading these lines.

Why? Well, due to the unfortunate ubiquity of Hollywood Narration in movies, it might just sound logical to you.

I meant to leave it at that; truly, I did. But on Saturday night, I was dragged kicking and screaming to a midnight showing of a Korean horror film, Epitaph, in which a good 10 out of the first 20 minutes of the film consisted of characters telling one another things they already knew. Most of the other ten consisted of silent shots of sheets blowing symbolically in the wind — in a GHOST STORY; get it? — and characters standing frozen in front of doors and windows that they SHOULD NOT OPEN UNDER ANY CIRCUMSTANCES.

I pass along this hard-earned nugget of wisdom to those of you who may not have a chance to catch the flick: should you ever find yourself in a haunted hospital in Korea, don’t touch anything with a latch and/or a doorknob. Especially if you happen to be standing in front of the body storage wall in the morgue.

Trust me on this one.

Now, I would be the first to admit that horror is not really my mug of java — I spent fully a quarter of the film with my eyes closed and ears blocked, which I suppose is actually a rather high recommendation for those fond of the genre — so I did not see every syllable of the subtitles. But the fact is, my companions and I were not the only ones giggling audibly during the extensive backstory-by-dialogue marathons. An actual sample, as nearly as I can remember it:

Grown daughter: Dad, are you lonesome?

Doctor-who-interned-in-haunted-hospital: (chuckling ruefully) No, of course not.

Grown daughter: You’re too hard on yourself, Dad. Stepmother had a heart condition long before you married her.

Doctor-who-interned-in-haunted-hospital: But we were married for less than a year!

Grown daughter: You can’t blame yourself. Mother died in having me, and Stepmother had been sick for a long time. It’s not your fault. It’s nothing you did.

Doctor-who-interned-in-haunted-hospital: (weighed down by Ominous Guilt) Both marriages lasted less than a year.

I’m sure that you can see the narrative problem — can you imagine a more blatant telling, rather than showing, presentation? — but the laughter from the audience was a dead giveaway that this dialogue wasn’t realistic. Bad laughter is a sure sign that the audience has been pulled out of the story.

Too addled with a surfeit of Hollywood narration to sleep — and, frankly, not overly eager to dream about a maniacally-laughing, high C-singing dead mother standing by her small, terrified daughter’s hospital bed in a ward where there were NO OTHER PATIENTS — I ran home, buried myself under the covers, and reached for the nearest book to sooth my mind and distract my thoughts from the maniacally-laughing, high C-singing dead woman who was clearly lurking nearby.

As luck would have it, the volume in question was a set of Louisa May Alcott’s thrillers; I had used it as an example on this very blog not so long ago. Yet no sooner had I opened it when my eye fell upon this sterling opening to a story promisingly entitled, THE MYSTERIOUS KEY AND WHAT IT OPENED. Because I love you people, I have excised the scant narration and turgid poetry of the original, so you may see the dialogue shine forth in untrammeled splendor:

“This is the third time I’ve found you poring over that old rhyme. What is the charm, Richard? Not its poetry, I fancy.”

“My love, that book is a history of our family for centuries, and that old prophecy has never yet been fulfilled…I am the last Trevlyn, and as the time draws near when my child shall be born, I naturally think of the future, and hope he will enjoy his heritage in peace.”

“God grant it!” softly echoed Lady Trevlyn, adding, with a look askance at the old book, “I read that history once, and fancied it must be a romance, such dreadful things are recorded in it. Is it all true, Richard?”

“Yes, dead. I wish it was not. Ours has been a wild, unhappy race till the last generation or two. The stormy nature came in with the old Sir Ralph, the fierce Norman knight, who killed his only sun in a fit of wrath, by a glow with his steel gauntlet, because the boy’s strong will would not yield to his.”

“Yes, I remember, and his daughter Clotilde held the castle during a siege, and married her cousin, Count Hugo. ‘Tis a warlike race, and I like it in spite of the mad deeds.”

“Married her cousin! That has been the bane of our family in times past. Being too proud to mate elsewhere, we have kept to ourselves till idiots and lunatics began to appear. My father was the first who broke the law among us, and I followed his example: choosing the freshest, sturdiest flower I could find to transplant into our exhausted soil.

“I hope it will do you honor by blossoming bravely. I never forget that you took me from a very humble home, and have made me the happiest wife in England.”

“And I never forget that you, a girl of eighteen, consented to leave your hills and come to cheer the long-deserted house of an old man like me,” her husband returned fondly.

“Nay, don’t call yourself old, Richard; you are only forty-five, the boldest, handsomest man in Warwickshire. But lately you look worried; what is it? Tell me, and let me advise or comfort you.

“It is nothing, Alice, except my natural anxiety for you…”

By this point in the text, tangling with the maniacally-laughing, high C-singing dead harpy was beginning to look significantly better to me. Clearly, the universe was nudging me to set forth again like the Ghosts of Christmas Past, Present, and Future to warn writers to alter their sinful ways before it was too late.

Just in case anyone out there didn’t spot the logic problem here: generally speaking, in real life, people do not recite their basic background information to kith and kin that they see on a daily basis. Unless someone is having serious memory problems, it is culturally accepted that when a person repeats his own anecdotes, people around him will stop him before he finishes.

Because, among other things, it’s BORING.

Yet time and again in print, writers depict characters wandering around, spouting their own résumés without any social repercussions. Not to mention listing one another’s physical and mental attributes, informing each other of their respective ages and marital histories, listing the articles of furniture in the room, placing themselves on a map of the world, and all of the other delights we saw above.

As we may see from Aunt Louisa’s example, authors have been using characters as mouthpieces for background for an awfully long time. Dickens was one of the all-time worst violators of the show, don’t tell rule, after all. Since the rise of television and movies — and going back even farther, radio plays — certain types of Hollywood Narration have abounded still more in manuscripts.

See dialogue above, lifted from the Korean horror movie. Or any of the films of Stephen Spielberg.

Oh, don’t get me started — but since you have, let me suggest something radical: readers tend to be pretty smart people. They are often, bless their respective hearts, quite capable of looking at an opening like this and remarking, “Hey, wait a minute: real people would have no reason to say these things to each other. Isn’t it just possible that the author is placing this dialogue into their mouths merely so I will know what’s going on?”

And you know something? They would be right. But that’s not all that’s going on here.

Like so many transgressions of the show, don’t tell rule, Hollywood Narration does provide some definite benefits to the writer who incorporates it. placing backstory and description in dialogue instead of narrative text is a shorthand technique, a means of allowing the author to skip showing entire scenes — or, even more commonly, to avoid figuring out how to reveal necessary information in a slower, more natural manner.

It is, in short, a trick — which is precisely how a professional reader who has seen it used 500 times this month tends to regard it. Millicent might not see it as necessarily the result of narrative laziness (although it can be that, too), but at least as evidence of a writer’s not being conversant with the many ways a text can convey information to a reader without just coming out and telling him outright.

Next time, I’m going to talk a bit more about this form of sleight-of hand and why so many aspiring writers seem to be so very fond of it. In the meantime, if you find yourself standing in front of a wall of drawers in a Korean morgue, keep your hands to yourself, okay? Maniacally-laughing, high C-singing spirits tend to be a trifle hard to shake once wakened.

Keep up the good work!

Laying the foundations of plot so they don’t fly up and hit passersby in the nose

What did you expect me to be taking pictures of while workers are crawling all over my yard for months on end — rainbows and cattle?

Last time, I wrote about how frustrating many professional readers find it when a narrative forces them to follow a poor interviewer through an information-seeking process that seems one-sided or lacking in conflict. Or when — heaven forbid — the answers just seem to fall into the protagonist’s lap without significant effort on her part, exactly as if — wait for it — SOMEONE HAD PLANNED IT THAT WAY.

Strange to say, even though a reader would have to be pretty obtuse indeed (or very into the postmodern conceptual denial of individual authorship) not to realize that any protagonist’s adventures have in fact been orchestrated by a writer, a too-obvious Hand of the Creator can yank the reader out of the story faster than you can say, “Sistine Chapel ceiling.”

To work on the printed page, fate has to move in slightly more mysterious ways. Or at least in interesting ones.

Which is to say: interview scenes are legendary in the biz for drooping, even in an otherwise tight manuscript. And let’s face it — almost every plot involves some element of detective work, however minor. It’s worth triple-checking ALL of your manuscript’s interviews for flow and excitement.

Especially, if you’ll forgive my saying so, toward the middle and the end of a book, where protagonists — or is it their creators? — often become a tad tired of searching for the truth. At that point, crucial clues hidden for years like Ali Baba’s treasure frequently start leaping out of the woodwork, screaming, “Here I am — discover me, already!”

As we all know, though, an agent, editor, screener, and/or contest judge needs to get through the early pages of a submission before getting to its middle or end — so it would behoove you to pay very close attention to the pacing of any interview scene that occurs in the first chapter, particularly within the first few pages, as this is the point in your submission where a screener is most likely to stop reading in a huff.

Was that giant gust of wind I just heard the collective gasp of all of you out there whose novels open with an interview scene?

I’m guessing so; an AMAZINGLY high percentage of novel submissions open with interviews or discussions of the problem at hand. The protagonist gets a phone call on page 1, for instance, where he learns that he must face an unexpected challenge: violà , an interview is born, as the caller fills him in on the details.

Or the book opens with the protagonist rushing into the police station and demanding to know why her son’s killer has not yet been brought to justice: another interview scene, as the police sergeant responds.

Or the first lines of the book depict a husband and wife, two best friends, cop and partner, and/or villain and victim discussing the imminent crisis: bingo.

Or, to stick to the classics, this dame with gams that would make the 7th Fleet run aground slinks into the private dick’s office, see, and says she’s in trouble. Bad trouble — as opposed to the other kind — and could he possibly spare a cigarette?

“What kind of trouble?” he asks — and lo and behold, another interview begins.

There are good reasons that this scene is so popular as an opener, of course: for at least a decade now, agents and editors at conferences all over North America have been urging aspiring writers to open their books with over conflict. And conversation is a great way to convey a whole lot of background information very quickly, isn’t it?

Or, to put it in the language of writing teachers, dialogue is action.

My long-term readers are giggling right now, I suspect, anticipating my launching into yet another tirade on what I like to call Hollywood narration (a.k.a. Spielberg’s disease), movie-style dialogue where characters tell one another things they already know in order to provide the audience with needed data. As in:

My long-term readers are giggling right now, I suspect, anticipating my launching into yet another tirade on what I like to call Hollywood narration (a.k.a. Spielberg’s disease), movie-style dialogue where characters tell one another things they already know purely in order to provide the audience with background information.

Openings of novels are NOTORIOUS for this. As in:

“So, Molly, we have been shipwrecked on this desert island now for fifteen years and seven months, if my hash marks on that coconut tree just to the right of our rustic-yet-comfortable hut. For the first four years, by golly, I thought we were goners, but then you learned to catch passing sea gulls in your teeth. How happy I am that we met thirty-seven years ago in that café just outside Duluth, Minnesota.”

“Oh, Tad, you’ve been just as helpful, building that fish-catching dam clearly visible in mid-distance right now if I squint — because, as you may recall, I lost my glasses three months ago in that hurricane. If only I could read my all-time favorite book, Jerzy Kosinski’s BEING THERE, which so providentially happened to be in my unusually-capacious-for-women’s-clothing coat pocket when we were blown overboard, and you hadn’t been so depressed since our youngest boy, Humbert — named after the protagonist of another favorite novel of mine, as it happens — was carried off by that shark three months ago, we’d be so happy here on this uncharted four-mile-square island 200 miles southwest of Fiji.”

“Well, Molly, at least for the last week, I have not been brooding so much. Taking up whittling at the suggestion of Brian — who, as you know, lives on the next coral atoll over — has eased my mind quite a bit.”

Since I have lectured so often on this VERY common manuscript megaproblem, I shall let this example speak for itself. Suffice it to say that about the NICEST comment this type of dialogue is likely to elicit from a professional reader is, “Show, don’t tell!”

More commonly, it provokes the cry, “Next!”

Did you notice the other narrative sins in that last example, by the way? Guesses, anyone?

Award yourself high marks if you dunned ol’ Molly for making the mistake we discussed earlier this week, over-explaining the rather uninteresting fact that she managed to bring her favorite book with her whilst in the process of being swept overboard by what one can only assume were some pretty powerful forces of nature.

And as much as I love the work of Jerzy Kosinski, in-text plugs like this tend to raise the hackles of the pros — or, to be more precise, of those who did not happen to be involved with the publication of BEING THERE (a terrific book, by the way) or currently employed by those who did.

Besides, it’s not a very telling detail.

Hear me out. Writers who include such references usually do so in the rather charmingly myopic belief that a person’s favorite book is one of the most character-revealing bits of information a narrative could possibly include. However, this factoid is unlikely to be of even the vaguest interest to someone who hadn’t read the book in question — and might well provoke a negative reaction in a reader who had and hated it.

Out comes the broken record again: it’s never a good idea to assume that ANY conceivable reader of one’s book will share one’s tastes. Or worldview.

Give yourself an A+ for the day if you said immediately, “Hey, if the island is uncharted, how does Molly know so precisely where they are? Wouldn’t she need to have either (a) seen the island upon which she is currently removed upon a map, (b) seen it from space, or (c) possess the magical ability to read the mind of some future cartographer in order to pinpoint their locale with such precision?”

And you have my permission to award yourself a medal if you also cried to the heavens, “Wait — why is the DIALOGUE giving the physical description here, rather than, say, the narrative prose?”

Good call — this is Hollywood dialogue’s overly-chatty first cousin, the physical description hidden in dialogue form. It tends to lurk in the shadows of the first few pages of a manuscript:

Link glanced over at his wife. “What have you been doing, to get your long, red hair into such knots?”

“Not what you’re thinking,” Gloria snapped. “I know that look in your flashing black eyes, located so conveniently immediately below your full and bushy eyebrows and above those cheekbones so chiseled that it would, without undue effort, be possible to use them to cut a reasonably soft cheese. Perhaps not a Camembert — too runny — but at least a sage Derby.”

“I’m not jealous sexually.” Link reached over to pat her on the head. “As your hairdresser, I have a right to know where those luxurious tresses have been.”

Why might introducing physical descriptions of the characters through opening-scene dialogue seem a bit clumsy to someone who read hundreds of submissions a month?

Well, again, it’s common, but this time, at least, that’s not the primary reason. Any guesses?

If you said that Link and Gloria are telling each other things they obviously already know, throw yourself a party. In this era of easily-available mirrors, it’s highly unlikely that anyone would NOT know that he possessed, say, dark eyes, and even the most lax of personal groomers would undoubtedly be aware of her own hair’s color and length.

The only reason this information could POSSIBLY appear in dialogue between them, then, is to inform a third party. Like, for instance, the reader.

That’s a pretty good test for Hollywood narration, incidentally: if a statement doesn’t serve any purpose other than revealing a fact to the reader, as opposed to the character to whom it is said, then it’s Hollywood narration. And it should go.

If you also said that Link and Gloria are engaging in dialogue that does not ring true, give yourself extra credit with sprinkles and a cherry on top. With the exception of medical doctors, art teachers, and phone sex operators, real people seldom describe other people’s bodies to them.

It’s just not necessary. My SO has just walked into the room, but I cannot conceive of any impetus that might prompt me to say to him, “Rick, your eyes are green,” despite the fact that his eyes are indeed green, and I might conceivably want a reader to know it.

In the interest of scientific experimentation, though, I just tried saying it out loud. It did not produce scintillating conversation. Turns out he already knew.

There you have it — several more excellent reasons to read your manuscript OUT LOUD and IN ITS ENTIRETY before you submit it, my friends, and an even better reason to have a third party read it before you send it off to an agent or editor: to see if the dialogue sounds like something a real person might actually say (as Hollywood narration doesn’t), and to check that it is interesting enough to keep a reader moving from line to line in those interview scenes.

More on dialogue spiciness next time — that is, if I can resist the burning desire not to take another run at Hollywood Narration. Must…remain…strong…

Somehow, I suspect that I’m going to lose this particular battle. Keep up the good work!

A beautiful picture — and a few tips on increasing your protagonist’s interview skills

Isn’t that photo GORGEOUS? It’s by one of my favorite art photographers, Lana Z Caplan, from her new book, Sites of Public Execution. Here’s a description:

SITES OF PUBLIC EXECUTION: Photographs and stories of former sites of public execution around the world.

Paired with interesting facts and stories of the events that took place in these public places, sepia-toned photographs, shot in Beijing, Paris, London, Florence, Rome and Massachusetts, present the contemporary appearances of locales used for hangings, beheadings, and burnings, some in the transient fury of revolution, some in long-term state-sanctioned spectacles.

For a PDF preview of the book, please visit Lana’s website.

Normally, I wouldn’t post an announcement about a book of photography here on Author! Author!, but Lana’s work moves me deeply — so much so, in fact, that I have one of her pieces hanging where I can glance up at it frequently while I write. We met at an artists’ colony several years ago; then, the provocative work-in-progress hanging in her studio made me downright giddy.

And yes, I HAVE been posting quite a few announcements of new releases lately — for some reason, I know many, many talented people bringing out books this spring. I can only conclude that publishing houses have started weighing connections to me heavily in their considerations.

Or perhaps I just know a heck of a lot of writers. In any case, this spring has certainly enriched my bookshelves, let me tell you.

Okay: on to the topic du jour.

As we’ve been going through various common narrative problems, I’ve noticed something: either due to my excessive saintliness or a desire to save the best, if not for last, at least for later in this series, I’ve been concentrating for the most part upon avoiding some of the more notorious agency screeners’ pet peeves, rather than merely upon what tends to annoy me in a text. For the next week or so, however, I have decided to cut loose and lay bare the narrative problems that make me foam at the mouth, professionally speaking.

That’s right: for the next little while, it’s going to be all about me, me, me.

Today, I’m going to concentrate upon one of my all-time favorite kinds of expendable text: the kind of dialogue that results from a protagonist’s being a really, really poor interviewer.

I heard that tittering out there. Seriously, a protagonist who doesn’t ask good questions — or necessary follow-up questions — can slow a novel, memoir, or creative nonfiction book to a limping crawl.

Why does it matter how skilled a questioner the protagonist is, you ask, unless s/he is a journalist of some sort? Simple: many, many, MANY novel plots require their protagonists to learn something that they do not already know – and, more importantly, that the reader does not already know.

Who killed the Earl of Cheswick, for instance, or why so many people are interested in that darned ugly Maltese Falcon. In the pursuit of answers to these and other burning questions, the protagonist is, necessarily, frequently forced into the role of interviewer, trying to extract information from other characters.

What a pity, then, that protagonists have a nasty habit of slowing down the collective search for truth by neglecting to promising lines of questioning, failing to follow up on something just said, or just plain being too polite to ask the questions the reader is dying to ask herself, but can’t.

It tends to run a little something like this:

“I swear,” Reginald claimed, one hand over his heart and the other hovering over the graying head of his sainted mother, “that’s all I know. Please don’t ask me any more questions.”

Janet drummed her long piano-player’s fingers on the rich mahogany tabletop. Her every instinct told her that he was not telling the truth — or at least not the whole truth. The very fate of Western civilization rested upon her solving this puzzle before midnight tomorrow.

She stood and offered her hand to the old woman. “Charming to meet you, Mrs. Fezziwig. You must come to my house for brunch sometime. I hate to boast, but I make extraordinary deviled eggs.”

Reginald detached their clasped hands so quickly that Janet’s hand burned. “Must you go so soon? Here’s your coat — I’ll walk you down to the cab stand on the corner before I release the vicious dogs that prowl our estate at night to discourage post-midnight visitors.”

Janet fumed, but what could she do? “Goodbye,” she called back from the hallway.

“Don’t forget to sprinkle your eggs with paprika,” she could hear Mrs. Fezziwig bellowing after her. “I love paprika.”

Why would an exchange like this prove annoying to a professional reader like me? Mostly, because it’s a lost opportunity for interesting conflict — rich potential for drama presented then abandoned by the narrative for no apparent reason.

Actually, writers often have what they consider pretty strong reasons for rushing their protagonists away from conflict. Trying to make them more likeable to the reader by demonstrating common courtesy, for instance, or forcing them to work harder to learn the Awful Truth.

Or wanting to stretch the novel from 100 pages to 200. My point is, regardless of the motive, this practice tends to render those of us who read manuscripts for a living a trifle impatient.

Why? Well, in essence, the protagonist becomes the reader’s surrogate in ferreting out information; as a reader, it’s not as though I can jump into the storyline, grab a microphone and tape recorder, and start grilling the usual suspects. After awhile, an inept interviewer can start to annoy the reader by being a poor tour guide to the plot.

I sense some uncomfortable squirming out there, don’t I? “But Anne,” I hear some of you suspense-lovers cry, “a too-good interview would give the whole plot away! What about building tension?”

You have a fine point, suspense-mongers: revealing the truth in slow increments is one way to create suspense. It’s such a fine point that I’m going to spend most of the rest of the post talking about how to do just that.

However, before I do, allow me to observe that making information unavailable through the simple expedient of not having the protagonist ask anyone about it tends to fall very, very flat with readers.

Why? Well, while readers do like to second-guess what’s going to happen next, trust me, it’s going to make your protagonist substantially less likeable if the reader keeps thinking, “Ask about the elephant in the room, you fool! Don’t just walk away!”

A professional reader — such as an agent, editor, contest judge, Millicent, or yours truly — is likely to react with even less sympathy, because a disproportionate percentage of submitted manuscripts create suspense by DELIBERATELY withholding information from the reader.

As in details that the protagonist already knows. We pros like to call this creating false suspense.

The most famous example, of course, is the sleuth from whose perspective the reader has viewed the entire case suddenly stops communicating his thoughts on the page — then gathers all of the still-living characters in the nearest drawing room (there always seems to be one handy, doesn’t there?) and announces, “You may be wondering why I asked you all here…”

Darned right we’re wondering — the reader wants to know why you suddenly withdrew your confidence from him, Mssr. Poirot.

Don’t start feeling too smug, those of you who write something other than mysteries — protagonists’ playing interviewer role is hardly limited to that genre. Think about it: it’s rare that any novel — or, indeed, any book with a plotline — does not contain at least one scene where somebody is trying to extract unknown facts from someone else.

Queries ranging from “Does that cute boy in my homeroom REALLY like me, Peggy?” to “Where did the cattle go, Tex?” aren’t just dialogue filler — typically, they call for character-developing and/or plot-satisfying responses. In fact, it’s a fair bet that any scene that contains one character exclaiming, “What happened?” is the precursor to an in-text interview.

Are you already warming up the highlighting pens, in anticipation of my ordering you to aim them at the interview scenes in your work? Good idea. Such scenes are often worth flagging for revision, because they are so very hard to pace well.

This is true, incidentally, even when the information being revealed is inherently exciting (“If you do not get across the bridge before sunset, giant bats will eat you, Reginald.”), emotionally revealing (“The reason I turned to piracy is – YOU, Father!”), or downright necessary to make the plot work (“Yes, George, although I haven’t seen fit to mention it once in the course of our sixty-two-year marriage, I have always dreamed of going spelunking!”).

Why? Well, when the point of a scene is for information to be revealed to the protagonist (and thus the reader), many writers become so focused upon that data’s being revealed entertainingly that they run to the opposite end of the reticence spectrum and have characters (secondary ones, usually) blurt out the necessary information practically BEFORE the protagonist asks for it.

This, too, is an interviewing problem — and one of the greatest sappers of narrative tension the world has ever known.

Many, many submissions where secrets that have been kept successfully for 25 years burst out of the mouths of the secretive practically the moment that the protagonist walks into the room. So why, the reader is left to wonder, if these secret-keepers are so willing to spill their guts to the first person to ask a direct question, has this information not been revealed before?

The apparent answer: because the plot required that it NOT be revealed before. And that, my friends, is never a sufficient motivation.

Or, to be blunt about it, the narrative should not make it EVIDENT that the hidden information would have been laughably easy to get all along, if only someone had thought to knock on the door of the only person who actually observed that the setting of that fire a decade before that shaped the entire town’s subsequent history.

You can just imagine all of the townsfolk slapping their heads in unison behind closed doors after that perky newcomer digs up the arsonist’s name in a single afternoon: why oh why didn’t it occur to any of us to ask Aunt Bessie why her nephew kept the garage stuffed to the rafters with matches?

Surprisingly often, the protagonist doesn’t even need to ask a question to elicit the revelations of tremendous secrets from minor-but-essential characters. Often, all she has to do is show up, and the legendary recalcitrant loner begins singing like a Rhine maiden: “So, Mr. Bond, now that I have you tied to that chainsaw, it’s time for me to reveal my evil plan…”

In many instances, the protagonist is reduced to helpful nods and murmured promptings on the order of, “Oh, really?” while the imparter engages in a soliloquy that would make Hamlet himself start looking at his watch.

A novel, the last time I checked, was not an opera: in real life, most people do not go around shouting out their deepest, darkest secrets at the top of their lungs to relative strangers.

And that’s what makes secrets interesting, right? In real life, it is actually rather difficult to convince folks to cough up the truth — partially because after one has lived with a lie long enough, one often starts to believe it oneself.

When you are trying to increase the tension throughout a novel, recognizing that truth is often hard to elicit is a powerful tool, one that can revolutionize how you handle interview scenes. They do not need to be essentially one-sided information dumps they so often are.

Instead of regarding them as just necessary exposition-through-dialogue, to be rushed through quickly, why not use the opportunity to introduce some conflict? Or heck, if you really want to get adventurous, some character development?

How? By making the information-imparter more reluctant — which automatically both forces the protagonist to become a better interviewer and renders the information-seeking process more difficult.

Automatically, this small switch makes the scene more interesting, by introducing viable (if brief) conflict between Character A (who wants to learn something) and Character B (who has very good reasons not to pass on the information).

A couple of fringe benefits: your protagonist will come across as smarter, more active, and more determined — and the information elicited will seem more valuable. As convenient as a suddenly-garrulous secret-hider is to the plot, too-easily discovered information runs the risk of seeming…well, ordinary.

So eschew the magic wand that turns the timid secretary who saw her boss murdered 15 years ago and ran off to live in a cave to avoid talking to the police into the operatic diva belting out precisely the information she has devoted to her life to hiding, simply because someone finally asked her a direct question about it. Banish the clue that only required someone opening the right cupboard drawer to find. Give your protagonist some killer interview skills.

Take, in short, a page from the time-honored pirate’s manual: make your treasures hard to dig up. The more difficult they are to find, the more engaged the reader will be in the search process.

More interviewing tips follow next time. In the meantime, keep up the good work!

Trusting the reader to extrapolate (or interpolate) the obvious

Millicent after her third latte of the morning

I’m rather tired today, but since we’ve been talking about such important, fundamental issues lately — showing, rather than telling; constructing a narrative; narrative voice; increasing tension and conflict — I’m eager to push ahead.

I know that many, if not most, came first to Author! Author! looking for guidance on marketing issues such as querying, pitching, and submission, so the Spring of Craft might come as a bit of a surprise. As a book doctor, though, I have to regard craft issues as integral to marketing — after all, a cliché-ridden first page or a storytelling glitch on page 5 has spelled the doom of untold submissions under the ever-watchful eye of Millicent the agency screener.

Basically, I think it’s important for writers to pay attention to both the craft and marketing sides of the equation — and that those bizarre implications we’ve all heard at conferences that a good writer can focus on one to the exclusion of the other are just wrong.

Most of the time, the latter argument veers toward the craft side (as in, a good book will always find a home, apparently magically, regardless of how or even if its author promotes it), so much of the time, I blog under the assumption that my readers already have a pretty firm grasp of the artistic side of the equation. Think of the recent spate of posts as my attempt to balance the equation a little.

I assure you, I haven’t abandoned more overt marketing concerns permanently — and if you’re looking for advice on how to write a query letter, synopsis, etc., before I veer back in the other direction, never fear: you’ll find fairly specific categories in the lengthy list on the right-hand side of this page, under the monthly listings. Also, this blog is searchable for specific terms — check out the wee box in the upper right-hand corner.

For the sake of long-term planning, though, let me ask a question: are many of you planning to pitch at conferences in the months to come? To put it another way, how many of you would LIKE for me to devote a few weeks’ worth of posts to pitching tips between, say, now and the Fourth of July?

I ask because I’ve blogged quite a bit about pitching over the last couple of years (see the many, many categories on it in the list at right), and while I usually like to take a run at it again in early summer, I don’t want to bore my long-term readers into a collective stupor. Especially if that means cutting this jolly interesting series on craft shorter than I’d like.

So if you have a strong opinion either way about a run-down on pitching, please leave a comment, so I can get a sense of popular opinion.

All right, back to craft.

Today, I shall be dealing with a manuscript problem that is frequently invisible to the writer who produced it, yet glaringly visible to a professional reader, for precisely the same reason that formatting problems are instantly recognizable to our pal Millicent: after you’ve see the same phenomenon crop up in 75 of the last 200 manuscripts you’ve read, your eye gets sensitized to it.

I’m talking, of course, about those most cut-able of sentences, statements of the obvious. If you’ll take the trouble to read on, I shall give you an example.

I just heard some of you out there chuckle — you caught me in the act, didn’t you?

Give yourself a gold star for the day if you caught it: the second sentence of the previous paragraph IS an example of a self-evident proposition — and thus could have been cut with absolutely no cost to the text. Knowing that I am a writer addicted to giving examples, where else would my faithful readers look for further explanation other than later in the text? To the PREVIOUS paragraph?

Lest that seem like an over-reaction to an innocent line of text, allow me to give you a peek into the professional reader’s world: when you’re reading in order to catch mistakes — as every agency screener, agent, editor, and contest judge is forced to do, faced with mountains of submissions — you’re inclined to get a mite testy. Occupational hazard.

Why? Well, to maintain the level of focus necessary edit a manuscript really well, it is often desirable to keep oneself in a constant state of hyperirritable reactivity. (You thought it was EASY to continue to care about comma placement enough to wax poetic in the margins about it?)

To a professional reader in such a state, the appearance of a self-evident proposition on a page is like the proverbial red flag to a bull; the reaction is often disproportionate to the offense.

Don’t believe me? Here’s a list of some things professional readers have been known to howl at the pages in front of them, regardless of the damage eardrums belonging to the inhabitants of adjacent cubicles:

*In response to the innocuous line, He shrugged his shoulders: “What else could he possibly have shrugged? His kneecaps?” (Insert violent scratching sounds here, leaving only the words He shrugged still standing in the text.)

*In response to the innocent statement She blinked her eyes: “The last time I checked, eyes are the only part of the body that CAN blink!” (Scratch, scratch, scratch.)

*In response to The queen waved her hand at the crowd: “Waving ASSUMES hand movement! Why is God punishing me like this?” (Scratch, maul, stab pen through paper repeatedly.)

And that’s just how the poor souls react to logically self-evident statements on a sentence level. Assertions of the obvious on a larger scale that send them screaming into their therapists’ offices, moaning that all of the writers of the world have leagued together in a conspiracy to bore them to death.

We haven’t, have we? I missed the last Writers’ World Domination meeting, and no one seems to be able to find the minutes.

Much of the time, self-evident statements are the brainchildren of that niggling authorial anxiety that has kept rearing its under-groomed head throughout much of our recent discussion of narrative construction, not trusting the reader.

In this case, not trusting the reader to be intelligent enough to figure out what’s going on without extensive and meticulous explanation. As in:

As Alison walked into the crowded movie premiere, she noticed that there were so many people there that few seats were left. She would need to move fast to grab the necessary three for herself and her two friends still parking the car in the garage, Georgette and Petunia. She hurried, scanning the rows for empty seats.

Fortunately, this was a movie screening in the greater Seattle area: people had seated themselves in a sort of mohawk down the middle of the theatre, in chairs so directly under the geometric center point of the room that had some enterprising engineer dropped a plumb line from the ceiling and measured seating distribution, the exercise would have revealed a pleasing symmetry on other side of the line beginning four rows back. People could not have seated themselves more evenly had they been posing collectively for a Rorschach ink blot.

Passing down the side aisle as swiftly as the packed throng allowed, she found three seats together in the front row, just in front of the podium where the film’s director would no doubt be speaking with in a few short minutes, when the event actually began. She sat down, spreading her coat over the seat to her left and placing her purse in the seat to her right.

The bespectacled youth in the seat beyond that glanced up from his film festival program, which listed all of the features with which a greedy theatre-goer could conceivably gorge himself over the next three weeks. In response to Alison’s query about whether the seat between them was taken, he replied somewhat cryptically, “Have you seen the new Indiana Jones film yet?”

Since it had been released only that day, she had not; she wondered how young he was, to still attach value to seeing a blockbuster a few hours before anyone else. “No — wouldn’t I have to be seeing it now?”

“I saw it,” the young man said smugly. “At ten o’clock this morning. I got up at eight so I could stand in line.”

Not a particularly scintillating story, is it? Partly, it’s because it’s a fairly accurate description of a few minutes of my evening — I’m just returned from the Seattle International Film Festival’s screening of THE BATTLE IN SEATTLE; if you guessed it was about the WTO protests, you’re the kind of reader an author may safely trust to extrapolate the extremely likely correctly — and if you guessed that this might have been the world’s most sympathetic audience for this particular story, take two gold stars out of petty cash.

But mostly, what weighs down this anecdote is the unnecessary explanation. At the risk of creating my own Rorschach pattern, here’s the same passage as a professional reader would see it, with the extraneous obvious crossed out. Just for fun, I’m going to add in bold what Millicent would be muttering under her breath as she read:

As Alison walked into the crowded movie premiere, she noticed that there were so many people there that{how could it be crowded WITHOUT a whole lot of people there?} few seats were left. She would need to move fast to grab the necessary three for herself and her two friends still parking the car in the garage{what else would they be parking — and is the reader honestly supposed to be astonished by the choice of parking venue? Where were they supposed to park, in the coat check room?, Georgette and PetuniaShe hurried, scanning the rows for empty seats.

Fortunately, this was a movie screening in {how many times do we need to be told this?} the greater Seattle area: people had seated themselves in a sort of mohawk down the middle of the theatre, in chairs {on what else would they be sitting in a theatre?} so directly under the geometric center point of the room that had some enterprising engineer dropped a plumb line from the ceiling and measured seating distribution, the exercise would have revealed a pleasing symmetry on other side of the line beginning four rows back. People could not have seated themselves more evenly had they been posing collectively for a Rorschach ink blot.

Passing down the side aisle as swiftly as the packed{If the narrative says one more time that there were a lot of people in the room, I’m going to throw my mug of coffee across the room.} throng allowed , she found three seats together in the front row, just in front of the podium where the film’s director would no doubt be speaking with in a few short minutes, when the event actually began. She sat down, {implied in what happens next, surely} spreading her coat over the seat to her left and placing her purse in the seat to her right. {Yawn. Wake me when something happens.}

Add here so we can tighten the next paragraph: “Is this seat taken?” she asked.

The bespectacled youth in the seat beyond that glanced up from his film festival program, which listeding all of the features with which a greedy theatre-goer could conceivably gorge himself over the next three weeks. In response to Alison’s query about whether the seat between them was taken, he replied somewhat cryptically, {show it being cryptic instead} “Have you seen the new Indiana Jones film yet?”

Since it had been released only that day, she had not; she wondered how young he was, to still attach value to seeing a blockbuster a few hours before anyone else. “No — wouldn’t I have to be seeing it now?”

“I saw it,” the young man said smugly. “At ten o’clock this morning.”

That’s quite a lot of omission-worthy verbiage, isn’t it? Take another gander at what Millicent wanted to cut, and it’s clear that the problems here go beyond unnecessary explanation: the edited bits slow the story considerably, are virtually conflict-free, and, taken as a group, aren’t particularly interesting. No one would miss them if they were cut, and Millicent would cry, “Hosanna!”

The omittable obvious is particularly common in dialogue — and, as is so often the case, the world of film provides some gorgeous examples for our edification.

Take, for instance, the phenomenon film critic Roger Ebert has dubbed the Seeing-Eye Man: after the crisis in an action film has ended, the male lead embraces the female lead and says, “It’s over,” as though the female might not have noticed something as minor as Godzilla’s disappearance or the cessation of gunfire or the bad guys dead at their feet. In response to this helpful statement, she nods gratefully.

Or the cringing actor who glances at the sky immediately after the best rendition of a thunderclap ever heard on film: “Is there a storm coming?”

Taken one at a time, such statements of the obvious are not necessarily teeth-grinding events — but if they happen too often over the course of the introductory pages of a submission, they can be deal-breakers for Millicent.

You’re better off cutting ALL of them — and yes, it’s worth a read-through (IN HARD COPY, anyone?) to search out every last one. Yes, even if your manuscript does not fall into this trap very often.

At the risk of sounding like the proverbial broken record: remember, you have absolutely no control over whose submission a screener will read immediately prior to yours. Even if your submission contains only one self-evident proposition over the course of the first 50 pages, if it appears on page 2 and Millicent just finished wrestling with a manuscript where the obvious is pointed out four times a page, how likely do you think it is that Millie will kindly overlook it amongst the multifarious wonders of your pages?

You’re already picturing her astonishing passersby with her wrathful comments, aren’t you? If not actually goring them with her horns.

The trouble is, virtually always, these obvious statements appear to the writer to be simple explanation. Innocuous, or even necessary. But provide too much information about a common experience or everyday object, and the line between the practical conveyance of data and explaining the self-evident can become dangerously thin.

I’ve been using bald examples so far, but let’s take a look at how subtle self-evidence might appear on a page:

The hand of the round clock on the wall clicked loudly with each passing second. Magruder ate his pie with a folk, alternating bites of overly-sweetened Ollieberry with swigs of coffee from his mug. As he ate, farmers came into the diner to eat lunch, exhausted from riding the plows that tore up the earth in neat rows for the reception of eventual seedlings. The waitress gave bills to each of them when they had finished eating, but still, Magruder’s wait went on and on.

Now, to an ordinary reader, rather than a detail-oriented professional one, there isn’t much wrong with this paragraph, is there? It conveys a rather nice sense of place and mood. But see how much of it could actually be cut by removing embroideries upon the obvious:

The round clock on the wall clicked loudly with each passing second. Magruder alternated bites of overly-sweetened Ollieberry pie with swigs of coffee. As he ate, farmers came into the diner, exhausted from tearing the earth into neat rows for the reception of eventual seedlings. Even after they had finished eating and left, Magruder’s wait went on and on.

The reduction of an 85-word paragraph to an equally effective 59-word one may not seem like a major achievement, but in a manuscript that’s running long, every cut counts. And the shorter version will make the Millicents of the world, if not happy, at least pleased to see a submission that assumes that she is intelligent enough to know that generally speaking, people eat pie with cutlery and drink fluids from receptacles.

This is one of those areas where it honestly is far easier for a reader other than the writer to catch the problem, though, so if you can line up other eyes to scan your submission before it ends up on our friend Millicent’s desk, do. And not casually, either: this requires some advance preparation.

As if all preparation weren’t in advance by definition.

Hand your first reader the biggest, thickest marking pen in your drawer, and ask her to make a great big X in the margin every time the narrative takes the time to explain that rain is wet, of all things, that a character’s watch was strapped to his wrist, of all places, or that another character applied lipstick to — wait for it — her lips.

I am now going to post this blog on my website on my computer, which is sitting on my desk. To do so, I might conceivably press buttons on my keyboard or even use my mouse for scrolling. You never can tell.

Believe me, Millicent can — trust her to do it. Keep up the good work!

Guest blogger Joel Derfner: I need permission to what?

Hello, gang –

Anne here. In writing yesterday’s post, I think I strained something while stretching to make yesterday’s analogies work. My credulity perhaps, or yours. That will teach me not to rush off and write a post the instant after I receive bad news, eh?

The timing couldn’t be better for me to take a day off, though — FAAB (Friend of Author! Author! Blog) Joel Derfner, better known to us here as witty commenter and fabulous blogger Faustus, MD has graciously written us a guest post for today.

And on a lulu of a topic I seldom address, too: getting permission to quote songs in your book.

Was that giant sucking nose I just heard your collective gasp at the realization that you might conceivably need such permission — and that obtaining it might be the author’s responsibility? Read on, MacDuff.

But first, for those of you who missed my crows of joy last week, Joel’s second book, Swish: My Quest to Became the Gayest Person Ever has just been released by Broadway Books, a division of Random House. And hoo boy, has it been garnering some enviable reviews. Lookee:

“Whether recounting his stint at New York’s cheerleading squad or the eye-opening week he spent undercover at a North Carolina “ex-gay” ministry, his inner terrain of hope and devastation is recognizable to anyone who has felt the scrutiny of peers. In one typically sidesplitting passage Derfner leads his step aerobics class, seemingly with unflappable confidence, while harboring private fantasies of boosting student morale with a tray of homemade brownies.

“‘I have these moments of insecurity quite often,’ Derfner admits. ‘If you can point to your flaws in a way that reveals them to be universal, then your flaws are not unattractive — just human.’ Whether he’s the next Noël Coward or a male Bridget Jones, one thing is clear: Queer America needs Derfner. In a culture where we disguise vulnerability with physical perfection and material success, Derfner skewers heartache with Wildean wit.” — Out.com

“These witty, fun and poignant essays knocked me on my ass more than once. I desperately want to hang out with him.” — Booksplosion!

“The ultimate swish-quest, indeed, though it makes for more than a delightfully breezy, campy read, for the humorous anecdotes morph into movingly evocative memoirs when, for instance, he recalls his liberal, civil-rights-activist parents’ response to his teenage coming out: Not At All Good. His mother never accepted it, and he and she never achieved more than an uneasy détente. Thus this superficially facile book becomes more than the sum of its parts, as Derfner indicates when he observes, ‘Writing about my quest to become the gayest person ever led me to realize I was actually on a quest to become myself.’” — Booklist

May all of our books be greeted with such delighted enthusiasm. (And make sure to let me know when they do — I love gloating over readers’ successes.) Both Swish and Joel’s hilarious first book, Gay Haiku are available on Amazon, or for those of you who prefer to deal with independent bookstores, Powell’s.

Take it away, Joel!

 

You know how you open a book and there are quotes from song lyrics all over the place? And how you figure the author just sent the manuscript in and somebody at the publishing company took care of getting permission to quote those lyrics?

You’re wrong.

I mean, you may not be wrong as far as, say, Stephen King is concerned. I don’t know. But excepting extraordinary cases the author is usually contractually obligated to get licenses for anything s/he quotes. (S/he is also contractually obligated, by the way, to pay for licenses for anything he quotes.)

Okay, I thought when I discovered this as I was finishing my book, that’s a hideous miscarriage of justice, but worse things have happened in the world. I mean, it’s not like I have to go camping or anything. It was in this frame of mind that I submitted my manuscript, which quoted lyrics from nine songs. I’d even taken the time to footnote songwriters and publication dates, just so Random House would see how diligent I was being.

But when my editor gave me his feedback, one of the things he said was, “Getting permissions can sometimes be tricky, so you might want to cut some of these. Actually, you might want to cut all of them.”

To appease him I went through the manuscript and cut as many of the lyrics as I could, replacing them with non-copyright-infringing prose references to the songs in question. Of course I knew he was worrying needlessly, but I am nothing if not accommodating (okay that’s totally a lie I’m not accommodating at all but I worry that if I don’t obey him he’ll stop giving me chocolate every time I show up at his office), so I didn’t have a problem doing this. In the end there was only one lyric I felt couldn’t be cut without doing real damage, “Without You” on pages 115-6.

THANK ^%$*ING GOD.

I tell you, I might as well have been trying to get my hands on the Hope Diamond.

At first it wasn’t so difficult. After a half hour or so with the Internet I figured out that the copyright was owned by a company (we’ll call it Company A) in Britain. My editor’s assistant called them (because I live in the ghetto and have a ghetto phone plan that would sooner let me destroy its headquarters in a rain of fire than allow me to call a country in Europe) and got the name of the guy I needed to talk to about permissions.

So far, so good.

I e-mailed the guy— I’ll call him Guy A, though over the course of time I would find many more names for him—asking him what I needed to do. He e-mailed back the next day and said I needed to get in touch with Company B, which managed Company A’s licensing in the U.S. I went to Company B’s website and put in a licensing request on their convenient licensing request page.

A week later I’d heard nothing. I was not particularly concerned; I assumed that the workings of Company B, like the workings of most companies, functioned at the speed of stalactite creation. But since I hadn’t even gotten an automated response I figured I might as well check in. “Oh, you’ll hear back a week or two from now,” said Guy B when I called.

Three weeks later I’d heard nothing. “You’ll hear back soon,” said Guy B. When I asked whether I could speak to the person in charge of licensing just in case, he said, “Okay, I’ll transfer you to Gal C.” I ended up leaving a very friendly message on Gal C’s voice mail asking her to call or e-mail me.

Two weeks later, no word.

I e-mailed Gal C again.

Nothing.

I cced Guy A at Company A asking him whether he had any suggestions. His response was, “I’m sorry, I have no ideas for you.”

Guy A can go jump in a lake, I thought.

Finally I e-mailed Gal C and cced Guy A, hoping that he was in some nebulous position of authority over her and that this move would inspire her to action. Whether because of my e-mail or not, she wrote back and asked for a few pieces of information, which I sent immediately.

I e-mailed again a month later.

And again a week and a half later.

I called again a week after that but when Guy B answered the phone he said, “We’re moving offices, so she doesn’t have a phone now.”

“Well,” I said, “can I just leave her a voice mail?”

“She doesn’t have voice mail either. Can I take a message for her?”

I left one, not believing for a moment it would do any good.

A few weeks later, I was visiting friends in Los Angeles and had the brilliant idea of actually going to the physical headquarters of Company B and asking to speak with Gal C. She wouldn’t be able to ignore me if I was standing in front of her.

So of course the office was closed. Nobody was there. At 11:00 a.m. on a Tuesday.

I e-mailed Gal C again a week later (ccing Guy A again)—oh, God, you know what? This is so incredibly tedious I can’t even bring myself to go on. Suffice it to say that I finally got permission from Gal C at Company B to use the lyrics (for $300).

Then like two months before publication I got an e-mail from my editor’s assistant saying that so-and-so in the legal department wanted to know whether this permission applied to Canada as well or just the United States. Company B said no, it was just for the U.S., and they had no idea who I should talk to for Canada. Company A said the same thing.

In the end I had to call Guy D and Gal E at Companies C and D in the U.S. (neither of them knew the answer to my question, and Gal E actually began explaining the basics of copyright law to me as if I were twelve, except she kept getting things wrong). Then I called Guys F, G, and H at Companies E, F, and G in Canada.

By this point it was too late to make any changes to the book, so all I could do was show that I was making a good-faith effort to secure permission, so I asked Gal I from Company G to have Gal J e-mail me saying that they’d received my request. Gal J did so and I forwarded the e-mail to my editor’s assistant.

To get permission to quote twelve lines of one lyric has taken me six months, countless phone calls, and probably two years of my lifespan. And $300 plus whatever Company G says I owe them.

I am never, ever, ever going to quote any copyrighted material in anything I write ever, ever again.

Addendum:

I just got an e-mail from Gal J at Company G. I have permission to use the lyrics in Canada.

Once I send them $755.

Remember that I had to pay Company B $300.

Right now I have $34.62 in my bank account.

On the one hand, I believe that Company G is much, much better at its job than Company B.

On the other hand, Company G’s superiority obviously consists not only in communicating much more responsibly but also in getting its clients much more money.

I am never, ever, ever going to quote any copyrighted material in anything I write ever, ever again.

  

Swish: My Quest to Become the Gayest Person Ever and Gay Haiku author Joel Derfner is from South Carolina, where his great-grandmother had an affair with George Gershwin. After fleeing the south as soon as he possibly could, he got a B.A. in linguistics from Harvard. A year after he graduated, his thesis on the Abkhaz language was shown to be completely wrong, as the word he had been translating as “who” turned out to be not a noun but a verb. Realizing that linguistics was not his métier, he moved to New York to get an M.F.A. in musical theater writing from the Tisch School of the Arts.

Musicals for which he has written the scores have been produced in London, New York, and various cities in between (going counterclockwise). In an attempt to become the gayest person ever, he joined Cheer New York, New York’s gay and lesbian cheerleading squad, but eventually he had to leave because he was too depressed. In desperation, he started knitting and teaching aerobics, though not at the same time. He hopes to come to a bad end.

  

R.I.P., Mr. M — and a few thoughts on marketing

My mother called me with some sad news today: Bob Mondavi, one of the grand old men of my childhood, passed away a few days ago. He was 94, so it wasn’t precisely a surprise, but while normally, the death of a nice little old man would be primarily a matter of local mourning, in this case, pretty much everyone who has ever drunk a glass of good American wine should be just a little saddened by Mr. M’s passing.

Why? Because Robert Mondavi was to a great extent responsible for Napa Valley wines becoming respectable. If you’ve ever paid more than $10 for a bottle of American wine, you might want to drink a toast to his memory.

Oh, there had been good wine coming out of the region for decades before he broke off from his family’s Charles Krug Winery to form the Robert Mondavi Winery (viticulturists are not known for their retiring egos) in the mid-1960s — in the 1890s, my great-uncle and great-grandfather won European awards for a wine grown in what is now known as the Carneros — and there were certainly much better wines being made than at RMW throughout my formative years.

Yet Mr. M was one of the first to see that it wasn’t enough just to make good wine — the world needed to know about it.

Sound familiar? This was someone who understood marketing.

How well, you ask? Well, as hometown legend has it, for years and years, it was extremely difficult for Californian winemakers to sell Sauvignon Blanc to restaurateurs. Not because it isn’t a perfectly lovely varietal — Mike Grgich, another of the grand old men of my childhood (perhaps even grander because he liked to sport a rakish beret year-round), has been making one of the best liquids to accompany fish available on earth since I was in pigtails — but because, I kid you not, people weren’t sure how to pronounce Sauvignon.

So they felt uncomfortable trying to say it out loud in front of a waiter.

How did Mr. M handle it, you ask? By changing the name of the wine.

Seriously — RMW was the first to release Sauvignon Blanc under the much easier-to-pronounce moniker Fumé Blanc. The switch was so successful that within a few years, one of the easiest ways to tell if the would-be snob across the table from one on a date knew a grape from a raisin was if he insisted that Fumé Blanc was actually the name of the grape.

Which it isn’t — and couldn’t be, as both of the words in question are adjectives: Sauvignon is the varietal, and thus a noun, but fumé means smokedblanc means white. By a certain stretch of tastebud definition, a Sauvignon Blanc could be said to have some rather smoky undertones.

But really, what people started ordering in restaurants was a kippered pale thing — which could refer, logically, to anything from a cigarette to sole. But heavens, does it roll off the tongue!

In latter days, like so many family wineries, RMW became the possession of a corporation while retaining the our-kids-and-grandkids-work-here façade. The old winemaking names stick to the the buildings and land long after the flesh-and-blood people who bore those names are long gone. (Which is why, in case you were curious, there’s hasn’t been a Chuck making Two-Buck Chuck for quite some time now.) To outsiders, the Mondavi name, like so many others, is just another brand.

But it was a sad day for a lot of locals when the Mondavis left the Robert Mondavi Winery, the end of an era of winemakers who still remembered having to fight the stigma that used to attach to any American wine.

Mr. M founded RMW the year I was born, and I was graduating from middle school before people stopped laughing at the phrase Californian fine wine. Those grapes have come a long way, baby.

So goodbye, Mr. M. The winemaking — yes, and the wine-drinking — world is poorer for your loss. I hope the angels pulled up something grand from the cellar in honor of your arrival.

And yes, Virginia, I am going to tie all this into advice on your writing career. Just watch me.

How? Well, like it or not, querying is marketing.

A writer has only a very, very short amount of time to grab an agent’s attention in a query letter or a pitch, especially in an e-mailed query. It’s imperative, therefore, to label your book correctly — and that means learning to define it in the terms used by the industry.

Yes, I AM talking about book categories.

Stop groaning, long-time readers — judging by the average query letter, many writers simply don’t know that the industry runs on book categories.

But think of it from the other side of the desk. It would be literally impossible for an agent to sell a book to a publisher without a category label — in an agent’s pitch, it’s usually mentioned before either the title or the premise. And since no agency represents every kind of book, or even every kind of novel, category is the typically the first thing an agency screener is trained to spot in a query.

Knowing that, think about Millicent’s mood immediately after she’s burnt her lip on that latte: how likely is she to feel charitable toward a query that makes her search for the category or — sacre bleu! — guess it?

Some writers, bless their warm, fuzzy, and devious hearts, think that they are being clever by omitting the book type, lest their work be rejected on category grounds. “This agency doesn’t represent mysteries,” this type of strategizer thinks, “so I just won’t tell them until they’ve fallen in love with my writing.”

I have a shocking bit of news for you, Napoléon: the industry simply doesn’t work that way. If Millicent does not know where the book mentioned will eventually rest on a shelf in Barnes & Noble, she’s not going to ask to read it.

Do I see some raised hands out there? You, in the front row: “But Anne, not all books, particularly novels, fall into obvious categories! What if I’m genuinely not sure?”

Good question, You. Yes, for most books, particularly novels, there can be legitimate debate about which shelf would most happily house it, and agents recategorize their clients’ work all the time. However, people in the industry speak and even think of books by category, so you’re not going to win any Brownie points with them by making them guess what kind of book you’re trying to get them to read.

Part of learning to market your writing well involves developing the skills to describe it in terms the industry will understand. When in doubt, pick the category that coincides with what the agency (or, better still, particular agent to whom you are addressing your query letter) represents.

If you found the last paragraph mystifying, please see the posts under the BOOK CATEGORIES heading at right. Scroll down until you find the entries on how to decide which is for you, and study it as if it were the Rosetta Stone.

In a sense, it is: book categories provide terms of translation between the often mutually incomprehensible conceptions of manuscripts held by their authors and the people they are asking to represent them.

Think of your query letter as a label for the bottle of wine you’re trying to sell.

Stop laughing; it’s not all that far-fetched a comparison. Just as a wine connoisseur expects the label to tell her what kind of grapes were used to produce the bottle she’s considering serving with her dinner, to try to figure out if it’s the kind of wine she tends to like, Millicent and her ilk want a query letter or pitch to inform them up front what kind of a book the querier is offering.

That’s not so unreasonable, is it?

Or, better yet, think of it as a personal ad. (Oh, come on, admit it: everyone reads them from time to time, if only to see what the new kink du jour is.) In it, you are introducing yourself to someone with whom you are hoping to have a long-term relationship — which, ideally, it will be; I have close relatives with whom I have less frequent and less cordial contact than with my agent — and as such, you are trying to make a good impression.

So which do you think is more likely to draw a total stranger to you, ambiguity or specificity in how you describe yourself?

This is a serious question. Look at your query letter and ponder: have you, as so many personal ads and queries do, been describing yourself in only the vaguest terms, hoping that Mr. or Ms. Right will read your mind correctly and pick yours out of the crowd of ads? Or have you figured out precisely what it is you want from a potential partner, as well as what you have to give in return, and spelled it out?

To the eye of an agent or screener who sees hundreds of these appeals per week, writers who do not specify book categories are like personal ad placers who forget to list minor points like their genders or sexual orientation.

Yes, it really is that basic, in Millicent’s world.

And writers who hedge their bets by describing their books in hybrid terms, as in “it’s a cross between a political thriller and a historical romance, with helpful gardening tips thrown in,” are to professional eyes the equivalent of personal ad placers so insecure about their own appeal that they say they are into, “long walks on the beach, javelin throwing, or whatever.”

Not very effective marketing, is it? Other than provoking idle speculation about precisely what kinds of activities would logically fall into the whatever category, appealing to both the beach-walker and the javelin-thrower, labeling this vague just isn’t all that intriguing.

Trust me, to the eyes of the publishing industry, this particular type of complexity doesn’t make a writer look interesting, or a book like an innovative genre-crosser. To them, this at best looks like an attempt to curry favor by indicating that the writer in question is willing to manhandle his book in order to make it anything the agent wants.

At worst, it comes across as the writer’s being so solipsistic that he assumes that it’s the query-reader’s job to guess what “whatever” means in this context.

Again: just how cordially do you think Millicent is going to respond to an invitation to play a guessing game with a total stranger? And don’t you want to know before you order a glass of wine whether it’s a white or a red?

Be specific, and describe your work in the language Millicent will understand. Because otherwise, you run the risk that she’s just not going to understand the book you are offering well enough to know that any agent in her right mind should be grateful to read it.

And please, don’t allow a handful of rejections to convince you that you don’t have a marketable book. Remember, there was a time that wine sellers laughed whenever anyone said that good wine was being produced in the Napa Valley.

Ask the shade of Bob Mondavi: it took a whole lot of convincing — yes, and giving away a whole lot of sample tastes — to establish the region’s reputation to the point that a Napa Valley wine meant something specific in the potential buyer’s mind. About fifteen years’ worth, in fact.

Not a bad parallel for an established author’s quest to market her latest work vs. a first-time writer’s, eh?

Stop giggling; it’s true. If the potential buyer is already familiar with a winery’s reputation, it’s far easier to cajole him into taking a chance on its most recent vintage than if he’s never heard of it. It might take some persistent marketing to convince him to taste what’s in the bottle and judge for himself whether the wine’s any good.

Think about it: whose book are you more likely to pick up in a bookstore, a brand-new author’s first book or the latest from an author you’ve been reading for years? And how likely are you to look for a thriller in the romance section of the bookstore?

Label your work well. You want Millicent to ask to taste what’s in the bottle, don’t you?

Next time, I’ll get back to craft issues. Keep up the good work!

Is that a plot flare I see before me, or did a line of text just spontaneously combust?

Over the past couple of posts, as I was making the case for setting up necessary character plot development well before it is needed to explain what’s going in a particular scene — or, heaven help us, the climax of the book — I made passing reference to what I like to call Plot Flares, an early screaming indication that something specific is going to happen later in the story.

Except, I now notice, I never managed to call them by name — so much for my clever plan to refer back to the concept a week or two hence, eh? And now that it occurs to me to check, I realize that I haven’t actually written a post on Plot Flares since sometime in 2006.

This is one of the dangers of blogging so much, you know: the archives start to blur in the blogger’s mind. I’ll be writing along, minding my own business, when all at once a side issue pops to mind. “Oh, I don’t need to attend to that now,” I mutter to myself, resolutely pushing it to the back of my mind for another year. “I blogged about that only a couple of months ago.”

Except it will turn out to have been a couple of years ago. So if I start throwing around terminology more recent readers don’t recall, please don’t hesitate to ask what the heck I’m talking about, okay?

So: plot flares. Once again, this is a phenomenon familiar to all of us from movies: the eventual startling plot twist is revealed in some small way within the first twenty minutes. If the heroine is going to have to shoot the villain at the climax as her Own True Love lies bleeding and weapon-free, for instance, she will almost invariably make a statement about her (a) loathing for guns, (b) aversion to violence, and/or (c) having witnessed some incredibly graphic murder during her formative years during the first act.

Ostensibly so we poor viewers can understand why anyone might have an aversion to, say, picking up a gun and shooting someone in cold blood or some other hard-to-grasp concept like that.

In novels, creative nonfiction, and memoirs, foreshadowing of the denouement often happens within the first 50 pages — or even the first chapter. Heck, it’s not all that uncommon for an actual SCENE of the climax to open the book as a prologue, with the plot jumping backward in time immediately thereafter to figure out how our hero ended up there.

Or, to put it in cinematic terms: “Rosebud.”

From the author’s POV, these hints are generally subtle, mild foreshadowing of events to come. As character development and background, small hints are often advisable, or even unavoidable. If these hints aren’t AWFULLY subtle, though, they can give away the rest of the book, deflating suspense as surely as helium comes out of a balloon when you jab a needle into it.

And to professional readers, who see every plot twist in the book, so to speak, on a literally daily basis, a poorly-done foreshadowing hint glows in the middle of a page like a flare set up around a midnight highway accident: don’t go there.

There are, of course, the classics common to both the silver screen and the printed page: if the female lead faints or mentions putting on weight, she’s going to turn out to be pregnant; if any man announces that he’s counting the days until retirement, he’s going to be killed (and, heaven help us, “Danny Boy” will be played on the soundtrack); if our hero is a sad guy, he will inevitably turn out to have had a beautiful (and often, in the flashback, silent) wife and possibly cherubic child who were slaughtered before his eyes while he watched, helpless.

Pathos, pathos.

And it’s not just lowbrow entertainment that embraces this strategy. These clichés transcend genre or even writing quality: that last example about the dead wife and child was the backstory for both half the action films Charles Bronson ever made and the Sidney Poitier character in GUESS WHO’S COMING TO DINNER (courtesy of a car crash), as well as for the Antonio Banderas character in ONCE UPON A TIME IN MEXICO (courtesy of Bad Men with Guns). It gets around.

The list of such common plot flares is practically endless. In a television detective story, the actor with the best résumé (who therefore cost more than the other players) will turn out to be the murderer; so will Ray Liotta, John Malkevich, Ice-T, and/or Christopher Walken — unless, of course, the directors have elected to incorporate what I like to call the Liotta Lapse, where they use an actor so habitually typecast as the guy you’re SUPPOSED to think did it, so the twist can be that someone else did.

Actually, I’ve always found it rather amusing that people in the movie industry continue to think that we’re all surprised by plot twists set up three miles in advance — in manuscripts, these cliché set-ups tend to be dismissed in the first read-through. I once attended a memorable preview of a forgettable thriller where one of the actors, unfortunately, had shown up to speak to the audience. A fairly well-known TV actor, he swore up and down that the first time he had read the script, he was stunned by the eventual plot twist.

When several audience members laughed uproariously (including, I’ll admit it, your humble narrator), the actor was unwise enough to ask us why. I spoke up: “Because ten minutes into the film, someone mentioned that the guy who turned out to be the murderer ‘had a tough childhood.’ The screenwriter might as well have erected a road sign with a big arrow that read ‘psychopath here.'”

The actor looked at me as if I had just spontaneously derived the theory of relativity from scratch on the spot. “I didn’t catch that,” he claimed, straight-faced.

Now, because I prefer for the sake of the republic to assume that most adults are reasonably intelligent, I assume the actor was lying about his own perceptions in order to protect his film from the all-too-deserved charge of predictability. For such a cause, I can cut him some slack.

However, in book form, agents, editors, and contest judges tend not to cut the author of a manuscript any slack at all. Remember, these are not charitable readers, as a rule, but business-oriented ones. They’re looking for plot twists that are genuinely surprising, not set up by plot flares a hundred pages in advance.

And that’s a problem, because most aspiring writers just LOVE foreshadowing.

Keep your foreshadowing, when you use it, SUBTLE — which means, of course, that unless you’re writing comedy, you might want to avoid having characters say of your politician protagonist in early childhood scenes, “That Harry! Some day, he’s going to be president.”

Um, can anyone out there give me even one good reason that a professional reader like me SHOULDN’T regard this as a glaring instance of telling, rather than showing?

Because it is, to my eye: the author has chosen to tell the reader point-blank that Harry has the qualities that would lead one to expect him to be president, rather than showing him exhibiting the individual characteristics through action.

Ultimately, that’s often the writerly motivation for inserting plot flares, I think: the author doesn’t trust that the reader is going to be able to figure out the irony…or the pathos, or the twist to come. Instead, try letting the circumstances lead naturally to dramatically satisfying conflicts and resolutions, rather than sending up plot flares every few pages to make sure that the reader is following along with the point.

As a writer, I have to assume that every one of my potential readers is as sharp as I am at picking up those clues. Admittedly, I was the person in the theatre who whispered to my date fifteen minutes into THE SIXTH SENSE, “Why aren’t any of the adults consulting with Bruce Willis about the kid’s case? Totally unrealistic, either in the school system or with the parent. He’s gotta be a ghost,” so we’re talking a rather high bar here, but I like plot twists that make readers gasp ALOUD.

If the reader’s been alerted by a flare, that gasp is never going to come, no matter how beautifully the revelation scene is set up. At most, the reader will have a satisfied sense of having figured the twist out in advance.

Keep it subtle, my friends. If there’s a cat in that bag, keep it there until it’s startling for it to pop out. There’s no need to have it meowing all the time first.

Keep up the good work!

PS to those of you currently residing in California: FAAB Joel Derfner is going to be giving readings from his new book, SWISH, in the week to come. If you live in the LA or San Francisco areas, drop by and say hi. Because, really, the primary reason for anyone to go to an author reading is to talk about ME, right?

Seriously, Joel has a lot of interesting things to say about the publication process, so this would be a tremendous opportunity to ask questions not only about how to become the gayest person ever, but about writerly concerns.

Monday, May 19, 7:30-9:00 pm — West Hollywood, CA
A Different Light, 8853 Santa Monica Boulevard

Tuesday, May 20, 7:30-9:00 pm — Long Beach, CA
Barnes & Noble, 6326 East Pacific Coast Highway

Thursday, May 22, 7:30-9:00 pm — San Francisco, CA
Books, Inc. in the Castro, 2275 Market Street

So we beat on, boats against the current, borne back ceaselessly into the past

  

Yes, Fitzgerald fans, you have guessed correctly: today, we shall be delving into the wonderful world of the flashback, with special emphasis on avoiding redundancy. Sounds like a good time, eh?

Before the screen begins to go wavy, kudos to reader Sharon for reminding me yesterday that there are in fact cliché-finding programs, as well as websites that will tell you if a particular phrase is (or is close to) a cliché. I tend to downplay the usefulness of such tools, out of fear that they will tempt writers to use them as a substitute for — chant it with me now, everybody — reading a manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD before submitting it to anyone even vaguely affiliated with the publishing industry.

See how hypnotic repetition can be?

Implemented judiciously, though, cliché-spotting programs can be very helpful indeed, particularly for writers who are not native English speakers or native speakers who do not happen to have grown up in Manhattan or LA. Or at any rate, not in a TV studio, sound stage, or publishing house in either.

As if that weren’t enough help in the self-editing department for one post, public-spirited long-time reader Chris Park, he of the impressive PC skills, has been kind enough to cobble together a shareware program for writers, specifically intended to catch repetition in a text. It’s called Manuscript Analyzer, straightforwardly enough, and because Chris is a generous guy, you may download it for free from his website.

Chris, I am delighted to report, will also have an excerpt from his latest novel, ALDEN RIDGE, used as an example of fine storytelling in Chris Roerden’s soon-to-be-released book on, you guessed it, self-editing, DON’T SABOTAGE YOUR SUBMISSION. Congratulations to Chris — and to Chris, too, while we’re at it!

Okay, now the screen may begin to go wavy.

In my last installment on self-editing, I went to town on the twin dangers of factual redundancy intended to remind readers of salient points (“As I mentioned back in Ch. 2, Maude, I stand to inherit a hefty chunk of change when my Uncle Mortimer dies.”) and screen clichés that have made their way into real life and vice versa (“Say ‘ah,'” kindly Dr. Whitehairedman told the child.). As I pointed out, both species are problematic in submissions, because they are so common.

Translation: professional readers get really, really tired of seeing examples of them. (And your garden-variety cliché-finder program is only going to catch the latter, please note.) But both types of repetition also tend to be, I am happy to report, some of the easiest sentences to cut.

And if you’re like so many aspiring writers in the current market — you know, the ones who clutched their hearts instinctively the first time they heard that a first novel over 100,000 words (estimated — and if you don’t know how to do that, please see the WORD COUNT category at right) is much, much harder for an agent to sell than one that, well, isn’t — this should be very good news indeed.

Because, contrary to popular belief, trimming a manuscript need not necessarily involve cutting entire scenes. Believe it or not, it can be done line by line.

Yes, really. Seriously, I’ve cut 50 pages out of a 400-page manuscript this way.

Redundant lines can often be trimmed wholesale, with no cost to the text at all. And clichés, like pop culture references and jokes that don’t quite work, are often digressions in a scene or dialogue, rather than integral to it. Much of the time, they can be deleted without adding any additional writing.

Which is a pretty good indicator all by itself that a line should be cut anyway, actually: if you wouldn’t miss it if it were gone, it should probably go.

Take, for instance, the following piece of purple prose, full of sentences just begging to hop into the tumbrel and ride to the guillotine. As you read, try to figure out how much could be cut without harming the relationships or plot of the scene:

Marcus Aurelius paced the room, frowning, revisiting in his mind his last encounter with Cardinal Richelieu, two months before, when they had shot those rapids together in the yet-to-be-discovered territory of Colorado. Despite moments of undeniable passion, they had not parted friends. The powerful holy man was known for his cruelty, but surely, this time, he would not hold a grudge. “Can I bum a cigarette?” Marcus asked, to buy more time to recap the plot in his head.

Richelieu laughed brutally, but with an undertone of affection. “Tobacco had not come to Europe in your time.” He shook two out of the pack and stuck both into his mouth. “And barely in mine.”

He lit the pair and handed both to his erstwhile lover. They sat in silence for a moment, the smoke winding its way around the cardinal’s red hat and through the halo of St. Jerome, who was standing nearby.

Finally, Marcus Aurelius decided he could take this brutal wordlessness no longer. “I’ve come for some information, Armand.”

Richelieu’s hand tightened on his sawed-off shotgun. “You’re wasting your time.”

“I’m not leaving until you tell me what I need to know.”

“It might,” St. Jerome suggested gently, “go a little faster if you were more specific.”

“Yes, do come to the point.” Richelieu waved a bejeweled hand toward his wall-sized TV screen. “American Idol is on in an hour.”

Tell me, how much cutting did you manage to do?

Other than the obvious, that is — as a major Stoic, Marcus Aurelius clearly would not have folded so quickly under the pressure, and the suggestion that he would might conceivably pull a well-read reader out of the story; I give you that. But even ignoring the philosophical problems and the time travel that seems to have happened here, there’s room for some fairly painless trimming that would speed up the scene:

Marcus Aurelius paced the room, frowning. The powerful holy man before him was known for his cruelty, but surely, he could not still be holding a grudge about how they’d parted in Colorado. “Please tell me, Armand. For old times’ sake.”

Richelieu laughed brutally, but with an undertone of affection. The smoke from his cigarette wound its way around his red hat and through the halo of St. Jerome, who was standing nearby.

“It might,” St. Jerome suggested gently, “be helpful if you were more specific about what you wanted.”

“Yes, do come to the point.” Richelieu lifted a bejeweled hand from his sawed-off shotgun to wave languidly toward his wall-sized TV screen. “American Idol is on in an hour.”

That’s 123 words, down from 231, a substantial cut obtained through the simple expedient of removing the movie clichés (the double cigarette bit is straight out of the Bette Davis vehicle NOW, VOYAGER) and unnecessary repetition.

Do I see some hands in the air out there? “But Anne,” I hear some of you ask, and rightly so, “was it really safe to cut that much? How did you know, for instance, within the context of an isolated excerpt, that the references to the Colorado scene probably referred to something that happened earlier in the book?”

Call it well-honed editorial instinct: this kind of micro-flashback almost invariably recaps a scene told more fully elsewhere — and when it isn’t shown at some point in the book, it probably should be.

Seem paradoxical? It isn’t.

A micro-flashback usually provides one or more characters’ motivation(s) in the scene occurring at the moment: here, the earlier romantic interlude has set the stage for Marcus’ belief that Richelieu would do him a favor, as well as Richelieu’s current attitude toward Marcus.

Clearly, then, this past episode is important enough to the development of both characters that the reader would benefit from seeing it in its entirety.

Which makes removing the micro-flashback from this scene an easy editorial call. To work as character development — as explanatory asides that deal with motivation must, right? — the reader really should have this information prior to the scene. Like a joke explained after it is told, character development presented as explanation of what someone has just done tends to be substantially less effective than presenting the relevant info earlier in the book, than allowing the reader to recall it at the proper moment.

Makes the reader feel smart, that does.

Think about it: a reader’s understanding of a complex character (or situation, for that matter) doesn’t really need to come in a single lump, does it? Isn’t the reader likely to develop a deeper sense of who the person is if the puzzle pieces are revealed in small shown-not-told increments?

By this logic, the micro-flashback should be cut — or at any rate minimized. If the Colorado rapids scene did happen earlier in the book, the micro-flashback here would be redundant; if it did not, the micro-flashback is not memorable enough in itself to make a lasting impression upon the reader to deserve retaining.

In other words: snip, snip.

Long-time readers of this blog, chant it with me now: emotionally important scenes are almost always more powerful if they are SHOWN as fully-realized scenes, rather than merely summarized. (Oh, come on — you DON’T want to know what happened on those rapids?)

Keep an eye out for those micro-flashbacks, my friends: they’re often flares telling the editor what needs to be done to improve the manuscript. As we saw yesterday, they are often little editors, jumping up and down in the text, shouting at the tops of their tiny lungs, “Show, don’t tell!”

In this case, the cut can only help: by removing the explanatory summary here, the author will need to make sure that the earlier scene made enough of an impression upon the reader that she will remember it by the time Marcus Aurelius comes looking for information.

Yes, even if that means going back and writing the earlier scene from scratch. Sometimes, adding a fresh scene is actually a quicker and easier fix for a manuscript that drags than merely trimming the existing text.

The metaphor that I like to use for this kind of revision comes from flower arranging, believe it or not. Everyone seated comfortably? Here goes:

Think of your draft as a wonderfully immense bouquet, stocked with handfuls of flowers you have been gathering over the last couple of years. It’s lovely, but after it has been rejected a few dozen times, you’ve come to realize that maybe the bouquet is too big for the room in which the agent of your dreams wants to place it; it does not fit comfortably into the only vase she has.

So you need to trim it — but how? A good place to start would be with the most common flower. Pull out half of the daisies; a few are nice, but handfuls make the daisy point a bit more often than necessary.

Where to begin? How about with your favorite phraseology and sentiments?

If I were editing Scott Fitzgerald’s work, for instance, I might scan first for beautiful-but-misunderstood heroines staring into nearby mirrors and moaning things like, “I’m so beautiful — why can’t I be happy?” It’s sort of an interesting statement the first time one reads it (if only to provoke the question, “Would any real woman actually SAY that?”), but it occurs something like 17 times throughout his collected short stories.

This is what the literary criticism people call a trope; professional readers call it by a harsher name: redundancy.

Either way, I’m thinking that 16 of Fitzgerald’s iterations could go. Back to our bouquet metaphor.

You could start searching for the flowers that have wilted a little, or are not opening as well as others. Pulling out the wilted flowers renders the bouquet both smaller and prettier — and the ones that wilt the fastest are the ones that are borrowed from other sources, like movie tropes, which tend to date a book, anyway.

Already, your bouquet is looking lighter, more vibrant, but you liked the color that some of the discarded flowers added. Rather than pulling the cast-off blooms out of the compost bin and putting them back into the vase (as most self-editors will do), adding a fresh flower here and there is often more beneficial to the overall beauty of the bouquet.

So be open to the possibility that trimming your manuscript may well mean writing a fresh scene or two, for clarification or character development. Search your manuscript for micro-flashbacks that may be telling you what needs further elucidation.

If you apply a truly diligent eye, you may well find that a single, well-developed past scene inserted early on will replace scores of micro-flashbacks down the line.

It happens. All the time, in fact.

Like a good joke, motivation goes over better with the reader if it can be presented cleanly, without excess in-the-moment explanation. Bear that in mind as you revise, and keep up the good work!

Writing with teeth…or at least with gums

The beast prior to the procedure

I meant to post yesterday, honest I did, but I couldn’t drag myself to the computer because of an overwhelming sense of guilt. Remember that shelter kitty we adopted last fall, to keep me company while I was lolling on the couch with mono? The one with the past that would make Charles Bukowski turn pale? Well, it turns out that he (the kitty, not Bukowski) had a set of teeth that imply that he spent his kittenhood ingesting crystal meth on a daily basis.

We’re relatively sure that he didn’t, but pretty much all of his front teeth had to go anyway. Thus my Friday o’ Guilt.

Actually, the kitty seems to be taking it all better than I am on this suddenly summer-like spring day:
he’s raring to go; I’m walking around apologizing to him every fifteen minutes.

Oh, no: I inadvertently used the evil phrase, the one involved in my first A CLOCKWORK ORANGE-like aversion therapy for repetitive phrase use. Pardon me, everybody…my vision is going wavy…

I was six years old, standing in line for the Peter Pan ride at Disneyland, back in the days when the quality and popularity of the ride was easily discernable by the level of ticket required to board it. E was the best; I believe this particular ride was somewhere in the B range.

So there I was, all eyes and braids, holding my mother’s hand while my father watched my older brother go on D and E ticket rides, waiting in a queue of inexplicable length to cruise around an ersatz London with Peter, Wendy, and the gang. As each ship-shaped (literally) car took a new crew of tourists into the ride itself, Peter’s voice cried out, “Come on, everybody, raring to go-o-o-o!”

Three feet forward. “Come on, everybody, raring to go-o-o-o!”

Six more feet. “Come on, everybody, raring to go-o-o-o!”

Tears have by now come to my mother’s eyes, but we’re too committed to the line to back out now. “Come on, everybody, raring to go-o-o-o!”

After about five minutes of listening to that annoying voice while inching toward the front of line, I started counting the repetitions. By the time it was our turn to step into the flying ship, Peter had barked that inane phrase at me 103 times. It’s all I remember about the ride.

And that, my friends, is how one grows up to be an editor: howling, “Oh, God, not that same phrase AGAIN!”

Yes, I know: I’ve used this example before here, but I don’t think most writers have any idea just how much word, phrase, and even concept repetition grates on professional readers and contest judges. Fingernails on a chalkboard doesn’t even begin to describe it.

But it makes the average pro want to hide under the bed like a cat threatened with a visit to the vet — and, since folks like me are trained specifically to catch redundancies a hundred pages apart, even a single repetition can sometimes send us diving bedward.

Did some of you out there just go pale? Are you perhaps thinking of my last post, where I mentioned that readers do not necessarily remember every detail about every character?

Good; that means you’ve been paying attention.

For those of you whose blood pressure remained normal, let me disturb it: character trait redundancy is really, really common in submissions. Why? Well, for precisely the reason cited above — fearing that readers may not recall important plot points or characteristics, many aspiring writers repeat such information throughout the book.

How common is this practice? Well, let’s just say that most of us who read for a living (and, I suspect, for most who review movies for a living as well) see the second instance and say immediately, “Oh, okay — THAT fact is going to be crucial to the climax.”

The best way to avoid engendering this reaction, as I suggested last time, is to introduce the relevant facts or characteristics in such a vivid way the first time around — showing them, perhaps, instead of simply telling the reader about them — that the reader may be safely trusted to recall 300 pages hence that the protagonist’s sister is allergic to the beets that are going to kill her on p. 423.

Gee, who saw THAT coming?

Did that sudden stabbing sensation in my back mean that some of you found that last observation a trifle harsh? “But Anne,” the repetition-fond point out, “readers honestly do forget details — my first reader/writing group/my agent/my editor keeps writing in the margin, ‘Who is this?’ when I reintroduce characters toward the end of the book, or even, ‘Whoa — this came out of nowhere!’ when I’d thought I’d laid the groundwork in the first third of the book. I’m just adding the repetition to address these concerns, because, frankly, unless the reader has that information, the conflict loses some of its oomph.”

You could do that, repetition-mongers, but I would translate this feedback differently: if your first readers are not recalling certain salient facts introduced early in the book by the time they reach the closing chapters, isn’t it possible that the earlier introduction is at fault?

My first response would be to rush back to the first mention of the information in question to see if it is presented in a memorable manner. Or if, as we discussed last time, the reader is presented with so much information that the important bits got buried.

Actually, it wouldn’t be a terrible idea to go back and double-check anytime you notice yourself repeating information. Is there a reason that you’re assuming that the reader won’t remember it if it’s mentioned only once?

This strategy will only work, however, if the writer catches the repetition — say, in the course of reading her manuscript IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD before submitting it to an agent, editor, or contest.

I’ve noticed that writers are very frequently unaware of just how much their manuscripts DO repeat themselves. There’s a very good reason for that, of course: repetition is constantly flung at all of us, all the time.

Not just in everyday conversations — although it’s there, too: if you doubt this, go find a community that’s experiencing a heat wave, sit in a popular café, and count the variations on, “Hot enough for ya?” you hear within a 15-minute period — but in TV and movies as well.

Most of us become inured through years of, well, repetition to the film habit of repeating facts and lines that the screenwriter wants to make sure the viewer remembers, information integral to either the plot (“Remember, Gladys — cut the RED cord hanging from that bomb, not the yellow one!”), character development (“Just because you’re a particle physicist with a summa cum laude from MIT, George, doesn’t mean you’re always right!”), or both (“You may be the best antiques appraiser in the British Isles, Mr. Lovejoy, but you are a cad!”)

My favorite example of this tendency is the cult TV series Strangers With Candy, a parody of those 1970s Afterschool Special designed to break the news to young folks like me that Divorce is Hard on Everyone in the Family, Outsiders are Teased, and Drugs are Bad. (See, I even remembered the morals, doubtless due to repetition.)

Because it’s not as though we could be trusted to draw conclusions like that for ourselves from real-world observation. Because these playlets were intended to be EDUCATIONAL (as opposed to, say, entertaining), Afterschool Specials tended to hammer home their points with SUBTLE TOUCHES OF IRONY on the order of some minor character’s saying to our tragic heroine (played by someone like Helen Hunt in braces), “You know, Esther, I don’t think that you should even consider taking those drugs. They might make you go CRAZY.”

Any sane viewer, naturally, would recognize that this would mean that Helen Hunt was going to (a) take those drugs, because where would our object lesson be otherwise? (b) in fact go crazy, and (c) probably be dead within the next ten minutes of screen time.

Strangers With Candy had a great deal of fun with this kind of foreshadowing: the heroine, Jerri Blank, often telegraphs upcoming plot twists by saying things like, “I would just like to reiterate, Shelly, that I would just die if anything happened to you.”

Moments later, of course, Shelly is toast.

It’s funny in the series, but it’s less funny to encounter in a manuscript, particularly if your eyes are attuned to catching repetition, as most professional readers’ are. Characters honestly do say things like, “But Emily, have you forgotten that I learned how to tie sailors’ knots when I was kidnapped by pirates three years ago?”

All the bloody time. Even when the first 200 pages of the manuscript dealt with that very pirate kidnapping.

At base, this is a trust issue. The writer worries that the reader will not remember a salient fact crucial to the scene at hand, just as the screenwriter worries that the audience member might have gone off to the concession stand at the precise moment when the murderer first revealed that he had a lousy childhood.

Who could have predicted THAT?

I’m sensing some squirming in desk chairs out there. “But Anne,” I hear some consistency-mongers protest, “doesn’t the fact that we ARE all accustomed to being spoon-fed the information we need when we need it mean that we writers should be ASSUMING that our readers will have some memory problems? Especially someone like Millicent, who might read the first 50 pages of my novel, request the rest, then continue reading a month or two later? Surely, I should be including some reminders for her, right?”

Good question, squirmers. Television and movies have most assuredly affected the way writers tell stories. One of the surest signs that a catch phrase or particular type of plot twist has passed into the cultural lexicon is indeed the frequency with which it turns up in manuscript submissions.

For precisely the same reason, one of the best ways to assure a submission’s rejection is for it to read just like half the submissions that came through the door that day.

“But WHY?” the consistency-huggers persist.

Come closer, and I’ll tell you a secret: repetition is boring. REALLY boring.

We all know how agents and editors feel about manuscripts that bore them, right? In a word: next!

And here’s another secret: people who read manuscripts for a living are substantially more likely to notice repetition than other readers, not less. (Perhaps Peter Pan traumatized them in their younger days, too.) Not only repetition within your manuscript, but repetition ACROSS manuscripts as well.

Let me ask you: just how much control does the average submitting writer have over the OTHER manuscripts Millicent might have already scanned that day?

That’s right: absolutely none. So while following the cultural norm for repetitive storytelling might not annoy a reader who curls up in a comfy chair with only your manuscript, if your tale repeats twice something similar to what the submission before yours saw fit to convey 37 times in 22 pages…

It may not be a problem to which your manuscript falls prey — and if so, hurrah for you; it’s hard to strip a manuscript of them entirely, because they are so pervasive. But just to be on the safe side, here’s a project for a rainy day: sit down with your first 50 pages and highlight every line of dialogue in there that you’ve ever heard a TV or movie character say verbatim.

Ever.

Was that giant slurping noise I just heard the sound of the blood rushing out of everyone’s faces at the realization of just how much dialogue that might potentially cover?

No? What if I also ask you to highlight similar phrases in the narration? First-person narration is notorious for echoing the currently popular TV shows.

Often, it’s unconscious on the writer’s part: it’s brainwashing from all of that repetition. It would be surprising if common dialogue HADN’T made its way into all of our psyches, actually: according to CASSELL’S MOVIE QUOTATIONS, the line, “Let’s get outta here!” is in 81% of films released in the US between 1938 and 1985.

Care to take a wild guess at just how often some permutation of that line turns up in submissions to agencies?

No? Well, care to take a wild guess at how many agents and editors notice a particular phrase the second time it turns up in a text? Or the second time it’s turned up in a submission this week?

“Come on, everybody, raring to go-o-o-o!”

Unfortunately, just because a writer doesn’t realize that he’s doing lifting lines doesn’t mean that an agency screener won’t notice and be annoyed by it. Particularly if three of the manuscripts she’s seen today have used the same line.

It happens. Or, to put it in Afterschool Special terms, Checking for Both Types of Repetition is Good.

I know, I know, it’s tempting to assume that you haven’t used any of the standard catchphrases or plot twists, but believe me, even the most innovative writers do it inadvertently from time to time.

The rest of the population is subjected to the same repetitive teleplays and screenplays as writers are. Over time, people do tend to start to speak the way they would if they were playing themselves onscreen. A writer of very good hardboiled mysteries told me that he is constantly meeting private detectives who sound like Sam Spade, for instance, something they apparently didn’t do before the 1930s.

But remember, just because people do or say something in real life doesn’t mean it will necessarily be interesting — or not come across as hackneyed — translated to the printed page.

Check. Weed out both repetition within your manuscript AND material unconsciously borrowed from TV and movies.

Or, better yet, have a good reader you trust check for you. (And if you’re not sure whether a particular twist or line is common enough to count, film critic Roger Ebert is kind enough to maintains a database of them.)

Often, it’s surprising how small a textual change will turn an incipient cliché into a genuinely original moment. But a writer cannot perform that magic trick without first identifying where it should be applied.

It’s time for me to go-o-o (curse you, Pan!) for today; I’ve got some cat appeasement to do. (I wonder if he’d like a salmon milkshake…). More tips on catching repetition follow anon.

Keep up the good work!

The hows and whys of showing, not telling, or, when it pays to get just a trifle graphic

Before I launch into today’s disquisition on the ins and outs of showing, rather than telling, an announcement for those of you within driving distance of San Francisco: author, blogger, and FAAB (Friend of Author! Author! Blog) Mark Pritchard will be giving a reading in the City by the Bay this coming Saturday, May 17. For those of you not already familiar with Mark’s Too Beautiful blog might want to run, not walk to his fascinating What Are You Working On? series of author interviews.

Mark will be reading in the Progressive Reading Series at 7:00 pm on Saturday, May 17 at the Makeout Room, 3225 22nd Street at Mission, San Francisco.

And hoo boy, is he ever going to be joined by an impressive line-up of writers who could tell you a thing or two about showing, not telling! Lookee:

Josh Bearman and Starlee Kine (This American Life)
Pam Houston (“Sight Hound,” “Cowboys Are My Weakness”)
Adam Mansbach (“End of the Jews,” “Angry Black White Boy”)
Mark Pritchard
Mary Roach (“Stiff,” “Spook,” “Bonk”)
David West

This evening benefits the campaign against California’s Proposition 98, and advance tickets are highly recommended.

Okay, back to business.

Last time, I argued that in both fiction and nonfiction, readers regard summarized information as less important — to the story, to the argument — than material presented in a more fleshed-out form. This is a pretty darned good reason to follow the old show, don’t tell rule in and of itself: vividly-rendered scenes, striking character development, and detailed proof are simply more memorable than quickly-sketched outlines.

Yes, you did read that correctly: I said character development. For some reason that I have never been able to understand fully, the show, don’t tell axiom and character development are seldom mentioned with in the same breath in writerly circles, or even in the same weekend seminar or composition class.

As an editor, I find this a touch odd, as in the average manuscript — come closer, so I may whisper a trade secret to you — a tendency to draw conclusions for the reader almost invariably detracts from the efficacy of character development. Heck, some professional readers would even say that telling is the natural enemy of character development.

Why? Well, several reasons, most of which dance around the issue of how people tend to read.

To understand the first reason, we need go no farther than to the opening paragraph of this post: as anyone who has ever tried to slog through a poorly-written textbook can tell you, readers are less likely to remember (read: think that they will need to remember) information presented as generalities than the same collection of facts enlivened by specifics.

Which means, in practice, that conclusions about a character tend to slip out of a reader’s mind. As you may recall from yesterday, a passage like:

Eustace was an inveterate coward, a hider behind matronly hips that had for many years been too narrow to provide truly effective concealment for his ever-increasing girth. He didn’t particularly care whose hips they were — Mom’s, his sister Rose’s, his girlfriend or wife du jour’s – so long as they were balanced between him and the frightening world.

may be amusing in the moment, but it’s unlikely to stick in the reader’s mind as anything but a pretty passage of prose. If Eustace were an important character, even a single scene that SHOWED him acting cowardly would establish this trait far more effectively than even four or five repetitions of simple assertions about it scattered throughout the text.

Why do I bring up the possibility of this much repetition? Because, alas, many aspiring writers confuse tellin} the reader what a character is like with character development.

But when the pros talk about character development, they don’t usually have broad summary statements in mind. (Yes, even if they don’t say so explicitly.) They’re generally thinking of the many, many different tiny, revealing, and delightful details a writer could use to show what a particular character is like — and how s/he grows and changes throughout the book.

This ideal should not be confused, of course, with the kind of narrative that showers the reader with a million and twelve tiny facts, each presented as equally important. That tends not to go over so well.

Especially — brace yourselves; here comes Millicent — in those all-important first few pages that determine whether a submission gets rejected out of hand or given a fuller reading. Writers seem particularly fond of overloading the reader with physical and environmental descriptions in early chapters, as if everything that could possibly be seen needs to appear in the reader’s first glimpse of the protagonist or can never be mentioned at all.

Let’s take a gander at how the average submission might introduce poor Eustace:

Whey-faced Eustace went more than usually pale, his already-pasty cheeks draining of what little blood had managed to work its way up from its customary pooling place farther south, in the region of the stomach his mother kept so well supplied and the acid-washed jeans in which she still ironed a lovingly uncool razor-sharp crease every morning. Certainly, his blood did not seem to be in the habit of regularly visiting his brain, where it might conceivably have provided some much-needed R&R to the synapses and corpuscles that would have been in charge of critical analysis in a better-lubricated mind. His reddish-blond hair, never too good a scalp covering even in its heyday, now seemed to be fleeing his astonishingly full eyebrows with all possible dispatch. If his chest hair had any aspirations to assert itself, it was still working up the nerve under his carefully-starched button-down shirts — fourteen of them hung lankly in his cedar-stuffed closet, awaiting Mom’s magical touch with spray starch. His shoes, shined to within an inch of their lives — a good trick, with sneakers — all pointed their toes toward the closet door, the front hallway, and the world beyond, as if they felt that Eustace’s timidity were the only thing keeping them from the life of adventure they deserved.

All RIGHT, already: we get the picture. We also would have gotten the picture with half as many details.

Don’t buy it? Okay, here’s a pop quiz: cover the last example and try to list all of Eustace’s physical and sartorial traits in the order they appeared. Difficult, isn’t it?

That’s not the fault of any of the individual details, incidentally. The problem here is one of emphasis — and presentation.

Too many facts in a row simply become a list, in the reader’s mind. By a couple of lines in, all of that information starts to blur together, encouraging — dare I say it? — skimming.

Faced with this kind of reaction (as well as the dread prospect of agents’ turning pale at manuscripts much over 100,000 words), many writers rush to the opposite extreme, cutting details to the proverbial bone in an effort to streamline their work.

Which isn’t necessarily going to improve the manuscript, if emphasis is the problem. What will solve it is removing non-revealing details that only serve to distract from what the writer wants the reader to take from the scene.

That last set of observations raised some hackles out there, didn’t it? “But Anne,” I hear some of the behackled exclaim, “I hate to quibble, but first you tell us not to summarize essential character information, but instead to reveal character through a plethora of details — and then you turn around insist that too many details are the kiss of death. How will I know when my manuscript has reached the right balance between detail and summary?”

Great question, raised hacklers, and one that richly deserves an answer. Unfortunately (and contrary to some writing guides out there promoting the {show, don’t tell} path of righteousness}, there isn’t a magic formula that can be applied to every manuscript.

Time to call in the first readers, in other words.

That advice didn’t sooth all that many savage breasts, did it? “Okay, Anne,” my former questioners continue through gritted teeth, “I can try to accept that. But when I gave my manuscript to my mother/sister/best friend/husband/some total stranger I happened to meet at the café down the street, I noticed that s/he didn’t seem to have all that great a memory for the details you told me to use to reveal character. Why, it says very plainly in Ch. 2 that Dorothea is my protagonist’s lover’s cousin’s au pair, but without exception, all of my feedback-givers wrote, “Who’s this?” in the margin when Dorothea appeared again in Ch. 27.”

Oh, honeys, I hope you’re sitting down, because I have some potentially disturbing news for you: most people don’t actually read every single syllable of a book, much less absorb the impact of every single sentence.

Or, to put it another way, just because a writer mentions something on a page doesn’t mean that any given reader — even a very good one who takes notes as she reads, like yours truly — will necessarily remember it all the way through the reading process.

I hope that didn’t make anyone out there faint.

Seriously, few aspiring writers seem aware of this phenomenon — come to think of it, plenty of published authors are apparently unaware of it as well. The overwhelming writerly tendency is to assume that reader is absorbing every word — otherwise, observations like what do you mean, you don’t know who Dorothea is? She was mentioned in passing 117 pages ago! simply wouldn’t make any sense, right?

You know me — I’m pretty much always on the writer’s side, right? As much as I love creative souls, I must admit that I tend to attribute this attitude to writerly ego: I wrote it, therefore it’s important.

But this isn’t always the message a manuscript is sending to the reader. One of the reasons that summaries make for less effective character development because readers are (for the most part, anyway) quite good at picking up authorial signals about what is and isn’t significant in a text.

Take, for example, the following passage from John Irving’s THE CIDER HOUSE RULES — which should be required reading, I think, for anyone who has fallen in love with 19th-century narrative styles and is trying to implement them now. It’s as jam-packed a sample of character development as you’re ever likely to see in print. Read it over, please:

You had only to know her to know that she was not a Candy; she was lovely, but never falsely sweet; she was a great and natural beauty, but no crowd-pleaser. She had daily reliability written all over her, she was at once friendly and practical — she was courteous, energetic, and substantial in an argument without ever being shrill. She complained only about her name, and she was always good-humored about it (she would never hurt her father’s feelings — or any one else’s feelings, willingly. She appeared to combine her father’s enraptured embrace of the work ethic with the education and the refinements he had allowed her — she took to both labor and sophistication with ease.

Based upon the style here, just how important a role would you expect Candy to play in the rest of the book?

Usually, a character whose traits are introduced in summary is a minor one — but Candy’s actually the most important female character in the book. Leaving aside for the moment the fact that mentioning that a female character speaks without ever being shrill or without ever sounding strident is usually code for her not holding radical feminist views like expecting to be paid for her work or be allowed to vote — or at least not holding them strongly enough to make an issue of them — what message do you think Mssr. Irving is sending the reader here by summarizing so much character development that he could easily have shown through action?

Okay, so maybe that’s not really a fair question to ask folks who may not have read the entire book, but as I have, I’ll hazard a guess: to give the reader a heads-up that Candy is going to be a fairly passive (if complex) character, acted-upon rather than acting.

Of course, that could just be my bias. But I did notice that in the movie version — based upon a screenplay by Mssr. Irving himself — virtually all of Candy’s complexity had been stripped away, her motivation for a life-changing affair with the protagonist reduced to a single line of dialogue thrice repeated in the script: “I’m not good at being alone.”

In other words, the character prefers to be acted-upon than act.

I intend no disrespect to Mssr. Irving (whose work I have loved for years, including this book), but even in a screenplay, wouldn’t it have been pretty easy to show this particular personal preference rather than simply tell about it — say, by placing the character in situations where she chooses to let others act for her?

In a manuscript, the answer is an unequivocal YES — or at any rate, should be, because it’s significantly easier for the reader to envision — and thus remember — characteristics based upon telling details than upon flat assertions.

Allow me to illustrate.

When I was a teaching fellow at a major football school that shall remain nameless (go, Huskies!), the professor whose discussion sections I was leading saw fit to assign a simply dreadful (and dreadfully simple-minded) article about how the great strength of American capitalism was that everybody could find personal fulfillment, because the market was so complex that whatever each of us wanted to sell, there would be someone out there willing to buy.

Not altogether surprisingly, my students were rather confused by this argument; it was my job to come up with a practical example to illustrate the principle. So I told them about a certain distant cousin of mine who, thanks to quite a nice singing voice, an unusual personal preference to appear in public with very little on, and the career-extending blessings of silicone implants, managed to carve out a niche for herself for many years as arguably the world’s most famous topless singer.

Think my students had any trouble remembering THAT example? Heck, when I bump into one of them on the street now, years later, there’s a better than even chance that s/he will mention it.

More to the point, every single one of them used Cousin Carol as an argumentative example on the final exam — even, amusingly enough, the students who evidently misremembered the point of the article.

Now THAT’s a telling set of details.

But that doesn’t really address the question of balance, does it? Do you still have that hard copy of your manuscript handy?

Here’s a radical revision idea: flip through it until you find a scene where it’s imperative that the reader understand that the character(s) involved has certain personality traits. Better yet, identify several scenes. At the top of each page, write a single sentence — no cheating; just one — about what you would like the reader to take away from it.

Not EVERYTHING the reader COULD take away from it, mind you — just the most important single point. (Hint: if you favor summary statements, you may already have a sentence per page that serves this function.)

Whip out your trusty highlighter pen and mark all of the character-revealing sentences. Go back through the pages, underlining all of the summary statements and circling the details.

Now read the scene(s), skipping the summary statements. Is the vital information for each page still coming across? If not, could you add a few telling details that would help bolster your point better than reinstating the summaries?

Next, take a look at the details. Are all of them necessary to make the crucial point? Or would adding a few more clarify the conclusions the reader should be drawing at that point of the text?

Stop right there: part of your brain is still trying to figure out what a topless singer would actually DO in her act, isn’t it? (And to forestall your next question: no, I never caught the act — I was in diapers at the height of my cousin’s fame — so I can’t provide satisfactory answers about it. Believe me, my students asked ALL THE TIME.)

That’s the power of a really good illustration of character, my friends: it sticks in the reader’s mind long after s/he has read it, and thus is easy to recall even 25 chapters later. But if every detail were as vivid, or if there were too many of them, the reader might have difficulty remembering necessary information throughout an entire storyline.

Be selective. Provide killer details that paint an indelible picture. And, of course, keep up the good work!

Hearsay vs. first-hand observation, or, “He ran into the room and said…”

Last week, I waxed poetic on the joys and perils of showing, rather than telling, as we writers are so often urged to do in our work. Theoretically, this advice makes oodles of sense: it is far, far more graceful to allow the reader to draw conclusions unassisted than for the author to state point-blank that a character was like this or that, right?

Well, I guess that settles that. In other news…

Wait a minute: contrary to what some hit-and-run advice-givers would evidently have you believe, in practice, it isn’t always so obvious what should be shown and what for reasons of parsimony or pacing should be merely summarized. Today, I am going to talk a little about how striking a balance between what you choose to show and what you choose to tell can affect a reader’s perception of what’s going on in a story.

Summaries, while often necessary, have the nasty propensity to compress acres and acres of fascinating action into, well, a compressed little bundle. Why is this a problem, you ask, if a writer is trying to cover quite a bit of material quickly?

Well, many aspiring writers make the serious mistake of assuming that if what’s being DESCRIBED is interesting or action-packed, the summary automatically will be as well. However, this is often not the case. Even when the summarized activity is inherently exciting, glossing over it as quickly as possible tends to sap its impact upon the reader. Compare, for instance:

Ghislaine flung her well-muscled arms around her long-lost lover, Robert. In the midst of one of the most passionate kisses the world has ever known, her eyes closed fully for the first time in seven years. Gone was the crowd of blunderbuss-wielding soldiers awaiting her culinary artistry; vanished were the king, queen, jack, and rook whose movements across the checkered floor had diverted her from her labors. Even the snarling dog at her heels, Lord Augustine’s pet, faded from her consciousness until it savagely ripped her foot off at the ankle. As she fell to the ground to be worried into sandwich meat, she saw her kid brother rush forward and stab her one true love between the third and fourth rib.

With:

Ghislaine hugged Robert. Lord Augustine’s dog bit her, and as she fell, her kid brother stabbed Robert.

Both of these passages are describing exactly the same event — and there’s no denying that the second moves the plot along pretty expeditiously. But when speed comes at the expense of enough detail for the reader to understand what’s going on, the story suffers.

And lest you nonfiction writers out there have been feeling a bit smug throughout the discussion of show, don’t tell, over-summarization can also seriously undermine an argument as well. Often, summary in nonfiction will take the form of presenting conclusions before (or even instead of) the detailed facts from which the author is deriving the conclusions.

Don’t believe me? Check out this historical summary about today’s poster girl:

Lucilla was a Roman empress of ill repute. Actually, we only have her successors’ word for that — her younger brother, the emperor Commodus, was no prize himself. The two of them were continually trying to assassinate each other, and Commodus, after having his sister executed, was left in charge of her reputation. As has often been the case with history since, the victors in Roman times used to work overtime to smear the reputations of those whom they deposed. Recently, scholars have begun to argue, albeit not very loudly, that Caligula, Macbeth, and Richard III might not have been such bad guys.

Leaves you wanting something more, doesn’t it? Evidence to support these contentions, for instance, or perhaps some indication of WHY Marcus Aurelius’ children might have been at each other’s throats? Clearly, this is a paragraph that deserves to have SHOW, DON’T TELL scrawled in the margin next to it — in Latin, presumably — even though everything in it is factually correct.

(Yes, really — someone actually is trying to rehabilitate Macbeth’s reputation. Hard to believe that he would care much at this point, but still, it’s kind of sweet.)

In both fiction and nonfiction, readers tend to perceive summarized information as less important than detailed accounts — unless, of course, the author has overwhelmed them with five million tiny facts, each presented as equally important.

We’ve all experienced this as readers, right? As we saw above in poor Ghislaine’s case, if a narrative presents a scene vividly, it’s inherently more memorable than summarized action. In the reader’s mind, s/he was there for the former, but merely told about the latter.

Try this on for size: when the herald comes running into the banquet hall to announce that the army has lost the battle and the enemy is about to storm the castle’s walls — as anyone who has ever seen a filmed costume drama or Shakespearean tragedy would naturally expect him to do — you might want to ask yourself, “Would this scene be more exciting if I SHOWED the army fleeing and the enemy scaling the walls, instead of having good old George just turn up and tell all the rest of the characters about it?”

I’m sensing some discomfort with that last suggestion. “But Anne,” I hear some of you herald-huggers out there protesting, “isn’t George’s running into the room active and exciting? If I show the marauding hordes approaching, won’t that cut into the sense of surprise in the room when they find that they’re under siege?”

Well, yes, announcement aficionados, George’s flinging the door open and yelling at the top of his lungs would indeed be action — but is it the most effective (or important) way to impress upon the reader the practical implications of being overrun? Would it not perhaps be more startling if the revelers had no advance warning at all, so the reader just saw them react when a hundred armed Amazons broke down the door?

I’m just saying.

The classic active-teller vs. shown action misstep is somewhat more complicated than this: a character’s narrating a scene s/he observed to a third party. Here’s an example from Louisa May Alcott’s potboiler BEHIND A MASK, a highly amusing and ethically dubious tale of Jean Muir, an actress who infiltrates an affluent English country family with an eye to the main chance. (The outcome will, I promise you, surprise most readers of LITTLE WOMEN.)

Fair warning: there is more than one problem in this passage; see if you can spot the full array. Lucia has been sitting with her presumptive fiancé, Gerald, who keeps flitting away to spy on his brother and sister being enchanted by the mysterious governess:

Lucia looked at her cousin, amazed by the energy with which he spoke, the anxiety in his usually listless face. The change became him, for it showed what he might be, making one regret still more what he was. Before she could speak, he was gone again, to return presently, laughing, yet looking a little angry.

“What now?” she asked.

“‘Listeners never hear any good of themselves’ is the truest of proverbs. I stopped a moment to look at Ned, and heard the following flattering remarks. Mamma is gone, and Ned was asking little Muir to sing that delicious barcarole she gave us the other evening.

“‘Not now, not here,’ she said.

“‘Why not? You sang it in the drawing room readily enough,’ said Ned imploringly.

“‘That is a very different thing,’ and she looked at him with a little shake of the head, for he was folding his hands and doing the passionate pathetic.

“‘Come and sing it there then,’ said innocent Bella. ‘Gerald likes your voice so much, and complains that you will never sing to him.’

“‘He never asks me,’ said Muir, with an odd smile.

“‘He is too lazy, but he wants to hear you.’

“‘When he asks me, I will sing — if I feel like it.’ And she shrugged her shoulders with a provoking gesture of indifference.

“‘But it amuses him, and he gets so bored down here,’ began stupid little Bella. ‘Don’t be shy or proud, Jean, but come and entertain the poor old fellow.’

“‘No, thank you. I engaged to teach Miss Coventry, not to amuse Mr. Coventry,’ was all the answer she got.

“‘You amuse Ned, why not Gerald? Are you afraid of him?’ asked Bella.

“Miss Muir laughed, such a scornful laugh, and said, in that peculiar tone of hers, ‘I cannot fancy anyone being afraid of your brother.’

“‘I am, very often, and so would you be, if you ever saw him angry.’ And Bella looked as if I’d beaten her.

“‘Does he ever wake up to be angry?’ asked that girl, with an air of surprise. Here Ned broke into a fit of laughter, and they are at it now, by the sound.”

Leaving aside the editor-annoying facts that people do not generally shrug anything BUT their shoulders and that if Gerald could hear the others laughing, chances are that Lucia could, too, did you catch the show-don’t-tell problems here? Or was the over-use of the verb to look just too distracting?

Give yourself a big gold star if you said that the first paragraph watered down Gerald’s changed mien by filtering it through Lucia’s conclusions about it. Give yourself two if you murmured that the transition between her perspective and his was a trifle abrupt.

If you are like most readers, though, none of these things would have qualified as this passage’s biggest problem: its real downfall is the soporific effect of having Gerald narrate this scene, flattening out all of the individual characters’ quirks. To render the reader even sleepier, the tension is lax, since we knew (because the narrative TOLD us) that he returned right away; evidently, then, what he had to tell could not have been particularly dramatic, or at any rate not life-threatening.

Zzzz.

Yet this scene could have been rather amusing and revealing, with slightly different authorial choices. By making Gerald not only the reader’s eyes and ears in a scene in which he is a passive listener AND using him as Lucia’s eyes and ears as well, this scene becomes all about Gerald’s perceptions, not about the actual dialogue he is reporting.

Had our friend Louisa instead elected to hide him behind a curtain and OBSERVE that scene, the narration could have embellished, shown each speaker’s tone, and increased the tension by introducing the possibility that he might get caught eavesdropping.

Instead, Ms. Alcott decided to keep it all from his perspective AND in his voice — anyone out there care to guess why?

To a professional reader, it’s pretty obvious: clearly, because the author wanted to use the line And Bella looked as if I’d beaten her, an impossibility UNLESS Gerald was the narrator at that juncture.

Believe it or not, an aside like this is not an uncommon reason for drafting an uninvolved actor into narrator service.

While I’m on the subject of characters narrating others’ activity, I should probably mention a pet peeve shared by scores of agents, editors, and contest judges the world over: when the narrator reports things s/he could not possibly know, presumably in the interest of not switching out of the chosen narrative voice.

This is VERY common in first-person narratives — where necessarily, ALL the reader should logically hear about is what the narrator can observe or recall. So how could the narrative possibly include other characters’ thoughts, feelings, or incidents that occurred when the narrator was not physically present?

Most of the time, writers choose one of two paths around this problem, both extremely hard to pull off on the page: abandoning the chosen narrative perspective just long enough to include necessary information that the narrator can’t know (dicey, unless the perspective shifts to an omniscient narrator) or by having someone like Gerald lope up to the protagonist and tell him what happened.

I blame television and movies for the pervasiveness of both of these strategies.

Just as the limitations of film have told writers that all human experience should be conveyed merely through the audible and the visible, leaving out other stimuli except as verbally described by the characters, they have also instructed us that where the camera can go, so can the narrator. But in a first-person narrative, this logically is not true.

I have quite a bit more to say on this subject, but for today, suffice it to say that from a reader’s perspective, just because character is shown summarizing action doesn’t make it any less a summary than if the same information appeared in a narrative paragraph. On the showing vs. telling continuum, it tends to fall toward the telling end.

Every so often, consider giving that poor herald a rest. Let the actions — and actors — speak for themselves.

Keep up the good work!

Book out TODAY from one of our own — and a writing contest!

Another post on craft follows soon, of course, but I wanted to get the trumpets blowing as soon as possible: the ever-fabulous Joel Derfner, better known to those of us here at Author! Author! as the prolific commenter and blogger extraordinaire Faustus, M.D. has a hilarious memoir coming out today from Random House’s Broadway Books!

Congratulations, Dr. F! Please join me, everyone, in a great big round of applause.

If you live in or around New York, Joel will be reading TONIGHT at 7:30 pm at the Barnes & Noble at 396 Avenue of the Americas . (if you’re like me and rely upon the kindness of strangers to navigate the isle of Manhattan, tell the cabbie that you’d like to go to 6th Avenue and 8th Street.) I have it on pretty good authority that in addition to being a hilarious reader, he also bakes a mean brownie; there may be some baked goods in evidence.

SWISH (which may be purchased from today onward from Amazon, Powell’s, and other fine book emporia) is Joel’s second book, following hard upon the heels of the must-be-experienced-first-hand GAY HAIKU.

Take a gander at the publisher’s blurb for SWISH:

Joel Derfner is gayer than you.

Don’t feel too bad about it, though, because he has made being gayer than you his life’s work. At summer day camp, when he was six, Derfner tried to sign up for needlepoint and flower arranging, but the camp counselors wouldn’t let him, because, they said, those activities were for girls only. Derfner, just to be contrary, embarked that very day on a solemn and sacred quest: to become the gayest person ever. Along the way he has become a fierce knitter, an even fiercer musical theater composer, and so totally the fiercest step aerobics instructor (just ask him—he’ll tell you himself).

In SWISH, Derfner takes his readers on a flamboyant adventure along the glitter-strewn road from fabulous to divine. Whether he’s confronting the demons of his past at a GLBT summer camp, using the Internet to “meet” men—many, many men—or plunging headfirst (and nearly naked) into the shady world of go-go dancing, he reveals himself with every gayer-than-thou flourish to be not just a stylish explorer but also a fearless one. So fearless, in fact, that when he sneaks into a conference for people who want to cure themselves of their homosexuality, he turns the experience into one of the most fascinating, deeply moving chapters of the book. Derfner, like King Arthur, Christopher Columbus, and Indiana Jones—but with a better haircut and a much deeper commitment to fad diets—is a hero destined for legend.

Written with wicked humor and keen insight, Swish is at once a hilarious look at contemporary ideas about gay culture and a poignant exploration of identity that will speak to all readers—gay, straight, and in between.

I don’t generally review books here, but I am going to bend my own rules a little in this instance to recommend this book to any of you out there who aspire to write either comedy or memoir, as well as to those enamored of a good laugh. Rarely have I seen a memoirist’s personality emerge so charmingly on the printed page — or so honestly. Over and above Joel’s talent with an outrageous turn of phrase and genuine gift for humor (which is, alas, granted less often by the muse Thalia than those of us who like to read comedy might like), this is a darned fine piece of memoir writing.

So fair warning, Dr. F: I’m going to be blandishing you mercilessly for a guest post on the subject. After your book tour, of course.

In the meantime, I promised you a writing contest, didn’t I? And a contest you shall have. Quoth Joel:

The First Annual Gay-Off

In the introduction to SWISH, I explain that my quest to become the gayest person ever did not turn out to be an unqualified success—which means that the position of the Gayest Person Ever is still open. So I’m having a Gay-Off.

If you’re interested in competing, log onto my website and send me a brief explanation (up to 100 words) of why you should be crowned this year’s Gayest Person Ever. Note, please, that in order to enter you do not have to be gay or even, I suppose, a person. The Gayest Person Ever describes an existential state, irrespective of plumbing and flavor.

The last day to send in entries is Tuesday, June 10. On Friday the 13th, I’ll post the top five entries (as determined by an independent panel of judges) on my website, and from then through the end of Gay Pride (Sunday, June 29) you can vote for your favorite.

At the moment I’m planning prizes as follows: the grand prize is a signed copy of Swish, a signed copy of my first book, Gay Haiku, a Swish T-shirt, a gay haiku written for the winner, and, depending on geographic location, a tin of homemade brownies made with loving care by me. Second prize a signed copy of Swish, a Swish T-shirt, a gay haiku written for the winner, and a tin of brownies slightly inferior to the tin the Grand Prize winner gets. Third prize is a Swish T-shirt, a gay haiku written for the winner, and a tin of brownies slightly inferior to the tin the Second Prize winner gets. However, the actual prizes may be different from this, like if I eat the brownies or something.

Good luck, and may the Gayest Person win!

See, I wasn’t kidding about the brownies. Should be a lot of fun — and it’s never a bad idea to run your work under the eyes of folks who already have agents, even if it’s just 100 words.

Congratulations, Dr. F, and please keep all of us here at Author! Author! posted on your book’s success!

The hard-and-fast rules about hard-and-fast rules

We begin today with a quiz: what does this photograph depict? More to the point, if you had to describe it in a manuscript, how would you do it?

Why, yes, now that you mention it, those are two rather different questions: the first has a single, fact-based answer, the second no uniquely right answer.

And yes, that IS an excellent parallel for many aspects of the revision process. How clever of you to spot that. Pat yourself on the back immediately.

I have been on retreat for the past couple of days, meditating in a remote mountain cave and living off sips of purest dew while I wrestled with the knotty problem of creating the Platonic blog post on showing, rather than telling — because, as I’m sure some of you have noticed, I’ve been spending the last week or so dancing around various aspects of incisive reader Shelley’s delightfully straightforward request that I address what the oft-repeated writing axiom actually MEANS.

There’s a short answer, of course, which I snuck unobtrusively into an earlier post: telling is when the narrative simply states what is going on and what it means, whereas showing is when the narrative allows the reader to be the primary drawer of conclusions based upon what the various characters do, say, and think.

The longer answer involves, as we’ve seen recently, a whole plethora of very specific writing strategies and techniques. I could keep us occupied for a good month on them, if I really put my mind to it. And I certainly intend to focus on a few of my favorites in the days to come.

But that prospect didn’t relieve me of the feeling that I really owed it to posterity to write the definitive single post on the matter, I must confess. If I crafted my notions persuasively enough, I figured, if I made the case for show, don’t tell so convincing that no reasonable creature could possibly ever disagree with it, if I made the very idea of telling rather than showing sound so unappealing that each and every one of you would feel faint at the very idea of doing the former, I could rest again at night.

I would also be a benefactor of humankind deserving of being carried through the streets of the nearest metropolis by an admiring throng — nay, of every metropolis in the English-reading world, if not actually meriting having my profile appear on future coinage, stamps, and Wheaties boxes.

If I could manage to make it funny as well, someone might even name a dessert of some sort after me, like Napoléon or Pavlova.

In short, I made the task so gigantic in my mind that there was absolutely no possibility of my ever posting on the subject again. Evidently, I was doomed to spend the rest of my natural life in that cave, being fed by those cartoon birds that are always fluttering around Snow White.

What knocked me out of my self-imposed procrastinative funk, you ask? My neighbor, Sarra, made me a mocha that was a work of art, complete with a beautiful top layer of foam patterned like an exotic cat’s pelt.

The subject of the photograph above, in short.

In the proverbial flash, the answer to my dilemma came to me: like so many of the so-called hard-and-fast rules of good writing, show, don’t tell should NOT be applied blindly to a manuscript, but with discretion — and with style.

Let’s face it — it’s not the clearest piece of advice anyone has ever given a writer. In some ways, show, don’t tell is a bit vague; show, don’t summarize is probably clearer advice. At least for the interesting bits that you want to stick in the reader’s mind forever and a day.

Obviously, though, any writer is going to need to summarize certain events from time to time: if every book set during wartime, for instance, had to describe every battle down to the last drop of blood hitting the ground, there wouldn’t be a whole lot of room for character development, would there?

Want a concrete example, do you? Okay, think about the photograph above for a moment. Factually, it’s a picture of a cup of coffee. Narratively, I would have been perfectly within my rights to tell you so from the get-go, correct?

But that simple empirical description wouldn’t have conveyed a whole lot about either the odd, animal-print beauty of the foam on top or how it got there, would it? Or why Sarra, a barista of local repute, might have gone to the trouble of creating such an intricate pattern, would it?

My guess is that she likes me — but that’s an example of the narrator’s drawing a conclusion that the reader might have drawn unassisted from the narrative so far, right?

I could, of course, have just come out and tell you that the foam was gorgeous, but gorgeous is a pretty non-specific descriptor, one that could conceivably apply to each and every one of the beautiful objects and people in a full and lovely universe.

Herd a hundred intelligent, observant people into a room and ask them to define the term, and you’ll end up with a hundred equally valid answers. Possibly more, if some of those hundred happen to be both indecisive and verbose.

By contrast, chestnut brown lushness alternated in chevrons with airy cream foam is awfully darned specific, isn’t it? Given the choice between that description and the foam was gorgeous, which do you think conveys a more vivid impression of what I actually saw?

The former is showing; the latter is telling.

Notice, however, that I did not describe the cup containing the drink of beauty in equal detail, nor the countertop upon which it rested briefly, nor the room in which Sarra and I were standing at the moment I first beheld her artistry.

Had I taken the axiom show, don’t tell very literally, I might have engaged in equally detailed descriptions of all of these — in addition to regaling you with meticulous accounts of the sky visible through a nearby window, the grunt of approval my SO emitted when I showed him my prize coffee, and every article of clothing I happened to be wearing today.

Why didn’t I do that? Because we’d all be here until Doomsday.

Also, these factors were extraneous to the story. Including them would have watered down the intense visual image that I was attempting to impress upon my readers’ brainpans.

Let me repeat that, because it’s vitally important: including too much detail can distract the reader from the main point of a description, scene, or narrative paragraph.

Show, by all means, but not indiscriminately. Apply the technique where it will have the greatest effect.

Dare I say it? Yes, I shall: use your judgment.

I’m sensing some uncomfortable shifting out there at the very notion, amn’t I? “But Anne,” I hear some of you murmur, “isn’t the point of a hard-and-fast rule that we should apply it in EVERY instance? Relying upon one’s individual judgment implies a bit more wiggle room than I am used to hearing about in rule application.”

Great question, anonymous murmurers — but doesn’t the answer depend very much upon what KIND of rule you’re thinking of applying?

Matters of grammar or standard format, for instance, are the stripe of rules that one might want to take literally every time. A semicolon may only be used in a certain limited number of ways, after all, and it would be pretty hard to argue that a 1″ left margin meant anything but that the text should begin one inch from the left-hand side of the page.

Other rules are not so clear-cut.

A very powerful agent who specializes in genre fiction used to tell roomfuls of conference-goers that he ALWAYS stopped reading a submitted novel as soon as he encountered a scene in which characters were drinking coffee, tea, or any other non-alcoholic beverage.

Why? Because he had found over years of scanning submissions that such scenes almost always involve the characters sitting around and talking about what was going on in the plot, rather than going out and doing something about it. Much like scenes where the protagonist sulks in his tent, thinking, these scenes provide analysis of what has already happened, rather making something new happen.

To him, such scenes were the kiss of death: they indicated, he said, that the author did not know how to maintain tension consistently throughout a book.

Now, speaking generally, he probably had a point: it’s not all that uncommon for characters to get together to discuss what the reader has just seen happen, mulling the implications without doing much to change the situation and thus move the plot along.

(Phone conversations are also prone to this tendency — especially, for some reason, when the chat is between the protagonist and his or her mother. Happy Mother’s Day.)

But the rule the agent proposed was not take a good look at any scene where your characters sit around and talk instead of acting, was it? I might go along with that, but no, his advice was very specifically beverage-related: implicitly, he was telling those roomfuls of aspiring writers to cut ANY scene where the protagonist was drinking coffee, tea, or any other quaffable liquid under 50 proof, on pain of getting their manuscripts rejected.

Sure sounds like a hard-and-fast rule, doesn’t it?

But it isn’t — and couldn’t be, in every instance, any more than it would be safe to declare that every scene that takes place in a bar is inherently action-packed.

Especially in my neck of the proverbial woods. Since I edit for many Seattle-based writers, if I advised them to skip every possible coffee-drinking opportunity in their works, I would essentially be telling them to ignore a fairly significant part of local community culture. Their poor characters would wander the streets in the omnipresent drizzle, mournfully wondering where their hang-outs had gone.

I do, however, routinely suggest that aspiring writers flag any lengthy let’s-talk-it-over scenes — no matter what kind of beverage happens to be bouncing about in the protagonist’s digestive system at the time — then go back and read the entire manuscript with those scenes omitted. Nine times out of ten, the pacing of the book will be substantially improved, with little significant loss of vital information.

The moral: pacing is HUGELY important to professional readers; if a discussion scene slows the book down without advancing the plot, consider trimming it or cutting it altogether. Ditto with pages at a time of uninterrupted thought.

What the moral isn’t: the mere mention of potable liquid kills narrative tension. Unless, of course, that liquid can be poured over a plum pudding and set aflame.

If you have ever found yourself wondering why I explain the logic behind my writing and marketing advice so extensively here — even for the rules of standard format, which aren’t negotiable (and if you aren’t sure why, or were not aware that there were professional standards for submitted manuscripts, please see the STANDARD FORMAT BASICS category at right) — this is why.

Yes, some rules of writing are pretty set in stone — but a great many are in fact matters of style, taste, and/or marketing strategy.

For those, you will need to use your own judgment, unavoidably. All I’m trying to do here is give you enough information about why certain stylistic choices and marketing strategies might behoove you to embrace.

Ultimately, though, it’s up to you whether to give ‘em a big old hug.

So if you asked me if it was all right to use business format for a query letter, I might instantly shout, “In heaven’s name, NO!” but that wouldn’t stop me from explaining at great length why I would do everything in my power to discourage you from making that TERRIBLE, TERRIBLE MISTAKE.

(If that last paragraph didn’t tempt you to chortle knowingly, you might want to take a gander at the HOW TO WRITE A QUERY LETTER category in the list at right before you send off your next. I just mention.)

In that spirit, I’ve saved the best possible argument for showing, not telling until after I’ve urged you to weigh the pros and cons of a writing axiom before you apply it. Everyone sitting comfortably? Here goes:

Based upon my description of the cup of coffee Sarra made for me, what do you think she’s like? What kind of a relationship do you think she and I have?

I’m not going to tell you. I’m going to let the details speak for themselves. You’re a good reader; draw your own conclusions.

And that, my friends, is an example of a narrative’s showing, not telling.

More specific strategies follow in the days to come, naturally. In the meantime, keep up the good work!

The (book) doctor makes a house call

If you’ll recall, just before I elected to ski down the slippery slope of dissecting all of the problems Hollywood narration can bestow upon a manuscript, I was already perched upon a soapbox, pointing out the pacing, voice, and storytelling dangers inherent to sneaking too much background information or physical description into interview scenes early in a novel submission.

Today, I’m clambering back up on that soapbox. Because, honestly, I’m reading as fast as I can, but I’m just not going to be able to read every manuscript in the English language before it lands upon the always-crowded desk of our old pal, Millicent the agency screener.

No doubt spilling her too-hot latte.

For those of you who missed my earlier posts on the subject, an interview scene is one where a character — generally the protagonist — obtains information critical to the plot and/or character development from another character, extracted through dialogue.

And a questionable interview scene is one in which, as is all too often the case in submissions, the narrator is not a particularly good interviewer, causing the reader to become impatient and/or lose interest in following that person who NEVER ASKS THE LOGICAL FOLLOW-UP QUESTION or JUST SITS THERE WITHOUT ASKING ANYTHING, waiting for the interview subject to spill his guts spontaneously.

If the reader in question happens to be Millicent, her cousin Maury the editorial assistant, or her Aunt Mehitabel the noted contest judge (hey, they’re a literary-minded family), the consequences are usually even more serious: if she loses interest in the manuscript before her, she tends to stop reading.

In other words, “Next!”

How may a writer avoid this grisly fate? Here’s a good rule of thumb: while not everything that people say in real life makes good dialogue, it’s an excellent idea to make sure that all of your dialogue is in fact something a real person MIGHT say.

And here’s a secondary rule of thumb — a rule of forefinger, one might say: that goes double for any dialogue that sounds anything remotely like Hollywood narration.

Yes, even if you have heard with your own tiny, shell-like ears a real person speak that way. As I have been pointing out none too gently for the past couple of days, real human beings tend not to tell one another things they already know — except, of course, about the weather (“Some heavy rains we’ve been having, eh?”), the relative progress sports teams (“How about them Red Sox?”), and politics (I’m not even going to go there until the Democratic nomination is beyond dispute).

In print, such iterations of mundane issues are notably primarily for their soporific value. As storytelling, such homely gems just tend to slow down the action of the scene.

Interestingly enough, adhering to these two rules while revising almost always results in trimming interview scenes substantially. This is particularly true for interviews that open novels, where Hollywood narration and dialogue stuffed with visual clues about characters tend to congregate — and thus are likely to do the most damage.

I sense some shifting in seats out there. “Yeah, yeah,” the impatient are murmuring. “You already yammered at us about this, Anne. Cut to the chase, already.”

Funny, that last sentence is precisely what Millicent is often heard muttering over interview scenes.

But you have a legitimate point, impatient mutterers. However, in my discussions earlier in the week, I left out one of the primary reasons Millicent tends to have that particular knee-jerk reaction: if the first couple of pages of text are a bit heavy-handed, agency screeners, contest judges, and other professional readers usually leap to the conclusion that the ENTIRE text reads the same way.

An assumption, as you no doubt have already guessed, that conveniently enables Millie and her ilk to reject the descriptively front-loaded submission immediately and move swiftly on to the next.

I have seen a LOT of good manuscripts done in by this tendency. Because this is such a common problem, as an editor, one of the first places I look to trim is that first scene — which, as I mentioned a few days back, is very, very frequently an interview scene.

Particularly if the opening scene relies far more heavily upon dialogue than narration. Take, for instance, this piece of purple-tinted prose:

“Don’t you go rolling those large hazel eyes at me, Thelma,” Marcel warned. “It hasn’t worked on me since our days in the chorus twelve years ago, in that bizarre road company of Auntie Mame. And you can save the eyelash fluttering, too. You’re wearing too much mascara, anyway.”

Thelma laughed. “That’s a fine criticism, coming from a man wearing false eyelashes. Just because you’re a drag queen doesn’t mean you can’t dress with some taste. I mean, bright red lipstick with a pale lavender sweater? Please.”

“What about you?” Marcel shot back. “In your puce bathrobe with purple magnolias dotted all over it still, at this time of day!”

Thelma walked around him, to check that the seams on his stockings were straight. “Because you’re my best friend in the world, I’m going to be absolutely honest with you: you’re too heavy-set for a miniskirt now, darling. Certainly if you’re not going to shave your legs. What are you now, forty-five and a size twenty-four?”

Marcel smoothed down his Technicolor orange wig. “At least at six feet, I’m tall enough to wear Armani with style. Your cramped five foot three wouldn’t even be visible on a catwalk.”

Admittedly, the banter here is kind of fun, but a judicious mixture of dialogue and narration would convey the necessary information less clumsily, without rendering the dialogue implausible. Try this moderately snipped version on for size:

Thelma rolled her large hazel eyes. Even ensconced in a ratty puce bathrobe that barely covered her short, round form, she carried herself like the Queen of the Nile.

Unfortunately for her dignity, her icy hauteur act had grown old for Marcel twelve years ago, three weeks into their joint chorus gig in that chronically under-attended road tour of Auntie Mame. “You can save the eyelash fluttering, sweetheart. You’re wearing too much mascara, anyway.”

Thelma laughed. “You’re a fine one to talk taste. Bright red lipstick with a pale lavender sweater? Please.”

His thick, black false eyelashes hit where his pre-plucked eyebrow had originally been; his current fanciful impression of an eyebrow swooped a good four inches higher, threatening to merge with his Technicolor orange wig. Even for a career drag queen, his moue of surprise was a bit overdone. “Will you be getting dressed today, darling?” he asked brightly. “Or should I just get you another bottle of gin, to complete your Tallulah Bankhead impression?”

Thelma walked around him, to check that the seams on his stockings were straight. He was getting too heavy to wear fishnets every night; still, not bad gams, for a forty-five-year-old. “If you insist upon wearing a miniskirt, my sweet, you might want to consider shaving your legs.”

Same information, but more naturally presented, right? By having the narration take over the bulk of the descriptive burden, a rather amusing narrative voice has emerged, conveying a point of view distinct from either Marcel or Thelma’s.

I can hear my mutterers muttering again. “Okay, so the second version has a stronger narrative voice,” they concede. “But even so, all of that physical description makes the scene drag a bit, doesn’t it?”

Which brings me back to my closing question from yesterday: other than the fact that television and movies have accustomed us all to having an instantaneous picture in our heads of a story’s protagonist, is there a valid reason that a narrative must include a photographic-level description of a character the instant s/he appears in the book?

Anytime you sit down to ponder revising the first few pages of a novel, it’s worth investing a moment or two in pondering the possibility that there is no such reason.

Consider it, perhaps, while sitting with a hard copy of your first few pages in your hand. Is there backstory or physical description that could come more gradually, later in the chapter or even later in the book?

Or — and this is a possibility that often occurs to professional readers of interview scenes, let me tell you — is that Hollywood narration or description-laced dialogue the book’s way of telling us that perhaps the book opens at the wrong part of the story?

I hope that didn’t make anyone out there faint; I’m not the kind of doctor that can resuscitate the fallen with impunity.

But I am the kind that can suggest ways to improve your book. Might, for instance, we learn more about Thelma and Marcel in a more graceful manner if, instead of beginning the novel with the dialogue above, it opened with a short prologue showing them twelve years ago, bright-eyed, innocent, and slim — and then jumped ahead to this scene, to show how they and their relationship have changed?

Dramatic, eh? One might even say character-revealing.

Of course, front-loading an opening scene with physical description is not necessarily an indicator of a structural problem. I suspect that often, writers who use this technique as a means of introducing description are driven primarily by a panicked sense that the reader must be told what the characters look like the instant they appear in the text — combined with a recollection that their high school writing teachers said that too-extensive physical descriptions in the narrative are dull. So they’re sort of trying to, you know, sneak the physical description in when the reader isn’t looking.

Trust me, a professional reader is ALWAYS looking. It’s her job.

Looking specifically, in the case of an agency screener or editorial assistant plugging through a mountain of submissions, for a reason to reject the manuscript in front of her. By avoiding the common twin traps of overloading the first scene with crammed-in backstory and physical description, a manuscript stands a much greater chance of cajoling Millicent into reading on to scene #2.

And we all want that, don’t we?

I sense more impatient shifting in the peanut gallery. “Um, Anne?” these fed-up folks say. “Isn’t this the same point you made a few days ago? I get it, already: don’t use dialogue to have characters describe one another. Have you considered that there might not be a reason to keep telling us this?”

Ah, but you’re assuming that I’ve already made my primary point. Far from it; like other doctors, we book medicos bill for our advice by the hour.

So here comes some professional wisdom: after a screener has had the privilege of scanning a thousand manuscripts or so, it becomes pretty clear that many aspiring writers don’t really understand what the writing gurus mean when they urge us all to open with a hook.

A hook, for those of you new to the term, is a grabber located within the first paragraph of a story or book — preferably within the first sentence, according to some writing teachers — that so intrigues the reader that s/he is instantly sucked into the story. (This is not to be confused with a Hollywood hook, a one- or two-sentence pitch for a script or book. See the so-named category on the list at right, if you are curious about the latter.)

Often, aspiring writers will interpret the advice to open with a hook to mean that a storyline must open with violent or even bloody action, a mystery that the reader will want to solve, or a conflict-ridden scene. While admittedly Millicent sees a whole lot of manuscripts that open with a bang (with or without gushes of blood), all of these strategic choices can indeed work, if handled well.

Although let me tell you, they are such common choices that it’s a downright relief to most professional readers when a writer elects to open with a powerful visual or sensual image instead.

What’s even more common than the book that kicks off with conflict? An beginning that insists that the reader must be 100% up to speed on the plot and characters by the bottom of page 1 — or page 5 at the latest.

Again, that vexing question rears its ugly head: is this strictly necessary?

Brace yourselves, because I’m about to suggest a revision technique that may shock some of you: just as an experiment, try removing the first scene of your book. Not permanently, mind you — and certainly not without having made a backup copy of the original first, in case you decide after mature and careful consideration that this was a stupid idea.

Cut it just long enough to find out whether the story would make sense to the reader without it. If it can fly that way, consider cutting the scene entirely and starting fresh slightly later in the plot.

I’m quite serious about this — you wouldn’t believe how many good manuscripts don’t actually begin until a couple of scenes in, or that allow absolutely gorgeous opening sentences or images to languish on page 4. Or page 15.

Or the beginning of Chapter Three.

Yes, I know: what I’m suggesting is potentially pretty painful; as we discussed in the GETTING GOOD AT ACCEPTING FEEDBACK series (still conveniently accessible in the category list at right, in case you missed it), many, many aspiring writers regard the approach of the reviser’s pen with every bit of the fear and loathing that the published writer feels for governmental censorship. But it’s just a fact that when we’re first constructing a narrative, we writers are not always right about where the story should begin and end.

If you don’t believe this, I can only suggest that you take a gander at THE BROTHERS KARAMAZOV, an undoubted masterpiece that could have lost most of the first 200 pages without bugging the reader much at all.

(That’s a professional opinion, by the way. One of the great fringe benefits of having walls lined with diplomas from prestigious institutions and a Ph.D. that’s just gathering dust these days is the ability make sweeping judgments like that about classics without fear of sounding ignorant. While I’m at it, allow me to add: THE TAMING OF THE SHREW is a stupid play, and I found A TALE OF TWO CITIES far-fetched. So there.)

Try to keep an open mind while you’re revising. Be willing to consider the possibility that your story might be more effective — and hook the reader better — if you began it at a different point. Or at least do a little field testing to rule it out.

Believe me, you’ll sleep better at night if you do.

How do I know this, you ask? Because now, I’ve planted the doubt in your mind. As much as you might pooh-pooh the idea that all or part of your opening could be snipped away without fundamental harm to the storyline, can you be ABSOLUTELY sure that it’s a stupid suggestion without going back over it pretty rigorously.

You’re welcome — and I mean that very seriously, because an aspiring writer who is willing to examine and reexamine her writing before she submits it is going to have a much, much easier time coping with editorial feedback later on in the process.

Trust me; I’m a doctor. That diploma over there says so.

Keep up the good work!

Yes, I KNOW that people use run-ons in everyday speech, but Millicent isn’t judging every word that falls out of the guy sitting next to you in the café’s mouth, is she? Anyway, what’s your hurry?

How are you enjoying our recent foray into craft issues and revision tips? Inspiring? Annoying? A little of both?

Never fear — here at Author! Author!, we never stray very far from marketing issues. As much as I love to talk about writing qua writing, my focus throughout this series is going to remain practical: how to revise your manuscript to minimize its chances of running afoul of screener Millicent’s hyper-critical eyes.

Last time, I began discussing that most overused of words in manuscripts, and. Leaning on this multi-purpose word can lead, I argued, to run-on sentences, dull action sequences, and contracting the bubonic plague.

Well, okay, perhaps not the last. But the results still aren’t pretty.

The other all-too-common and sentence structure, X happened and Y happened, turns up VERY frequently in both submissions and contest entries. It’s appealing because, like stringing together sentences beginning with conjunctions, it artificially creates the impression conversation-like flow:

I woke up the next morning and poisoned my husband’s cornflakes.

See? Chatty, casual: the way your local poisoner is very likely to say it to her next-door neighbor, right?

Many aspiring writers consciously strive for prose that echoes the kind of conversational rhythms and structures one hears every day, particularly when they are penning first-person or present-tense narratives. “I want it to sound real,” they say with engaging earnestness. “My goal is to hold, as ’twere, the mirror up to nature.”

Unfortunately, from Millicent’s perspective, most of these writers don’t realize just how widespread this particular goal is — or that much real-life conversation would be either deadly dull, logically incoherent, or at minimum not literarily interesting transferred directly to the printed page.

Why? Well, to take the reason most relevant to us today, because real-life speakers repeat both words and sentence structures to an extent that would make even the most patient reader rip her hair out at the roots in frustration.

If you doubt this, here’s a little experiment: sit in a crowded café for two hours, jotting down the conversations around you verbatim. Afterward, go home and type up those conversations as scenes, using ONLY the dialogue that you actually overheard.

If you can complete the second part of that exercise without falling into a profound slumber, you have an unusually high threshold for boredom. Or perhaps you have a great affection for the mundane.

In any case, it’s highly unlikely that you would be able to get the result past Millicent, either as dialogue or as narrative. In professional writing, merely sounding REAL is not enough; a manuscript must also be entertaining.

Yes, Virginia, even if it happens to be literary fiction, if it’s book-length. Slice-of-life pieces can be quite effective IF they are short — but frankly, in my opinion, most of what goes on in the real world doesn’t rise to the standards of literature

Far, far better to apply your unique worldview and scintillating ability with words to create something BETTER than reality, I say.

In that spirit, let’s look at that sentence structure beloved of the real-life speaker, X happened and Y happened and see if we can’t improve upon it, eh?

If this structure is used sparingly, it can work very well indeed — but its advocates seldom seem to be able to restrain themselves. Let’s take a peek at several sentences of this type in a row, to see why it might annoy your garden-variety Millicent at the end of a long, hard day of rejection:

Esmeralda blanched and placed her lily-white hand upon her swiftly-beating heart. Rolando nodded with satisfaction and strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously and continued to move closer.

See what I mean? Although each of these sentences is in fact grammatically correct, and this structure reads as though it is merely echoing common spoken English, it’s also pretty much the least interesting way to present the two acts in each sentence: the and is, after all, simply replacing the period that could logically separate each of these actions.

By contrast, take a look at how varying the sentence structure and adding the odd gerund livens things up:

Esmeralda blanched, her lily-white hand clutching her swiftly-beating heart. Rolando strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously, moving closer every second.

Easier to read, isn’t it? Admittedly, the prose is still pretty purple — or at least flushing lilac — but at least the paragraph is no longer jumping up and down, screaming, “My author knows only one way to structure a sentence!”

Most agents, editors, and contest judges would agree with the paragraph’s assessment, alas. They tend to have a very low tolerance for over-use of this particular sentence structure.

Seriously. I’ve seen pens poked through manuscripts at the third instance of this kind of sentence within half a page.

While you are self-editing, then, it’s a dandy idea to rework ANY sentence in which and appears more than once. (Hey, where have I heard that trenchant advice before?) Chances are high that such a sentence will be a run-on, in any case:

In avoiding the police, Zelda ran down the Metro stairs and out onto the platform and into the nearest train.

This is a classic run-on: too much information crammed into a single sentence, facilitated by those pesky conjunctions.

Some writers, of course, elect to include run-on sentences deliberately in their work, for specific effect: to make the narrator sound less literate, for instance, or more childlike, or to emphasize the length of a list of actions the protagonist has to take to achieve a goal. Or sometimes, the point is to increase the comic value of a scene by the speed with which it is described, as in this excerpt from Stella Gibbons’ classic comedy, COLD COMFORT FARM:

He had told Flora all about his slim, expensive mistress, Lily, who made boring scenes and took up the time and energy which he would much sooner have spent with his wife, but he had to have Lily, because in Beverly Hills, if you did not have a mistress, people thought you were rather queer, and if, on the other hand, you spend all your time with your wife, and were quite firm about it, and said that you liked your wife, and, anyway, why the hell shouldn’t you, the papers came out with repulsive articles headed “Hollywood Czar’s Domestic Bliss,” and you had to supply them with pictures of your wife pouring your morning chocolate and watering the ferns.

So there was no way out of it, Mr. Neck said.

Quite the sentence, eh? (Not the second, silly — the first.)

I’m going to part company with pretty much every other editor in the world for a moment and say that I think that a writer can get away with this sort of run-on every once in a while, under three very strict conditions:

(1) IF it serves a very specific narrative purpose that could not be achieved in any other manner (in this example, to convey the impression that Mr. Neck is in the habit of launching into such diatribes on intimate topics with relative strangers at the drop of the proverbial hat),

(2) IF it achieves that purpose entirely successfully (not a foregone conclusion, by any means), and

(3) If the writer chooses to do this at a crucial point in the manuscript, s/he doesn’t use it elsewhere — or at least reserves the repetition of this choice for those few instances where it will have the greatest effect.

Why minimize it elsewhere? Well, as we have seen above, this device tends to create run-on sentences with and…and…and constructions, technically grammatical no-nos. YOU may be doing it deliberately, but as with any grammatical rule, many writers who do not share your acumen with language include them accidentally.

Let me ask you this: how is a speed-reading agency screener to tell the difference between a literate submitter pushing a grammatical boundary on purpose and some under-read yahoo who simply doesn’t know that run-ons are incorrect?

Usually, by noticing whether the device appears only infrequently, which implies deliberate use, or every few lines, which implies an ingrained writing habit.

I’ve sensed disgruntled rumblings out there since point #3. “But Anne,” I hear some of you protest, “I read a great deal, and I see published literary fiction authors break this rule all the time. Doesn’t that mean that the language has changed, and people like you who go on and on about the rules of grammar are just fuddy-duddies who will be first up against the wall come the literary revolution?”

Whoa there, disgruntled rumblers — as I believe I have pointed out before, I invented neither the rules of grammar nor the norms of submission evaluation. If I had, every agency and publishing house would post a clear, well-explained list of standard format restrictions on its website, along with explanations of any personal reading preferences and pet peeves its staff might happen to have. Millicent would be a well-paid, under-worked reader who could spend all the time she wanted with any given submission in order to give it a full and thoughtful reading, and the government would issue delightful little checks to compensate writers for all of the time they must now spend marketing their own work.

Clearly, then, these matters are not under my personal control, so kindly take me off your literary hit lists.

Even in literary fiction, it’s rather dangerous to include grammatically incorrect sentences in a submission — to someone who hasn’t read more of your work than the first few pages of your manuscript, it’s impossible to tell whether you are breaking the normal rules of grammar in order to create a specific effect, or because you just don’t know the rule. If an agency screener concludes that it’s the latter, she’s going to reject the manuscript, almost invariably.

Thus, unless you are getting a valuable effect out of a foray into the ungrammatical, it’s best to save your few opportunities to do so intentionally for when it serves you best. At the very least, make sure that two such sentences NEVER appear back-to-back, to avoid your submission’s coming across as the work of — gasp! — a habitual runner-on.

Sometimes repeated ands work rhythmically, but to an agent or editor, a manuscript that employs X happened and Y happened as its default sentence structure it just starts to read like uncomplicated writing — which makes it less appealing to the pros.

The other common conclusion trained eyes often draw from over-use of this technique smacks of either the narrative’s trying to rush through an otherwise not very interesting series of events.

This is not always a fair assessment, of course. But when you do find patches of ands in your text, step back and ask yourself honestly: “Do I really NEED to tell the reader this so tersely — or all within a single sentence? Or, indeed, at all?”

“Perhaps,” (you’re still speaking to yourself here, in case you were wondering) “I could find a way that I could make the telling more interesting by adding more detail? I notice by reading back over the relevant paragraphs that my X happened and Y happened sentences tend to be light on telling specifics.”

My, you’re starting to think like an editor, reader.

Since your revision eye is getting so sophisticated, let’s consider the opposite possibility: in paragraphs where ands abound (or, sacre bleu, sentences!), are you rushing through the action of the scene too quickly for the reader to enjoy it? Are some of those overloaded sentences cramming four or five genuinely exciting actions together — and don’t some of these actions deserve their own sentences?

Or, to put it a bit more bluntly, is the repeated use of and in fact your manuscript’s way of saying COME BACK AND FLESH THIS OUT LATER?

C’mon, admit it — almost every writer has resorted to this device at the end of a long writing day, haven’t we? Or when we have a necessary-but-dull piece of business that we want to gloss over in a hurry?

You thought you were the only one who did this, didn’t you?

Don’t be so hard on yourself — writers do this all the time. When the point is just to get lines down on a page — or to get a storyline down before the inspiration fades — X happened and Y happened and Z happened is arguably the quickest way to do it.

It’s a perfectly acceptable time-saving strategy for a first draft — as long as you remember to go back later and vary the sentence structure. Oh, and to make sure that you’re showing in that passage, not telling.

When we forget to rework these flash-written paragraphs, the results may be a bit grim.

Relying heavily on the and construction tends to flatten the highs and lows of a story: within them, actions come across as parts of a list, rather than as a sequence in which all the parts are important.

Which — you guessed it — encourages the reader to gloss over them quickly, under the mistaken impression that these events are being presented in list form because they are necessary to the plot, but none is interesting enough to sustain an entire sentence.

Which is not exactly the response you want your sentences to evoke from an agency screener, right?

When in doubt, revise to minimize the ands. I hate to come down unfairly on any grammatically correct sentence, but the fact is, the X happened and Y happened structure is just not considered very literary in the business. So the automatic assumption if it shows up too much is that the material covered by it is to be read for content, rather than beauty of prose.

To quote Millicent’s real-life dialogue: “Next!”

I would prefer to see your submissions getting long, luxurious readings, on the whole, not getting knocked out of consideration over technicalities. I’m funny that way.

Keep up the good work!

(PS: the lovely picture above appears courtesy of the fine folks at FreeFoto.com.)