Part XXVI of Pet Peeves on Parade, and part IV of Structural Repetition, and other excuses stockpile a whole lot of ands. Because you wouldn’t want to run out or anything.

Are your fingers stained with highlighter ink, campers? I hope they are: last time, I urged you to scan your submission pages — in particular, the first five, the opening chapter, or all of a contest entry — for over-use of the words and, but, and then; the average manuscript submission is positively peppered with ‘em. Since our old pal, Millicent the agency screener, sees these words so very often, I suggested that you print out these pages and highlight these words throughout, so that you might get a sense of just how often you tend to utilize them.

As I hope you have seen for yourselves, once you started marking, it was pretty darned astonishing just how often those conjunctions leapt off the page, wasn’t it? Or they would have, had you flung yourself into this nit-picky task wholeheartedly — as opposed to, say, devoting yourselves the activities of normal people.

The typical writerly reaction, though, is somewhere in between: glancing over those pages with an initially willing mind, but throwing up one’s hands in despair three buts in. “What was Anne thinking,” I sensed some of you muttering yesterday, “to advise such a time-consuming (and potentially ink-consuming) exercise? Doesn’t she realize that most of us have to fight in order to carve out time to write — and even if I happened to be one of the happy few who don’t, sunny days relatively rare in the Pacific Northwest?”

Well, in the first place, summer in Seattle is frequently beautiful; the popular belief that it rains here non-stop is a myth. In the second place, I do realize just how important your time is to you — which is precisely why I’m advising you to invest a little time now in exchange for not having scads of your time wasted later in the submission process.

Think of it this way: as those of you who have submitted to an agency or entered a contest lately are already well aware, preparing your pages and sending them off is quite time-consuming, and, if you’re like most aspiring writers, even more energy-consuming. We also all know, I hope, that the cleaner your manuscript — that’s industry-speak for pages free of basic spelling, grammar, formatting, and logic problems, in case anyone was wondering — the less likely it is to push Millicent’s rejection buttons. The same holds true for her pet peeves: the better revision job you do, the less likely your pages are to come winging back in your SASE, accompanied by a form-letter rejection. Or, as is increasingly common, for them not to come back at all.

Sense where I’m heading with this? Getting caught in a submission-rejection cycle generally ends up eating far, far more of a writer’s valuable time than an intensive revision aimed at weeding out rejection triggers would take.

Or, to put it more bluntly, aspiring writers who routinely send out first drafts, especially — sacre bleu! — ones that have neither been proofread or spell- and grammar-checked — because they are impatient to get their books published generally have a harder time landing an agent, winning a contest, and/or pleasing an editor than writers patient enough to polish their work prior to submitting it.

Given such a noble goal, concentrating upon something as basic as whether your narrative relies too heavily upon and, but, and then may not seem as if it would make a big difference, but actually, out of all the potential problems a self-editor might discover in a Frankenstein manuscript, overused conjunctions are some of the easiest to catch and fix. And the pay-off can be tremendous: quick-reading agency screeners, editorial assistants (who screen submissions for editors) and contest judges are routinely ordered to subtract points (Brownie in the case of the former two, literal in the case of the contest submission) for grammatical errors — and word repetition is always high on their penalty list.

As is that habitual roommate of conjunctions, the run-on sentence. Not sure what one looks like? Here’s a lulu, presented for your reading pleasure in its natural habitat, the manuscript page.

Laugh if you like, but would it astonish you to learn that this is shorter than some of the sentences my aged eyes have beheld in manuscripts and contest entries? I’ve seen sentences that have dragged on for more than a page; I once spotted one that expected the reader to follow its twists and turns for almost three.

Although I have apparently lived to tell about it, there can be no legitimate justification for dragging the reader through such an epic. The best possible outcome — which the author does not deserve — is that perhaps no one will notice that there was only a single period in those 21 lines of text, but that’s not what’s likely to happen at submission time. Since text like this simply shouts at Millicent, “Hey, this writer didn’t bother to reread this paragraph in hard copy after writing or revising it; clearly, these pages are not ready for professional perusal,” including such a lengthy run-on produces prose that is in effect self-rejecting.

I sense that those of you fond of the occasional multiply compound sentence longing to equivocate. “But Anne,” run-on huggers point out, “couldn’t embracing this sort of conversational-style sentence be a daring authorial choice? Could it not, in fact, be a characteristic of a distinctive voice?”

Well, it could, if it were handled skillfully — but in 99.99% of cases, extended run-ons are not interesting enough to be honored with the name of style. Run-on sentences, much like the repetition of a favorite word or phrase, virtually never strike Millicent as the result of well-thought-out and purposeful writerly strategy. Or, if a pro does think it is purposeful it’s poor strategy: “I know! I’ll bore my reader and annoy Millicent by making her read the sentence twice in order to understand it!”

Seem like a harsh assessment? It isn’t, particularly, if you consider that from an agent or editor’s perspective, it’s the writer’s job to write not only clearly, but beautifully, adhering to the basic rules of grammar. Expressing a sentiment well and without gaffes is, after all, the minimum requirement for professional writing, not an optional extra.

To Millicent, then, a run-on sentence tends to look like an instance of the writer’s just being in too much of a hurry to write well — and in practice, she’s frequently right about that. It’s not at all uncommon for an aspiring writer to whip out a scene or paragraph in a rush, fully intending to come back and flesh out those not-especially-stirring sentences when he has more time. Astonishingly often, though, that mythical day with 27 hours — 24 for normal life, plus an extra 3 for revision — never manages to roll around. The writer forgets all about those original noble intentions and moves on.

Multiply that by a few hundred times, and you’ll end up with the type of submission that makes Millicent shake her head over a good premise gone awry: a typo-filled, run-on laden series of scenes dimly indicating what an intriguing story this might be four or five drafts down the line. A half-century ago, an agent or editor might have taken on a project like this, seeing that with proper professional guidance, the writer might polish it up into something genuinely fine. Today, however, our Millie sees just too many technically perfect submissions to worry much about rejecting those that still need work.

You’d be surprised, I suspect, at just how clearly a page featuring a couple of run-ons telegraphs to the pros that this manuscript could use more revision. Run-ons are usually hodgepodges of several distinct sentences’ worth of material, rubber-cemented together with our old pals and, but, and then. Look how obvious it is that the writer was in a rush:

Eighteen thousand citizens rushed as one to the city’s walls and stared over the side, but they could not possibly have anticipated what they would find there and gasped accordingly, then began to shout.

Essentially, this is a summary, not a description. We can see where and how this hefty hunk of prose could be chopped up into interesting, specific detail-filled individual sentences, but for reasons best known to herself, the writer has elected not to do so.

Once a reader has developed the editorial eye to see what could have been, other types of compound sentence also seem ripe for closer scrutiny. Take, for instance, the 19th century prose practice of stringing clause after clause together with whiches and whos and wheres:

Petunia, who was desperate, ran along the docks where Ambrose had vanished. She turned right every time she came to a curve, which was easier than making a new decision each time, but which left her wondering after about fifteen minutes if the awnings she was passing were the same ones she had passed earlier.

Modern style cries out for fewer of those clunky asides. And don’t even get Millicent started on the species of run-on that’s simply the result of a writer’s apparently being unsure whether it’s okay to replace a period with a comma in order to speed up the reader’s sense of what’s going on.

Sebastian hesitated before marching through the doorway, the scent of gunpowder coming through it was so strong.

The answer, Millie would like me to tell you, is no: it’s never correct to slap two complete sentences together with a comma. That last example should have been cut in half with a period:

Sebastian hesitated before marching through the doorway. The scent of gunpowder coming through it was so strong.

Or a semicolon:

Sebastian hesitated before marching through the doorway; the scent of gunpowder coming through it was so strong.

Even with the punctuation corrected, these sentences still might raise Millicent’s ire. Any guesses why?

Give yourself a gold star with almond clusters if you instantly leapt to your feet, shouting, “So is comparative! It must take a modifier!” A so statement logically requires a that follow-up. Voilà:

Sebastian hesitated before marching through the doorway. The scent of gunpowder coming through it was so strong that it made him gag.

Why, yes, I did add some extra information to this sentence that might not have been part of the author’s original intention; editors are notorious for doing that, in the interests of rendering the prose clearer. I could also have revised these sentences without changing the meaning. What the author probably meant (“And should have taken the time to say,” sniffs Millie) was this:

The scent of gunpowder wafting through the doorway was so strong that Sebastian hesitated before marching through it.

This version also, I am glad to report, neatly side-steps the other professional readers’ pet peeve in the original, presenting cause and effect out of chronological order. Think about it: how likely is it that Sebastian would have hesitated before he smelled the gunpowder? Isn’t it far more plausible that he paused because it wafted toward him and he drew a conclusion from it about what probably lay beyond that doorway?

I hate to be the one to break the sad news, but the writer of the first version probably thought she had said precisely that. She was just in too much of a hurry to go back and make sure a reader would take that meaning from it.

Starting to get the hang of reading a run-on for clarity and grammar? Good. Now — and only now — are we ready to talk about style.

Let’s face it, none of these are particularly pretty sentences. The word choice is not especially interesting; they reveal little about the physical environment, Sebastian’s character, or even the danger into which he is almost certainly walking. As such, the phrasing takes a potentially suspenseful moment and squashes the reader’s sense of anticipation.

So I ask you: as a writer, how likely would you be to do any of those things on purpose, in the name of delightful literature or compelling storytelling?

Millicent doesn’t think it’s likely, either. No professional reader would mistake any of these examples for a daring stylistic experiment; they are not polished or interesting enough to prompt the reader to try to figure out if the writer had some clever reason for presenting these facts in this manner.

Nor — dare I say it? — are these sentences original enough to set off the High Literary Stylings siren in Millicent’s brainpan. That may well come as something of a surprise to creators of the variety of first-person narration whose primary stylistic recommendation is that it reads like everyday speech. The most popular means of pulling that off, as we have discussed earlier in the Pet Peeves on Parade series, is to replace grammatically-necessary periods with the ands, buts, and thens that grant a false consecutiveness to verbal storytelling.

My name is Louisa, and I am seven years old — and already, I see your eyes glazing over, dismissing anything I might have to say as the mere ramblings of a child. But I was there when the schoolhouse caught fire, there when the mayor decamped with the last dime of the town’s funds, there when the crocodiles began to squirm up from the riverbed to dine on the dear departed that no one was around anymore to bury. Then the vultures came, and still, I was there.

It’s not an uncompelling voice — although of the scores of professional readers’ pet peeves, few will cause the average Millicent to mutter, “Next!” faster than the grade-school storytelling expedient of having the narrator say right off the bat My name is X and I am # years old — but honestly, any originality the reader might spot in it comes from the details, not the echo of run-on filled normal speech. (“And even if it did,” Millicent adds, “this is a far cry from a seven-year-old’s voice.”)

Don’t believe me? Okay, here is the same passage, stripped of run-ons and reworked to minimize conjunctions.

My name is Louisa. I am seven years old. Already, I see your eyes glazing over, dismissing anything I might have to say as the mere ramblings of a child, but I was there when the schoolhouse caught fire. I was there when the mayor decamped with the last dime of the town’s funds. I was there when the crocodiles began to squirm up from the riverbed to dine on the dear departed that no one was around anymore to bury. When the vultures came, I was still there.

A forest of hands sprouted throughout the course of that last paragraph; I couldn’t be more delighted. “But Anne,” shout those of you who have been paying attention in recent weeks, “isn’t this opening a prime example of the oh-so-common invocatory rhythm achieved through word and phrase repetition that we have already identified as one of Millie’s pet peeves? I can’t believe that you edited the original without addressing that problem.”

Hey, it’s not the editor’s job to rewrite the author’s voice choices; all we do is flag what’s not working and suggest how to kick-start that story’s engine. It’s the writer’s job to decide how the words should appear on the page, right?

Admit it: you’re happy that’s the case. You wouldn’t really like somebody else to set your literary voice for you, would you?

So I leave to you the meaty creative challenge of making your prose sound like you at your best. For the moment, my goal is far less lofty: I want to help you be able to spot a run-on when you encounter it in the wild.

Here’s a good preliminary rule of thumb: if you can’t say any given sentence within a single breath, it might be a run-on. (Yet another great reason to read your manuscript OUT LOUD, IN HARD COPY, and IN THEIR ENTIRETY before you submit, eh?) Another classic tip-off: where run-ons gather, there will be ands aplenty also, typically.

So whip out your marked pages from last time, please, and let’s observe the reproduction habits of and. If you’re like most writers, your marking project probably revealed four major patterns of andusage:

(1) In lists.

Remember, not all lists take the form of Kamala had three novels, two memoirs, and a dictionary in her backpack. Keep an eye out for lists consisting of named emotions, which often appear in groups (Kamala felt angry, betrayed, and hurt), too-hurried accounts of activity (Kamala went to the store, searched fruitlessly for spumoni ice cream, ran down the block to her favorite trattoria, and begged them to sell her a couple of scoops on the sly.), as well as lists inadvertently formed by the use of and for emphasis (Kamala felt angry and betrayed and hurt and, consequently, ravenous for spumoni ice cream.).

Don’t think of all of those types of sentence as lists? Millicent does, believe me — and are lists really the most interesting way to present your protagonist’s activities? Ever?

(2) In the immensely popular X happened and (then) Y happened sentence structure.

We’re all familiar with this one, right? Edward ate his pizza and drank his Coke. The sky turned brown, and all of the birds stopped singing. I could go on like this all night, and if my guests were not flipping impatiently through magazines, I would.

There’s nothing wrong with this structure per se — but used too often, or too close together, all of those ands can start to feel quite repetitious quite fast. As can…

(3) In the almost-as-popular trilogy structure: Someone did X, Y, and Z. Alternatively, it may appear as Someone did X and Y, then Z.

Yes, either of these structures could be considered a list (as in, Christos cried, rolled over, and bawled some more.), but since most aspiring writers simply like the three-beat rhythm, I prefer to talk about it as a separate sentence type. Again, there’s nothing wrong with this structure if used sparingly, but all too often, the three-beat descriptive sentence becomes the default in the manuscript.

The resulting repetition can feel quite percussive to a reader, even if the actual sentence structure varies:

Christos felt betrayed, confused, and, oddly enough, desperate for some spumoni ice cream. Puzzled, he wandered into his kitchen, yanked open the freezer door, and pondered his ice cream supply. Wait — what had happened to his long-hoarded supply? Suddenly, it came to him: he’d heard Kamala rooting about in here in the wee hours, rattling bowls and clattering spoons. He felt angry and betrayed and hurt.

See how predictable those threesomes became, even in the space of one short paragraph? Imagine how Millicent feels when confronted with pages upon pages of them — which happens more than any of us would like to think.

(4) In complex descriptions.

Descriptions with multiple elements almost always contain at least one and, particularly if the sentence is passive: Germaine was tall and lanky. Again, this is technically a list (albeit a short one), but few writers would think of it as one.

Pay close attention to descriptive passages for another common and bugbear: sentences containing more than one of them. A multiple-and sentence is to most professional readers what a red flag is to a bull, and yet they are so easy to produce almost inadvertently if a writer is trying to cram too much description into a single sentence. As in:

Germaine was tall and lanky, with long, straight hair that came down to her lean and boyish hips. She liked to dress in black-and-white dresses, the kind that confused the eye if she walked past a strobe light, and skin-tight leather boots. She also favored tight jeans and tank tops, except of course for days she knew she would be running into Kamala and joining her on a spumoni ice cream run.

Quite a lot of ands, isn’t it? As strange as it may seem, most writers have an infinitely easier time spotting this kind of repetition in other people’s work; in their own, they tend to concentrate on the description, not the repetitive structure.

Complicating matters is the fact that often, two or more of these four types of and usage will appear within a single paragraph — or even a single sentence. Not sure what that might look like in practice? Okay, see if you can ferret out instances of all four kinds in this sterling piece of prose:

Abe took a deep breath and ran his palms over his face. He yanked his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow, folded it twice, and stuffed it back into his coat. A motley assortment of trash caused his hand to recoil: cast-off candy bar wrappers, half-sucked lollipops hastily stuck back into their wrappers, waiting for later, and both red and black licorice whips. Sure, he was a sane and sober adult now. Outwardly composed, he twisted his face into a smile, swallowed a groan, and extended his hand to Emile.

How did you do? Admittedly, we’re looking for something a bit subtle here. Although the types of repetition used in this example may sound merely chatty when read out loud, they would come across as structurally redundant on the page. Even minor word repetition can set editorial teeth on edge, because editors — like other professional readers — are trained to zero in on redundancy.

To see how this orientation might affect how one reads, let’s look at this same paragraph with a screener’s heightened antennae:

Abe took a deep breath and ran his palms over his face. He yanked his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow, folded it twice, and stuffed it back into his coat. A motley assortment of trash caused his hand to recoil: cast-off candy bar wrappers, half-sucked lollipops hastily stuck back into their wrappers, waiting for later, and both red and black licorice whips. Sure, he was a sane and sober adult now. Outwardly composed, he twisted his face into a smile, swallowed a groan, and extended his hand to Emile.

See? The repetition of all those ands can be downright hypnotic — the percussive repetition lulls the reader, even if the action being described on either end of the and is very exciting indeed.

There’s a reason for that, you know, and if you’ve been paying attention throughout this series, it has probably already occurred to you. The swiftly-scanning eye’s automatic tendency is to jump between repeated words on a page, in very much the manner that a CLUE player might move his piece from the study to the kitchen via the secret passage about which everyone in the game is evidently quite well-informed. (Hey, it’s an editor’s job to demand precise word usage.)

The result: Miss Scarlet did it in the kitchen with the revolver.

Oops, wrong chain of events: the result relevant for our purposes is a submission page read far, far more quickly than the average submitter might wish. Not only by Millicent and her ilk, but by the average reader as well.

The best way to avoid triggering this skimming reaction is to vary your sentence structure. A great place to start: scanning your manuscript for any sentence in which the word and appears more than once. Take a gander:

Ezekiel put on his cocked hat, his coat of many colors, and his pink and black checked pantaloons. And he dusted himself out before heading toward the big top, clown shoes a-flopping.

Did your eye catch the subtle problem here? No? Let’s take a second look, this time as Millicent would see it:

Ezekiel put on his cocked hat, his coat of many colors, and his pink and black checked pantaloons. And he dusted himself out before heading toward the big top, clown shoes a-flopping.

All of the ands are serving slightly different functions here, two of which would be perfectly valid if they stood alone: the first is connecting the second and third items in a list; the second is connecting two characteristics in a shorter list. And the third — as in this sentence — is the kind of usage we discussed last time, where a conjunction gives a false sense of chatty consecutiveness between the first sentence and the second.

When I first began writing that last paragraph, I didn’t intend it to be an illustration of just how visually confusing word repetition may be on the page — but as I seemed to be succeeding brilliantly at doing just that, I figured I’d just run with it.

You’re welcome. Let’s highlight the repetition here, to determine precisely why a skimming reader might find it confusing:

All of the ands are serving slightly different functions here, two of which would be perfectly legitimate if they stood alone: the first is connecting the second and third items in a list; the second is connecting two characteristics in a shorter list. And the third — as in this sentence — is the kind of usage we discussed yesterday, where a conjunction gives a false sense of chatty consecutiveness between the first sentence and the second.

Is your brain in a twist after all of that percussive redundancy? Never fear — the twin revising morals are actually quite simple to remember:

(1) Every writer, no matter how experienced, will occasionally write a poorly-constructed sentence or paragraph, so there will never be a point where any of us can legitimately assume that our first drafts require no revision whatsoever, and

(2) Just because a given word may carry more than one meaning — or, as here, refer to distinct categories of things — that fact doesn’t nullify the effects of repetition upon the reader.

Because we writers tend to think of words according to their respective functions within any given sentence, rather than as images on a page, these kinds of repetition often flies under our self-editing radars. Unless one is looking for it specifically, it’s easy to, well, overlook. Thus my urging you to whip out the highlighting pens, in case you were wondering. I’m just trying to make repetition jump out at you as garishly as it does to those of us who read for a living.

Incidentally, words that sound alike but are spelled differently — there, they’re, and their, for instance — often strike readers as repetitious if they are used in too close proximity to one another. For example:

“They’re going to look for their zithers in there,” Thierry pointed out.

Why might this sentence give a reader pause? Because many pronounce words silently in their heads while they scan. Yet another great incentive to read your manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD, eh? It’s the best way to replicate the silent reader’s mental experience.

Next time, I shall delve into some other problems that commonly arise from an over-reliance upon ands. In the meantime, in between time, try to minimize word and sentence structure repetition, and keep up the good work!

Pet peeves on parade, part XXV, structural repetition, part III, and the role of pretzels in a well-rounded breakfast

This morning, I was puzzled into wakefulness by my fiancé’s waving a soy latte and a freshly-baked pretzel under my nose. A new German bakery has opened in our neighborhood, and he’s terrified that it will go out of business without our daily support. A reliable source for Black Forest cake is not to be taken for granted, after all.

Now, I’m as fond of a good pretzel as the next person, but at 8 a.m., I must confess, mustard-laden food options are generally not the first to pop to mind. Nor is rock salt my favorite pillow covering, given my druthers.

Rick, however, subscribes to the surprisingly pervasive school of thought that holds what a person has said she liked once, ever, will come as a pleasant surprise to receive at any randomly-selected moment for the rest of her life. Or so I surmise from the fact that he could not resist pointing out that I had apparently enjoyed a remarkably similar pretzel only two afternoons before.

Which, of course, would render it even less likely that I would want another one now. The pretzel was turning out to be pretty tasty, though, so rather than take the time to explain at length that piling on more of a good thing does not necessarily improve, well, anything, I decided it would be the better part of valor to thank him graciously and bear my usual breakfast into a more appropriate environment for consuming something warm and squishy. As I fled, I marveled at how, once again, the muses had tumbled all over themselves to provide me with a delightfully apt metaphor for a craft issue you and I were already discussing.

Oh, hadn’t the pretzel-paragraph construction parallel hit you instantly? Allow me to recast it as a self-editing aphorism for the ages, then: what might read beautifully as a stand-alone sentence may not work as well within the context of a page of text. Varying word choice and sentence structure will usually provide the reader with a more pleasurable reading experience than a narrative’s insisting that if something looked good on the page once, it will necessarily look great if it’s repeated.

For the last couple of posts, I’ve been talking about how professional readers tend to respond to repetition in submissions. (To summarize their reaction for those of you joining us mid-series: not at all well.) I cannot in good conscience round off my lobbying for reduced repetition in your manuscripts, though, without discussing those ever-popular transients passing through Conjunction Junction: and, but, and then.

Positive legions of hands shoot into the air. Yes, grammar mavens? “But Anne,” you point out, and rightly so, “then isn’t a conjunction! Why, then, would you include it in your discussion of conjunctions, when there are so many legitimate conjunctions — yet, for instance — deserving of your august scrutiny?”

Quite right, hand-wavers: when used properly, then isn’t strictly speaking a conjunction. However, enough writers are using it these days as if it were a synonym for and in a list of actions (as in The Little Red Hen kneaded the bread, baked it, then fed it to her forty-seven children.) that I feel justified in — nay, compelled to — treat it as such for the purposes of our ongoing discussion of repetitive sentence structures and their predictably negative effect on Millicent the agency screener’s weary peepers.

Language does grow and change, of course. Back in the bad old days, when dinosaurs roamed the earth Roosevelts were presidents Dorothy Parker was still speaking to Ernest Hemingway editors like Maxwell Perkins called the shots in the publishing world, it was considered hugely improper to begin any sentence with and, but, or then; amongst the literate, these words were purely intra-sentence phenomena. As my Uncle Alex (a fairly well-known SF short story writer in the 1950s, an editor at the LA Free Press, and a stickler for grammar for his entire life) used to scrawl in the margins of letters I had written when he returned them to me, a conjunction, by definition, connects one part of a sentence to another.

“Therefore,” he would ink in large letters, “a conjunction may not begin a sentence. How’s your mother?”

There are easier things than growing up in a family of writers and editors. Toward the end of his long, colorful, and occasionally scurrilous life, Uncle Alex was even known to shout grammatical advice at the TV screen when newscasters –sacre bleu! — began their sentences with conjunctions. And really, who could blame him?

(I couldn’t resist. Hey, a pretzel is not exactly the breakfast of champions.)

Time and the language have been marching merrily onward, however, and at this point in North American history, it’s considered quite acceptable to begin the occasional sentence with a conjunction. I do it here all the time. So do most bloggers, journalists, and columnists: it’s a recognized technique for establishing an informal, chatty narrative voice.

That mournful crashing sound you just heard was Uncle Alex stomping his feet on the floor of heaven, trying to get all of us to cut it out, already, but there can be perfectly legitimate stylistic reasons to open a sentence with a conjunction. They can, for instance, be very valuable for maintaining an ongoing rhythm in a paragraph. Like so:

Ghislaine spotted the train pulling into the station. But would Arbogast be on it? He would — he had to be. And if he wasn’t, well, she was just going to have to call him to find out why. Or not. Anyway, she wasn’t going to waste her energy speculating on what would be a moot point the second Arbogast stepped off that train and caught her in his arms.

As Uncle Alex would undoubtedly have been the first (and last, and middle) to tell you, classic English grammar has an elegant means of preventing those conjunctions from hanging out at the beginnings of those sentences: by eliminating the periods and replacing them with commas. The result would look a little something like this:

Ghislaine spotted the train pulling into the station, but would Arbogast be on it? He would — he had to be, and if he wasn’t, well, she was just going to have to call him to find out why — or not. Anyway, she wasn’t going to waste her energy speculating on what would be a moot point the second he stepped off that train and caught her in his arms.

To old-fashioned eyes, this paragraph’s meaning is identical to the first; it is merely cleaner grammatically. However, I suspect that most current readers of English prose would recognize a substantial difference in the rhythm. A period is, as the English like to call it, a full stop; a comma, on the other hand, indicates a pause. A dash indicates a slightly longer and more pointed pause. To this millennium’s sensibilities, the first example has a choppiness, a breathless quality that conveys the subtle impression that Ghislaine’s breathing is shallow, her pulse racing.

The periods my uncle would have forbidden, then, could be regarded as subtle narrative indicators of protagonist stress. At least to those in the habit of breaking paragraphs down into their constituent parts to see what their functions are. Like, say, most of us who read manuscripts for a living.

Before we leave that last set of examples, did you happen to notice any other editorial pet peeves in that first? No? Okay, let me whip out my editorial machete pen and remove a couple of Millicent’s pet peeves. Rather than merely noticing that this third version reads better, why not challenge your revision skills by trying to figure out why?

Ghislaine spotted the train pulling into the station, but would Arbogast be on it? He would — he had to be, and if he wasn’t, well, she was just going to have to call him to find out why. Right now, she wasn’t going to waste her energy speculating on what would be a moot point the second he stepped off that train and caught her in his arms.

How did you do? Take a nice, shiny gold star from petty cash if you immediately cried, “Why, word repetition is word repetition, Anne — which is why you removed the second Jason in the paragraph.” Stack another star on top of the first if you added, “Anyway is often how speakers inform hearers that they’ve digressed from their point. Is there a reason the narrative should go out of its way to inform readers that it has digressed?” And give yourself three more stars if you have gotten in touch with your inner Millicent sufficiently to have mused, “You know, to find out why — or not is conceptually unnecessary. And would the paragraph lose any actual meaning if I cut or not?”

I hear those of you who did not shout any of those three observations muttering under your collective breath, and you’re quite right: this is nit-picky stuff. Both good writing and professional presentation are made up of lots and lots of nit-picky stuff. Your point?

While you’re trying to come up with a sufficiently scathing comeback for that one, let’s tie the anyway revelation (i.e., that what’s considered acceptable in everyday speech may not work so well in a narrative voice on paper, even if it happens to be in the first person), back to our ongoing discussion of and and but. Since conjunction-opened sentences can sometimes mirror actual speech better than more strictly grammatical ones, the former can be a positive boon to dialogue.

Seem paradoxical? Okay, contrast this sterling exchange:

“And I tell you, Spencer, it was eerie. I’m never going back into that deserted house again. And that’s final.”

“But Yvette, you’re backing recklessly away from the conventions of our chosen genre! You’re a scantily-clad, unattached female who screams easily, often while tossing your dreamy long red (or blonde) hair. You are fleet of foot in the face of danger. Yet you are astonishingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingénue sidekicks never seem to twist their ankles navigating. And, naturally, you are entirely unarmed. Therefore, you must return to face the danger that any sane person would take extreme measures to avoid!”

“Or what? Or you’re going to turn me in to the Stereotype Enforcement Police?”

“Or else, that’s all.”

“Fine. Then give me the key to the tool shed.”

“If you insist. But don’t come crying to me when an axe comes crashing through your door at the closed-for-the-season hotel.”

with the same dialogue after the conjunctions have been tucked into the middle of the sentences:

“I tell you, Spencer, it was eerie. I’m never going back into that deserted house again. That’s final.”

“Yvette, you’re backing recklessly away from the conventions of our chosen genre! You’re a scantily-clad, unattached female who screams easily, often while tossing your dreamy long red (or blonde) hair. You are fleet of foot in the face of danger, yet surprisingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingénue sidekicks never seem to twist their ankles navigating. Naturally, you are entirely unarmed. Therefore, you must return to face the danger that any sane person would take extreme measures to avoid!”

“Is there some penalty attached to my refusal? Are you going to turn me in to the Stereotype Enforcement Police?”

“You must, that’s all.”

“Fine. Give me the key to the tool shed.”

“If you insist, but don’t come crying to me when an axe comes crashing through your door at the closed-for-the-season hotel.”

The difference is subtle, but to a professional reader, it would be quite evident: the second version sounds more formal. Partially, this is a function of the verbal gymnastics required to avoid the colloquial Or what? Or else.

But these are not the only ways aspiring writers utilize sentence-beginning conjunctions in narrative prose, are they? As anyone who has ever been trapped in a conversation with a non-stop talker can tell you, beginning sentences with conjunctions gives an impression of consecutiveness of logic or storyline. (As was the case with the first sentence of this paragraph, as it happens.) Even when no such link actually exists, the conjunctions give the hearer the impression that there is no polite place to interrupt, to turn the soliloquy-in-progress into a dialogue.

We all encounter this phenomenon so often in everyday life that giving a concrete example seems a tad, well, repetitive. If you feel that your life lacks such monologues, though, try this experiment the next time you’re at a boring cocktail party. (They’re coming back, I hear.)

(1) Walk up to another guest, preferably a stranger or someone you do not like very much. (It will soon become apparent why that last trait is desirable.)

(2) Tell a lengthy anecdote, beginning every sentence with either and, but or then. Take as few breaths as possible throughout your speech.

(3) Time how long it takes a reasonably courteous person to get a word in edgewise.

Personally, I’ve kept this game going for over 15 minutes at a stretch. The imminent threat of fainting due to shortness of breath alone stopped me.

Which is, in case you happen to be writing a book about such things, why panhandlers and telemarketers so often speak for minutes at a time in what seems to the hearer to be one long sentence: run-on sentences discourage interruption. Almost invariably, this phenomenon is brought to you by the heavy lifting skills of and, but and then.

Perhaps for this reason, aspiring writers just love to tuck conjunctions in all over the place: it can create the impression of swift forward movement in the narrative. Or, even more often, to establish that chatty-sounding first-person narrative voice I mentioned above. Sometimes, this can work beautifully, but as with any repeated stylistic trick, there’s a fine line between effective and over-the-top.

Also, had I mentioned that aspiring writers just love to overload their manuscripts with conjunctions? And that they use the device a lot? Or that by the time Millicent picks up your submission, she’s probably already read hundreds of conjunctions that day?

In case I’m being too subtle here: since false consecutiveness is a narrative that professional readers see so very much, you might want to screen your submission for its frequency. Particularly, if you’ll forgive my being a bit pushy and marketing-minded here, in the early pages of your manuscript. And absolutely on the first page.

Why especially the opening? Long-time readers, chant it with me now: agents, editors, and contest judges tend to assume that the writing on pages 1-5 is an accurate representation of the style throughout the entire manuscript. That presumption enables them to stop reading as soon as they decide that the writing is weak.

Or, to cast it in terms of our running analogy: Millicent didn’t like the second pretzel of the day, she takes it as given that she’s not going to like the 145th. She does not feel the need to gobble up pretzels 3-144 to confirm that.

Was that sudden blinding flash an indication that light bulbs just went off over some of your heads? That’s right: this often-unwarranted assumption, renders rejection on page 1 not only logically possible, but reasonable. It certainly underlies the average Millicent’s practice of not reading past any problems that might turn up on page 1 of a submission: once you’ve seen a modicum of this author’s writing, she reasons, you’ve seen enough.

Feel free to pause here to punch the nearest pillow, sofa cushion, or other relatively soft object seventeen or eighteen times. I’ll wait.

Got all of that frustration out of your system? Excellent. Let’s shift our energies to what a writer can control in this situation. Narrative structure and voice are not merely matters of style; to a market-savvy writer, they are also matters of strategy.

And, frankly, the oh-so-common practice of conjunction overuse is not particularly good strategy. If you over-use any single narrative tool in your writer’s kit in those early pages, Millicent and her ilk are not going to stick around to see whether you’ve mended your ways by page 25, alas. They’re going to stop reading, so they may move on to the next submission.

Do I hear some moaning out there that’s not attributable to any of my late relatives? “But Anne,” these disembodied voices moan, bravely beginning their protest with a conjunction, thereby risking a thunderbolt flung by Uncle Alex and whatever minor deities he may have managed to befriend in his time in the choir eternal; he always did throw great parties, “not every book’s best writing falls on its first page, or even within its first chapter. Many, many writers take a chapter or two to warm up to their topics. So doesn’t this practice give an unfair advantage to those writers who do front-load their work?”

In a word, yes. Next question? In fact, I would highly recommend front-loading your submission or contest entry with your best writing, because I want your work to succeed.

Again, we could waste a lot of energy complaining about the necessity for this (which I’m sure all of us could, at great length), but I would rather we concentrate instead upon heading the problem off at the proverbial pass. Whip out your trusty highlighter pens, and let’s get to work.

(1) Print out at least the first 5 pages of your submission. If you want to be very thorough, print the entire first chapter, as well a random page from each subsequent chapter.

And before anybody asks: no, reading through those pages on your computer’s screen is not an adequate substitute here. Nor is simply doing a Word search for those particular words. The goal here is not to come up with a simple accounting of how often you are using these words, but to spot patterns in how and where you are habitually including them.

(2) Pick a color for and, another for but (go ahead and use it for the howevers and yets, too), and a third for then.

Why these words and no others? Well, these particular ones tend to get a real workout in the average manuscript: when writers are trying to cover material rapidly, for instance, and, but, and then often appear many times per page. Or per paragraph.

Or even per sentence. Yes, really.

(3) Mark every single time each of those words appears on your pages.

Not just where these words open a sentence, mind you, but every instance.

(4) After you have finished inking, go back and re-examine every use of then, asking yourself: could I revise that sentence to cut the word entirely? If it begins a sentence, is that the most effective opening?

(5) If you were even tempted to skip Step 4, does then appear more than once within those first 5 pages? More than once on page 1?

At the risk of seeming draconian, you should seriously consider excising every single use of then in those opening pages — and at least toy with getting rid of most thereafter. Sound drastic? Believe me, I have an excellent reason for suggesting it: some professional readers’ visceral negative reaction to repetitive use of then borders on the physically painful.

Why? Well, it’s one of the first words any professional editor would cut from a text — and with good reason. In written English, pretty much any event that is described after any other event is assumed to have happened later than the first described, unless the text specifies otherwise. For instance:

Jean-Marc poached the eggs in a little butter, slid them onto the plate, then served them.

Ostensibly, there’s nothing wrong with this sentence, right? Perhaps not, but given the average reader’s belief that time is linear, it is logically identical to:

Jean-Marc poached the eggs in a little butter, slid them onto the plate, and served them.

Technically, then is unnecessary here. In fact, then is almost always omittable as a purely temporal marker.

“Pardon my asking,” Millicent says, wondering why I have a latte at my elbow and she doesn’t, “but why is do submissions so often include it repeatedly, as if it were stylish? Or, if appears frequently enough, as a characteristic of authorial voice? It’s seldom necessary, and it’s hardly original.”

That would be hard for anyone who has read more than a handful of manuscripts or contest entries to dispute. To professional eyes, this percussive use of then is logically redundant, at best. At worst, it’s a sign that the writer is getting a bit tired of writing interestingly about a series of events and so crammed them all into a list.

Is this really the reaction you want to elicit to your narrative voice within the first few pages of your book?

Actually, it’s not a bad idea to omit temporal thens altogether in your writing unless the event described after them is a genuine surprise or occurred so abruptly that it would have been so to onlookers. Here’s an instance where the use is undoubtedly justified:

Jean-Marc poached the eggs in a little butter, slid them onto the plate — then flung their steaming runniness into Anselmo’s astonished face.

Now that’s a then that signals a change in sentence direction, isn’t it? Reserving the device for this use will render your thens substantially more powerful.

(6) Turn now to the buts, howevers, and yets on your marked-up pages. Each time they appear, ask yourself: is the clause that immediately follows the word ACTUALLY a shift in meaning from what has come immediately before it? If not, consider excising the words altogether.

I hear more squawking from the non-celestial peanut gallery. “But Anne,” they cry, bravely persisting in their long-term habit of opening every protest hurled my way with a conjunction, “you can’t seriously mean that! Don’t you mean that I should carefully rewrite the sentence, substituting another word that means precisely the same as but, however, or yet? The whole point of my introducing however and yet was to give my but a periodic rest, after all.”

Good question, but-resters, but I did mean what I said. But, however, and yet logically imply contradiction to what has already been stated. Many aspiring writers use these words simply as transitions, a way to make the sentence before seem to flow naturally — that is, in a way that sounds like conversation — into the next.

What I’m suggesting here is not that you remove every legitimate negation, but rather that you should remove the negative conjunctions that are misused. Let’s take a gander at what a savvy reviser might spare.

Bartholomew wanted to answer, but his tongue seemed to be swelling in his mouth. Was it an allergic reaction, stress, or had Josette poisoned him? He felt panic rising within him. However, his epi pen was in the pocket of his fetching dressing gown, so he need not panic. Yet now that he began to search for it, his personal first-aid kit seemed to have vanished from its usual resting-place.

“Cat got your tongue?” Josette asked sweetly, adding another lump of strangely-colored sugar to his tea.

I would vote for keeping all of buts, howevers, and yets in this passage. Each is serving its proper function: they are introducing new facts that are genuinely opposed to those that came just before the conjunction.

That is not always the case, alas. Take a look at a version of the same scene where none of these words is ushering in a twist related to the last information before it:

Bartholomew settled his fetching dressing gown around him irritably, but his tongue seemed to be swelling in his mouth. Was it an allergic reaction, stress, or had Josette poisoned him? He felt panic rising within him. However, he could not breathe. Yet his asthma seemed to be kicking in full force.

“Cat got your tongue?” Josette asked sweetly, adding another lump of strangely-colored sugar to his tea.

See the difference? By including conjunctions that imply an opposition is to follow, but not delivering upon it, the transitional buts, howevers, and yets ring false.

Yes, this level of textual analysis IS a heck of a lot of work, now that you mention it. Strategically, it’s worth it, for this device is so popular amongst aspiring writers that the transitional but has become, you guessed it, a common screeners’ pet peeve.

Harrumphs all round from my questioners, earth-bound and otherwise. “No big surprise there,” they huff. “To hear you tell it, it doesn’t take much for a writerly preference to graduate to industry pet peeve.”

Actually, it does take much — much repetition. It just doesn’t take very long manning the screening desk to discover that out of any 100 submissions, a good 92 will all share this narrative device.

And yes, Virginia, the transitional but IS that common. As is the unnecessary then. Trust me, agents and editors alike will bless you if your manuscript is relatively light on these overworked words.

Or if you don’t overuse favorite words in general. English is a marvelous language for prose because contains so very many different words; it enables great precision of description.

“So why on earth,” Millicent wonders, rejoining us after a coffee run, “do these submissions keep leaning so heavily on to be, to have, to think, to walk, to see, to say, and to take? If it happened in, say, one submission out of fifty, I could cope with it, but every other one?”

Good question, Millie. Varying word choice almost always makes a better impression upon professional readers than leaning too heavily on the basics.

Yes, I brought this up a few days ago, but it’s a fact that I wish more first-time submitters knew, but usually, US writers have been taught just the opposite: all throughout their school years, teachers kept quoting either Mark Twain or Somerset Maugham’s (depending upon how old the teachers were, and what examples their teachers had used) overworked axioms about never using a complex word when a simple word would do.

The reason that your teachers told you this is not that simple, straightforward words are inherently better than polysyllabic ones, but because they were trying to prevent you from making the opposite mistake: a narrative that sounds as if it has swallowed a thesaurus whole, dragging in pretentious or obsolete words inappropriate to the book category or target market. For most manuscripts, this is still pretty good advice.

Now, however, it’s considered less a matter of style than of marketing. Remember, the standard vocabulary expectation for adult fiction is a 10th-grade reading level; in many genres, it’s even lower. Doing a bit of reading in your chosen category can help you figure out where to pitch your word choices — and how broad a vocabulary Millicent is likely to expect in your manuscript.

Why is this a good idea? Not only is the gratuitous induction of polysyllabic terminology into a tome formulated for a less erudite audience not liable to galvanize a professional reader into spontaneous cries of “Huzzah!” (see how silly it looks on the page?) — it can also stick out like the proverbial sore thumb, knocking the reader out of the story.

The much-hyped 2007 movie JUNO contained such an excellent example of this that you might want to consider renting it just to see this phenomenon in action. After spending fully two-thirds of the film establishing the protagonist’s father as a Working Man with a Heart of Gold, living in a house that apparently contains no books, repeatedly telling better-heeled folk that he’s just a plain man, and who never once mentions to his pregnant 16-year-old daughter that her condition might conceivably (so to speak) affect any future college plans she might have, he says to his daughter, “You look morose.”

At which, naturally, half of my fellow theatergoers laughed, believing this line to be a joke. Morose didn’t seem to be a word that this character would ever use. Yet from context, it wasn’t intended humorously: evidently, the screenwriter simply liked the word.

Nothing wrong with that, of course — but authorial affection is not always sufficient justification to include a pet word or phrase. If a word is not book-category appropriate, think seriously about finding a substitute. That’s not compromising your artistic vision; that’s gearing your voice to your audience.

It’s also a necessary step towards individualizing your authorial voice. Just as a matter of practicality, if Millicent has already seen several conjunction-heavy narratives within the last hour, it’s going to be significantly more difficult to impress her with the originality of a manuscript that’s embraced a similar narrative strategy.

Speaking of developing a sensitivity to repetition across manuscripts, as well as within them, did anyone happen to catch the too-close similarity of Yvette and Josette in the two of today’s examples? “What’s going on?” Millicent shouts immediately after burning her lip on her too-hot latte. “A plague of -ettes? Did a bestseller from a year ago feature a heroine with an -ette name, and are the writers of these two passages copying that?”

Well caught, Millicent: I didn’t catch that one myself until about ten minutes after I wrote the second example. Clearly, I should have had a more balanced breakfast.

Don’t toss out those marked-up pages, please: we shall be talking more about overused conjunctions in the days to come. Next time, it’s on to the ands. Keep up the good work!

Pet peeves on parade, part XXIV, structural repetition, part II, or, are these concurrent series starting to get out of hand?

No, that image isn’t doctored — that’s a quick snapshot I took today of my garden’s first summer poppy. Eat your heart out, Georgia O’Keeffe.

I wasn’t playing hooky in the garden, honest; I was prowling my flowerbeds for bright, arresting color to illustrate our topic du jour. What, after all, would remind a self-editing writer more of structural repetition — the phenomenon of a writer’s falling in love with a certain kind of sentence and consequently over-using it throughout a manuscript — than a flower that might attract a passing motorist’s attention from half a block away?

“But Anne,” metaphor enthusiasts throughout the writing world protest, “I don’t get it. How are these two apparently unrelated things akin?”

That’s a perfectly legitimate question from a writerly point of view, metaphor-huggers, but from an editorial perspective, the connection is self-evident: both seem to leap out at the observer. To most of us who read manuscripts for a living, a manuscript that keeps recycling sentence structures, pet phrases, or even individual words might as well be covered with flashing neon signs.

Don’t believe me? Okay, here is a page stuffed to the gills with one of the more common types of repetition, the over-use of proper nouns in general and character names in particular. I’ve made the image a trifle larger than usual, to render the pattern easier to spot.

In fact, you don’t even have to read the text to notice it: stand up, back away from your computer until you can’t make out individual words, then walk slowly toward the screen. Ready, set — observe!

All of those Js and Ps were the first thing you saw on your return trip, were they not? A sharp-eyed pro like Millicent the agency screener would have that reaction scanning the page at a normal reading distance.

Now let’s take a gander at how the visual problem is exacerbated if the sentence structure is also repetitious. To render this tortured page even more likely to annoy our Millie, I’ve selected a common construction in the passive voice.

Quite a bit less amusing to read, isn’t it? I wouldn’t be at all astonished if you were tempted not to read it all the way to the end — although the page was not in fact made up entirely of it was X and it was as though sentences, it certainly began to feel like it by halfway down the page, didn’t it?

A trained eye would be drawn immediately toward those repeated patterns — and thus away from other aspects of the text a savvy writer might want a professional reader like our old pal Millicent to notice instead, such as the compelling storyline, the interesting characters, and/or the overall beauty of the writing. Because repetition in general and structural repetition in particular are so very common in submissions, Millicent and her ilk not only find it distracting; they tend to regard it a symptom of both a small authorial vocabulary and — you’re sitting down, I hope? — weak writing.

On the off chance that I’m being too subtle here: you might want to think twice about incorporating much repetition into your preferred authorial voice. Especially in your opening pages — which, lest we forget, folks who screen manuscripts for a living are prone to regard, rightly or not, as representative of the writing in the rest of the manuscript.

To put it rather less gently: if the sentence structure and vocabulary on page 1 don’t show much variation, Millicent’s unlikely to keep reading until page 50 to find out whether these traits are consistent features of the author’s chosen voice. Heck, she probably won’t turn to page 2 to confirm that suspicion.

It’s hard to blame her, given the provocation. As we saw in the second example, even when the word choices vary enough to keep things moderately interesting, it’s simply more tiring to read the same kind of sentence over and over than to read text where the form varies more.

That’s true, incidentally, regardless of the subject matter: even an inherently fascinating topic can quickly be rendered stultifying by the simple expedient of writing about it in structurally similar sentences. Repetitive phraseology can render even the most exciting, conflict-ridden scene quite a bit less nail-biting than its activity level should dictate. That’s true, surprisingly, even if the chosen structure is quite complex.

Did my reuse of the that’s true + adverb structure bug you more in that last paragraph, or the recycling of even? By this point, I would hope that neither escaped your attention.

Back to the principle at hand: let’s observe the soporific effect of a more complicated repeated structure in action. So I don’t plunge all of you into a deep, refreshing slumber, I shan’t subject you to an entire page of it.

Obviously, no one plans to crash a motorcycle into the side of a cross-town bus, but that is precisely what Barnaby did. Fortunately, he was wearing his inflatable jumpsuit, saving him from significant injury, but clearly, his morning was not going to be a smooth one. Resignedly, he collected his scattered belongings, including the small thermonuclear device he later planned to smuggle into the state dinner, but he could not resist cursing under his breath.

Something tells me that a scene with stakes this high could have been written about in a slightly more compelling manner. There’s more to good storytelling, after all, than just getting all of the facts down on the page. To see why this is true, we need look no farther than the early reader books of our youth.

You know the type, right? See Spot run. See Spot bite Dick. See Dick shiv Jane. Stab, Dick, stab.

Dull, from an adult perspective, weren’t they? But dull with a purpose: part of their point was to encourage new readers to recognize letter patterns as particular words. Varying the sentence structure enough to render the insipid story interesting to more advanced readers would merely have distracted from the task at hand.

So we were treated to the same sentence structure for what seemed like the entire book. I have a distinct memory of taking my kindergarten copy of FROG FUN home from school (Hop, frog, hop. Hop, hop, hop: hardly Thackeray), reading a two pages of it to my father, and both of us deciding simultaneously that no self-respecting human being would keep slogging through that much narrative repetition. He wrote a very amusing little note to my teacher about it.

Suffice it to say that my teacher quickly learned to send me to the library for alternate reading material. And stopped teaching kindergarten shortly thereafter. I’m told that she still winces whenever she sees a frog.

It’s even easier to make Millicent wince — at any given moment, her to-read pile overfloweth with submissions that, if not as word-repetitious as FROG FUN, have fairly obviously not been carefully revised with an eye to sentence variation. That’s a pity, because when a professional reader sees a manuscript that uses the same sentence structure or the same few verbs use over and over, the specters of Dick, Jane, and Spot seem to rise from the page, moaning, “This is not very sophisticated writing!”

Why? Well, when one’s eye is trained to note detail, it’s doesn’t take much redundancy to trigger a negative reaction.

In fact, a good professional reader will often catch a repetition the first time it recurs — as in the second time something is mentioned in the text. It’s not unheard-of for an editorial memo to contain an angry paragraph about the vital necessity to curb “your inordinate fondness for” phrase X when phrase X shows up only three or four times in the entire manuscript.

As in over the course of 382 pages. Had I mentioned that we pros are trained to be extremely sensitive to redundancy?

Imagine, then, how much more annoying they find it when every third sentence begins with a structure like, Blinking, Sheila backed away or George was…” or the ever-popular, As she was doing X, Y happened.

That last one caught you a bit off guard, didn’t it? I’m not entirely surprised: if an alien from the planet Targ were to base its understanding of human life solely upon the frequency with which protagonists in first novels do something while something else occurs, it would be forced to conclude that humanity is doomed to perpetual multitasking. Either that, or it would surmise that the space-time continuum is somehow compressed by the mere fact of someone’s writing about it.

Oh, you laugh, but how else could the poor visitor to our solar system possibly interpret a passage like this?

As Monique turned the corner, she spotted Clarence. He dodged as she came up to him. While he was looking for someplace convenient to hide, she calmly unearthed a crossbow from her purse.

Aiming, she cleared her throat. “The jig’s up, Clarence.”

That’s quite a bit of activity happening simultaneously — and quite a few logically similar sentence structures shouldering one another for prominence. But contrary to popular opinion amongst aspiring writers, the mere fact that two things occurred at the same time is not particularly interesting to most readers. Unless the simultaneity of the motions in question is crucial to the reader’s understanding what’s going on, as and while can be awfully easy to overuse.

How so? Well, let me put it this way: if our imaginative little run-in with the Targian had not tipped you off in advance, would you have noticed that there were two things going on contemporaneously in every sentence in that last example?

If so, you’re certainly not alone: most aspiring writers — i.e., the folks who have not yet had the professional opportunity to hear an editor go on a tirade about it — would not see a problem with that excerpt. Millicent, however, would, and that’s likely to spark some rather unpleasant consequences at submission time.

So how might a savvy reviser rearrange that passage so as to leave her eyebrows mercifully unraised? Vary the sentence structure — and cut out any extraneous activity. While you’re at it, reserve as for those relatively rare occasions when it’s imperative that the reader be made aware that things happened at the same time. The result might look a little bit like this:

Monique strode around the corner, surprising Clarence so much that he dropped his bullwhip. While he was looking for someplace convenient to hide, she calmly unearthed a crossbow from her purse.

Carefully, she took aim at his Adam’s apple. “The jig’s up, my friend.”

The contrast between this version and the previous one is pretty stark, is it not? To repetition-sensitive eyes, a page filled with structural and word repetition is like badly-done CGI in movies, where battle scenes between thousands of characters are created by filming 50 extras flailing at one another, copying that image, and plastering it seventeen times across the scene, perhaps alternated with two or three other images of the same actors in different positions. Honestly, to those of us who count patterns for a living, that level of repetition can be downright migraine-inducing.

“Wait just a nit-picking minute, Anne!” I hear some conscientious revisers exclaiming. “English grammar only permits so many ways of arranging sentences properly. Isn’t any manuscript going to exhibit a certain amount of pattern repetition, necessarily?”

Yes, of course — but that does not give writers carte blanche to use the same structures back-to-back, or to utilize a favorite complex sentence form twice per page. And that’s unfortunate, because it’s not as though your garden-variety writer is repeating herself on purpose: in the vast majority of instances, the writer simply likes a kind of sentence or a particular verb enough to use it often.

You lucky souls, however, are going to be one up on that kind of writer come revision time, because we’re about to take a run at spotting the phenomenon in its natural habitat. Since last post’s foray into A TALE OF TWO CITIES was so obvious, let’s try a comparatively subtle one on for size.

Rubbing his sides for warmth, Stephen glanced unhappily at his fellow cheerleaders. Waving his pom-poms in a wan impression of good sportsmanship, he reminded himself never to be stupid enough to accept one of his sister’s bets again. Pulling up his flesh-colored tights –- oh, why hadn’t he listened to Brian, who had told him to wear nylons under them on this near-freezing night? – he wondered if Tammy would be vicious enough to demand the performance of the promised splits before the game ended. Sighing, he figured she would.

How did you do? Individually, there is nothing wrong with any given sentence in this paragraph, right? Yet taken communally — as sentences in submissions invariably are — the repetition of the same kind of opening each time starts to ring like a drumbeat in Millicent’s head, distracting her from the actual subject matter, the quality of the writing — and, alas, even the blistering pace you worked so hard to achieve on the page.

That’s not just a voice problem — it’s a marketing problem.

Why? Well, think about it: very, very few agents and editors can afford to work with specialists in a single type of sentence. And don’t start waving random pages ripped from Ernest Hemingway’s oeuvre at me, either: present-day readers expect a narrative with a broad array of sentence structures.

The sad thing is, most of the time, writers don’t even realize that they’re repeating patterns, because unless the repetition bug has really bitten them, the redundancy isn’t in every sentence. Or if it is, the repetition often lies in words or phrases that are similar, but not identical, so the writer does not think of them as the same word. Consider:

Arnold began sweating, sweating as though his sweat glands were going on strike tomorrow. Should he go to the window and throw it open, beginning the cooling-down process? Or should he go downstairs, into the basement, to the cool of the pickle cellar? Or should he wait for the seller on the cooler porch?

Subtle, isn’t it? Sometimes, the structures a writer favors may be common enough in themselves that she would need to read her pages IN HARD COPY and OUT LOUD to catch the problem. As in:

“But I didn’t steal the payroll,” Claire insisted, “because I had no reason.”

“But you did take it,” Edmund shot back, “because you needed the money for your sainted mother’s operation.”

Claire’s eyes filled with tears. “You leave my sainted mother out of it, since you don’t know her.”

These three lines of dialogue feature different words, of course, but they sport identical structures. This may not seem like a serious problem on any given page, but once a professional reader notices a manuscript exhibiting this kind of repetition a couple of times, she will simply assume — feel free to sing along; you should know the words by now — that the pattern will recur throughout the manuscript.

How does s/he know, you ask? Experience, my dears, experience. How many horror films did you have to see before you realized that the monster/killer/Creature from the Black Lagoon wasn’t really dead the first time it appeared to be?

Go back and re-read that last example out loud: did you notice how similar those three paragraphs sound in the mouth — almost as though they were not the words of two different speakers? The repetitive structure here makes Claire and Edmund speak in essentially the same rhythm, as though they were echoes of the same voice. (Which, from an authorial point of view, they are.)

When two characters speak in the same rhythm, it mutes the conflict between them a little — not to mention making it harder for the reader to follow the dialogue. Check out how varying the sentence structure ramps up the tension between them, even in an excerpt this short:

“But I didn’t steal the payroll,” Claire insisted. “I had no conceivable reason.”

“You lie,” Edmond shot back. “You needed the money for your sainted mother’s operation.”

Her eyes filled with tears. “You leave my sainted mother out of it, me bucko, since you don’t know her.”

“Aha! I knew you were concealing a pirate past!”

“I ought to keel-haul you.” Sullenly, she removed her eye patch. “What gave me away, the parrot?”

Nifty, eh? That, in case you were wondering, is the kind of character development benefit a writer is likely to derive from reading her work OUT LOUD. I just mention.

But a writer need not only pay attention to how many times he’s using the same words or similar sentence structures in back-to-back sentences, but also on any given page, or even over the course of a scene. Let’s take a look at how non-consecutive repetition might play out in practice.

As the car door opened, Beatrice swallowed a horrified gasp. It was Harold’s severed hand, dragging itself around the latch mechanism, one grisly fingertip at a time. As she reached for the gun, her intestines palpitated, but she forced her arm to remain steady. While she loaded the bullets into the chamber, she thought about how much she had loved Harold, back when his constituent parts were all still interconnected as a human’s should be. It was a shame, really, to have to keep blowing him to bits. But blow him to bits she would continue to do, as often as necessary.

My, but our examples are violent today. To most self-editors, this paragraph would not seem especially problematic. However, to a professional reader, it contains two of the most commonly-repeated structures, our old friends, the While X was Happening, Y was Occurring and the It Was Z…. Standing alone as individual sentences, either form is perfectly valid; the problem arises when either appears too frequently on the page. To a professional reader, this is how the paragraph above would scan:

As the car door opened, Beatrice swallowed a horrified gasp. It was Harold’s severed hand, dragging itself around the latch mechanism, one grisly fingertip at a time. As she reached for the gun, her intestines palpitated, but she forced her arm to remain steady. While she loaded the bullets into the chamber, she thought about how much she had loved Harold, back when his constituent parts were all still interconnected as a human’s should be. It was a shame, really, to have to keep blowing him to bits. But blow him to bits she would continue to do, as often as necessary.

See how even spread-out repetition jumps off the page, once you’re sensitized to it? Millicent (and her boss, and the editors at the publishing house across the street, and even the average contest judge after reading the first handful of entries) is so attuned to it that she might not even have made it as far as the end of the paragraph.

To use the most overworked word in her vocabulary: “Next!”

Of course, you may strike lucky: your submission may be read by a screener who hasn’t been at it very long, a contest judge brand-new to the game, or an agent whose tolerance for pattern repetition is unusually high. Heck, your work may even land on the desk of that rara avis, the saint who is willing to overlook some minor problems in a manuscript if the writer seems to have promising flair. In any of these cases, you may be able to put off winnowing out pattern repetition until after the book is sold to an editor — who is most unlikely to be so forgiving.

Do you honestly want to gamble on Millicent’s possible saintliness at the submission stage?

Because editorial response to this kind of repetition tends to be so strong — I wasn’t kidding about those migraines — you would be well advised to check your first chapter, especially your opening page, for inadvertent pattern repetitions. (Actually, since quick-skimming pros tend to concentrate upon the openings of sentences, you can get away with just checking the first few words after every period, in a pinch. But you didn’t hear that from me.)

The most straightforward way to do this is to sit down with five or ten pages of your manuscript and a number of different colored pens. Highlighters are dandy for this purpose. Mark each kind of sentence in its own color; reserve a special color for nouns and verbs that turn up more than once per page. You probably already know what your favorite kinds of sentence are, but it would be an excellent idea to pre-designate colors for not only the ever-popular While X was Happening, Y was Occurring and the It Was… sentences, but also for the X happened and then Y happened and Gerund Adverb Comma (as in Sitting silently, Hortense felt like a spy.) forms as well.

After you have finished coloring your pages, arrange all of the marked-up pages along some bare and visually uncomplicated surface — against the back of a couch, along a kitchen counter, diagonally across your bed — and take three steps backward. (Sorry, kitty; didn’t mean to step on your tail.)

Does one color predominate? If you notice one color turning up many times per page — or two or three times per paragraph – you might want to think about reworking your structures a little.

If this all seems terribly nit-picky to you, well, it is. But the more you can vary the structure and rhythm of your writing, the more interesting it will be for the reader – and, from a professional perspective, the more it will appeal to educated readers.

Think about it: good literary fiction very seldom relies heavily upon a single sentence structure throughout an entire text, does it?

You know what kinds of books use the same types of sentences over and over? The ones marketed to consumers with less-developed reading skills. If that is your target readership, great — run with the repetitive structure. (Run, Jane, run! Don’t let Dick stab, stab, stab.) But for most adult markets, the industry assumes at least a 10th-grade reading level.

In my high school, Ernest Hemingway’s THE OLD MAN AND THE SEA was assigned in the 9th grade. If you catch my drift.

Then, too, agency screeners and editorial assistants typically hold liberal arts degrees from pretty good colleges. That’s a long, long way from the reading level that was contented to watch Dick and Jane running all over the place with Spot and frogs having fun hop, hop, hopping.

Let your structural choices be as exciting as the writing contained within them — and let your voice emerge as more than a repetitive collection of your favorite words and sentences. Incorporate your pet structures and phrases, by all means, but have them appear rarely enough that they will seem like revelations, not just narrative-as-usual.

Above all, keep mixing up those sentence structures. You may be pleasantly surprised at how much interest merely preventing a sentence from reading like the one before it can produce. Keep up the good work!

Pet peeves on parade, part XXIII: the monster always returns…returns…returns…

I’m having a good day, campers: today, I got to delve back into an editing project I’d had to put aside for a while. It’s something that requires my full energy; digging one’s arms up to the elbow in a complex manuscript takes more out of a conscientious editor than writers tend to believe.

You’d be surprised at how deeply those of us who read for a living can bond with the manuscripts we handle. It’s not as though an editor (or an agent, or an agency screener) can plop himself down and read a book like any other reader; it’s our job to be alive to every detail. I like to think of myself as the book’s advocate, trying to figure out all of the little ways to make it as beautiful and marketable as humanly possible.

And no, in response to what a good third of you just thought very loudly, beautiful writing is not always marketable, any more than marketable writing is always beautiful. Ideally, a manuscript should be both. It should also, if I can possibly manage to nudge it in this direction, be written in a voice and vocabulary appropriately challenging for its target readership.

Bringing out any of these laudable traits is not only a matter of critiquing what could be improved; quite a lot of what I do involves helping the author see what is already good and could be made better. Part of being a thoughtful freelance editor — as opposed to a careful copyeditor, the nit-picky soul who concentrates on making sure that the manuscript is clear and the sentences grammatically correct, the minimum standard for professional writing — involves not only checking for possible red lights that might lead to rejection, but also figuring out what a manuscript’s strengths are, as well as why it will appeal to its target audience.

Again, those are not necessarily the same thing, right?

Most aspiring writers do need to be reminded, I’ve noticed, what is good about their work. Or even told what the selling points for their books are.

There’s a pretty good reason for this, actually. Throughout the writing process, it’s awfully easy to start to think of the effort you’ve put into a book as its most important characteristic. But realistically, publishing houses do not acquire books simply because someone went to the trouble to write them. Nor, contrary to popular opinion amongst aspiring writers, will readers — ones who do not already know the author personally, at any rate — pick up a book simply because somebody happened to write it.

Why does prompt publishers to acquire manuscripts and readers to buy books, you ask? Would I sound like a broken record if I suggested that both sell because of their strengths?

In fact, the length of time it took to write a book is precisely the wrong thing to mention in a query letter or pitch; it’s widely considered unprofessional. Millicent the agency screener is apt to regard queries that include statements like I have spent seven years writing NOVEL, GREAT AMERICAN as not only a waste of page space, but as a studied appeal for her sympathy.

“Why on earth would I care how long this manuscript took to write?” Millicent murmurs into her omnipresent latte. “And why would I be more favorably impressed by a seven-year effort than one that took only six? What matters is on the page, not what Herculean efforts it took to get there.”

Let me repeat that, as it’s awfully important: at the submission stage, manuscripts are evaluated based upon what actually appears on their pages, not the writer’s intentions, effort, or even what the book might look like after a conscientious editor’s had a few rounds with it. Many, many aspiring writers seem to have a hard time accepting this, judging by how often justifications and explanations seem to find their way into queries and pitches. From a professional point of view, this information just isn’t relevant.

But that’s not the only reason that including it could hurt you. Because it’s quite standard for both agents and editors to request revisions after taking on a book project — see my earlier observation about how involved professional readers can get with manuscripts they like — it’s prudent to assume that the pros in your future will expect you to be able to incorporate feedback in a timely and reasonable manner. So if the agent of your dreams’ reaction to a detailed account of the five years you invested in producing the manuscript is less likely to be, “Gee, this book must be worthwhile,” but “Heavens — if a single draft took five years, how long will any revisions I want take?” is it truly in your interests to mention it?

Save the probably quite interesting story of how you churned out that 400-page novel in the scant ten-minute increments you managed to snatch between your day job and your night job for future interviews. Trust me, your reading public will eat it up.

In your queries and pitches, stick to the information that Millicent actually needs in order to decide whether to request pages. As submitting writers are all too prone to forget, publishing is a business, not an art form — agents and editors acquire books they believe are marketable, not just ones they believe are well-written. And, as I believe I have mentioned several hundred times before, they do not — contrary to the hope of most submitting writers — read the entire submission before making up their minds on either point.

Anyone care to tell the class at what point in the average submission Millicent stops reading? Think on it, and I shall give you the answer at the end of this post.

Hint: it doesn’t necessarily correlate to the number of pages her agent boss asked you to send. Not at all.

How does this relate to the revision process, you ask? Well, swift judgments mean that if you have limited revision time at your disposal, it’s smart strategy to concentrate on the first 50 pages of your manuscript — the usual first request from an agent — or, in a pinch, the first 5. (If you are planning to head to a writers’ conference anytime soon, burnishing the first 5 until they shine is imperative: the first five pages of the manuscript are the standard writing sample, the most anyone is at all likely to ask to see within the context of a pitch meeting. But I digress.)

Do I sense an undercurrent of amusement out there? “Are you seriously taking the time to justify doing any revision at all, Anne?” those of you who have followed the Pet Peeves on Parade series closely ask, chuckling. “Isn’t it a bit late in the series for that? We all know what a stickler Millicent can — and indeed, should — be. Or are you once again leading us down the primrose path to some well-concealed eventual point?”

Well, the importance of revision bears repeating, chucklers, but you’re right: my little peroration was warming you up for a pet peeve that I suspect not all of you will agree is problematic on the page. Or so professional readers like yours truly surmise from how pervasive the problem I’m about to mention is in submissions — particularly in openings.

I’m speaking, of course, to invocatory rhythms that don’t quite work. And you thought this post wasn’t going to be a continuation of our discussion on voice!

Invocatory rhythms are one of the most popular tools aspiring writers use to beautify their narratives, a kind of sing-song rhythm that alerts the reader that Something Literary is Going on Here. One of the easiest ways to add this music to a text is through word and phrase repetition. Take a gander at a fairly representative sample:

Musette ran through the corridor, ran like the wind, ran as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her freedom, after all this time? Didn’t she deserve a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, deserve to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

See the problem? No? Okay, let’s take a peek at it through Millicent’s experience-sharpened peepers.

Musette ran through the corridor, ran like the wind, ran as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her freedom, after all this time? Didn’t she deserve a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, deserve to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

The problem is clearer now, right? Not only does this innocent-looking paragraph harbor a heck of a lot of word and phrase repetition — enough that our Millie may murmur under her breath, “Wow — doesn’t this writer know any other words?” — but that eye-confusing reiteration is encased in identical sentence structures. The result is a little something we professional readers like to call structural repetition: a percussive repetition of similarly-structured sentences (or sentence fragments) intended to make a rhythmic point.

Why bring this up as a voice and revision problem, in addition to a notorious Millicents’ pet peeve? Because part of the issue here is editorial: merely broadening the vocabulary, the usual fix for word repetition, would not solve this problem. Lookee:

Musette ran through the corridor, sped like the wind, fled as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? Didn’t she merit a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, have an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

Better already, is it not? To a professional reader, though, this passage would still read as structurally repetitious, despite the wording being more varied (and thus more interesting) this time around. And that reaction is apt to confuse self-editors, who would tend to see the nice, pulsing rhythm pushing the paragraph forward, rather than the probability that the too-similar sentence structures will cause the reader to zone out a bit as the paragraph goes on.

Not to mention the virtual certainty that Millicent will murmur, “There’s nothing inherently wrong with this narrative trick, but why must this writer foist it on us twice in a single paragraph?”

You’ve got an excellent point there, Millie. Like every other narrative device, structural repetition works best when it is used sparingly.

How sparingly, you ask with fear and trepidation? Two or three times, say, in the course of a manuscript, to draw the reader’s attention to particularly important passages. Even within the context of this short excerpt, see how much more effective the first use of structural repetition is if we remove the second.

Musette ran through the corridor, sped like the wind, fled as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? She longed with the urgency of a sneeze for a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat. Clearly, she had an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever.

Didn’t like it that way? Okay, let’s switch where the structural repetition falls — and while we’re at it, take out the cliché about the wind.

Musette sped through the corridor as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? Didn’t she merit a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, have an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

Was that a sudden gust of non-clichéd wind that just made my cat topple over, or did a significant minority of you just sigh gustily?
“I see that there are repeated words in the original version, Anne,” some of you point out, “but frankly, I liked it best. Surely the choice to incorporate structural repetition is a stylistic choice, rather than a matter best left up to an editor. Unless you have just inadvertently proven your point about not every reader’s liking every well-written narrative voice, and you are demonstrating yourself to be the kind of knuckle-dragging troglodyte who eschews the joys of literary fiction in favor of novels that — ugh — feature a plot?”

Actually, I’ve been known to read and enjoy both, oh ye quick to judge. What’s more, I’ve read plenty of literary fiction with strong plots and genre fiction that features beautiful language. So there.

But you are obliquely correct, oh sighers, that the original version above was more likely to have dropped from the fingertips of a writer with specifically literary aspirations than one who was aiming for a more mainstream readership. Since invocatory rhythms are quite common in poetry, this style turns up very frequently in novel and memoir submissions, particularly in those that are either literary fiction or are other types of manuscript written with a literary tone. It just sounds pretty, right?

“If the writing’s pretty on an individual sentence level,” sighers everywhere argue, “how could that be problematic in a submission?”

In several ways, actually. Rather than telling you why, let’s look at the single most famous example of invocatory prose in English literature, the opening to Charles Dickens’ A TALE OF TWO CITIES. Yes, I use this particular example fairly frequently, but humor me here: Dickens, bless his now-still heart, has provided us with a lulu of an example of why structural repetition is problematic in print.

Just for kicks, pretend that you have never seen it before, and try to read like an agency screener. To facilitate that laudable endeavor — and to give you the opportunity to judge for yourself whether all of this textual repetition provides a compelling entrée into the story that follows, here is not just the well-known opening, but the next page as well. As always, if you find you are having trouble making out the individual words, try holding down the COMMAND key and pressing + to enlarge the images.

Now, this voice is certainly distinctive, isn’t it? Hard to conceive of a more memorable opening, rhythmically speaking. But it’s also true that if these were the first two pages of a submission, virtually any modern-day Millicent would have rejected it by line three. Any guesses why?

If your hand instantly shot into the air, alerting me to your trenchant observation that it was because the first paragraph is one interminable run-on sentence — 119 words, connected incorrectly by commas, rather than semicolons, sacre bleu! — give yourself a gold star for the day.

Ditto if you zeroed in upon the apparently random capitalization of nouns, the criminal punctuation choices, the ubiquitous logical contradictions (yes, I know it’s meant to be ironic; think like a screener here and look for reasons to shout, “Next!”), the second paragraph written entirely in the passive voice, and the fact that two paragraphs into the piece, the reader still has absolutely no idea who the protagonist is or what’s going on.

And can’t you just picture an editor furiously scribbling in the margins: “Which was it — the best of times or the worst of times? It could hardly have been both. Commit to one or the other!”

Although any one of those perfectly valid objections might have prompted that cry of “Next!”, the structural repetition is what most pros would have noticed first. To see why, you stand up right now and take two steps backward from your computer monitor.

Notice the visual pattern? Millicent would have spotted it as soon as she pulled the first page of ol’ Charles’ manuscript out of the envelope.

Actually, if you’ve been revising for a while, you might have caught that the structural repetition problem without backing off. A solid tip-off: the verb to be appears 14 times within the first sentence.

It was the best of times, it was the worst of times, it was the age of wisdom, it was the age of foolishness, it was the epoch of belief, it was the epoch of incredulity, it was the season of Light, it was the season of Darkness, it was the spring of hope, it was the winter of despair, we had everything before us, we had nothing before us, we were all going direct to Heaven, we were all going direct the other way — in short, the period was so far like the present period, that some of its noisiest authorities insisted on its being received, for good or for evil, in the superlative degree of comparison only.

Yes, this is a level of verb variation that would make Millicent long for the comparatively challenging vocabulary choices of See Dick run, Jane. Run, Jane, run. Remember, though, it’s not just the repeated words and phrases that would raise professional readers’ weary eyebrows here: it’s the phenomenon of consecutive sentences being set up in the same way. No matter how great your high school English teacher told you this particular opening was, it’s dull for the reader to read the same It was X, it was Y sentence structure over and over again.

Or, indeed, any given sentence structure, if it is repeated often enough within too few lines of text.

Unfortunately, a lot of writers just adore structural repetition: it reads a bit like a prayer. It can provide a driving, almost galloping rhythm to a page. Many aspiring writers see that rhythm in the work of authors they admire and say, “By gum, I’m going to make my paragraphs read like that!”

And they do. Sometimes, they make their paragraphs read like that several times per page.

Don’t mind that loud rapping. It’s merely Millicent pounding her head against a wall, moaning, “Make it stop! Make it stop!”

That’s what happens when perfectly legitimate voice choices run amok. Like any magic trick,, repetitive structure loses its ability to charm when the reader sees it too often. After a surprisingly short while, it can start to come across less as an interesting stylistic choice than as a sort of narrative tic.

Don’t believe me? Okay, let me ask you: how many iterations of It was… did Dickens put you through before you first thought Oh, come on, Chuck; get on with it?

“But Anne,” lovers of percussive repetition beg piteously, “I just love my structurally repetitious opening page/paragraph/chapter. If I’m careful not to use this trick again anywhere in the manuscript, I can keep it, can’t I?”

I have a news flash from Millicentville: she sees a LOT of structurally repetitious openings; as with anything else she sees a dozen times a week, it’s probably going to be more difficult to impress her by this method. She’s also not particularly likely to believe that an opening redolent with repetition is a one-time narrative choice.

More often than not, when a manuscript opens with repetitive structure, it will continue with repetitive structure. That, alas, renders structural repetition dangerous to use in the first pages of a submission. Or book proposal. Agents and editors are just so used to this tendency that they’re all too likely — fairly or not — to conclude that to read on would be to be treated to the same type of sentence over and over, ad infinitum.

And that, my friends, is not invocatory; it’s soporific. Next time, I shall talk about ways to tell which is which in your writing, to figure out when invocatory rhythms will help your work.

Remember, Millicent seldom makes it all the way to the bottom of page one. That’s not a whole lot of lines in which to establish the originality and power of your voice.

Too bad our pal Chuckles blew his chance by repeating himself so much, eh? Keep up the good work!

Finding your voice, part III, or, this is no time to make a carbon copy

For the last couple of posts, we’ve been obsessing on the subject of narrative voice. Yesterday, I advanced a modest proposal: it was more to your advantage as an aspiring writer to revise your manuscript with an eye to making it sound like your writing, rather than like a pale (or even very good) replica of an author whom you happen to admire.

And jaws dropped to the floor all over North America. Apparently, this approach to literary success was something of a novelty to a lot of you.

Or perhaps you were merely surprised that anyone who reads manuscripts for a living would want to talk about individual literary voice. In the maelstrom of advice aimed at writers trying to land an agent, the issue of voice often falls by the wayside, as if it were not important. Indeed, in many writers’ fora and at many conferences, the prevailing advice seems to veer away from it: although most of us who write cherish our original voices, pick any four writers’ conference attendees at random, and three of them will swear that they’ve just heard at least one agent or editor say point-blank that the surest path to literary success is not to wow the world with a fresh new voice or innovative story, but to produce a narrative close enough to a currently established author’s that it could easily be marketed to the same audience.

From the publishing world’s perspective, this is just common sense: figuring out who your target reader is, what s/he is reading right now, and what s/he likes best about it is not only a great way to come up with tweaks to render your work-in-progress more marketable, but also a fabulous means of coming up with a list of agents to query. Think about it: an agent has already established a solid track record of representing books in your chosen category that sales records prove appeal to your ideal readership is far, far more likely to be interested in your work than an agent who habitually represents, well, anything else.

But that’s not what 99% of aspiring writers hear in this advice, is it? Ask any one of those three out of four conference attendees: they have derived the impression that their manuscripts are supposed to sound as if they had been written by someone else.

To be precise, by an author on the current bestseller list. According to this theory, all any agent wants to see is a slightly modified retelling of what’s already available on the market. Or so we must surmise from the tens of thousands of YA queries and submissions in recent years for stories that sound suspiciously like something in the TWILIGHT series.

This erroneous belief does not merely affect what’s submitted to agencies; it can have serious repercussions at the revision stage. Rather than approaching their submissions with the intent of sharpening individual voice, many aspiring writers assume that their narratives should sound less like them. Revision, then, becomes a matter of looking at one’s pages, comparing them to a similar bestseller, and attempting to minimize the difference.

See the problem? These writers are setting their sights far too low. They’re also setting them far too late.

Listen: fads fade fast. (And Sally sells seashells by the seashore, if you’d like another tongue-twister.) In the long run, I believe that a writer will be better off developing her own voice than trying to ape current publishing fashions. Provided, of course, that the voice in question is a good fit for the project at hand.

And then there’s the logistical problem: it takes a while to write a novel; by the time a copycat manuscript is complete. Even after a writer signs with an agent, it takes time to market a manuscript to editors — and after the ink is dry on the publication contract, it’s usually at least a year before a book turns up on the shelves of your local bookstore. Often more like two.

Why is that problematic, in practical terms? Well, chances are, the market will have moved on by then. A bestseller’s being hot now doesn’t necessarily guarantee that the same kind of voice or story will be sought-after several years hence.

In fact, what was selling like the proverbial hotcakes a couple of years back often, if it landed on Millicent the agency screener’s desk today, just seem hackneyed, if not downright derivative. “That’s been done,” Millicent murmurs, moving on to the next submission. “What makes this writer think that there are still editors clamoring for the next BRIDGET JONES’ DIARY, HARRY POTTER, or even THE DA VINCI CODE? Copycats of these bestsellers have inundated agencies for years now. What I’m looking for is a fresh take on a story I know my boss can sell, written in a voice that will appeal to the already-established readership in that book category.”

That’s not an unreasonable request, Millie — but imagine how difficult it would be for an aspiring writer to be simultaneously trying to write like a surprise bestseller’s author and to get a completed manuscript ready to market before that bestseller has ended its love affair with the reading public. Even if an offbeat hit has an unusually long run — vampire vs. werewolf romance, anyone? — unless an aspiring writer had already been working on a similar book project when the sleeper hits the New York Times bestseller lists, it’s likely that by the time the copycat manuscript is complete, Millicent will already have been exposed to hundreds of submissions with the same aim.

Oh, they might not all be obvious about it; many will be genuinely interesting twists on the established premise. But you’d be amazed at how many trend-following aspiring writers will be perfectly up front about their stories being derivative. Any agent who has ever represented a genre-busting hit has received hundreds of thousands of queries like this:

Dear X. Tremely Pickison:

I am looking for an agent for my novel, DUSK, a YA paranormal designed to appeal to the millions of readers of the bestselling TWILIGHT series. But while TWILIGHT’s heroine was torn between a vampire and a werewolf, DUSK’s teen protagonist must choose between a sexy merman and a handsome Frankenstein’s monster.

You won’t want to miss out on this next great bestseller! I don’t know that I’m supposed to include a SASE, so you’ll just have to guess how to get in touch with me if you are interested in my work.

Sincerely,

Starchaser McFameseeker

Okay, so the part about the SASE was a bit of an exaggeration — most queries like this don’t include one and don’t mention it. But the toss-a-brick-through-the-nearest-window subtlety of the sales approach and the carefully-drawn obvious parallel to the copied book is often this blatant.

Unfortunately for queriers who embrace this strategy, neither this kind of hard sell nor the carbon copy approach to breaking into publishing tend to do much for Millicent. Oh, a book featuring some of the same elements and written in a comparable voice might well strike her as marketable in the wake of a blockbuster — as anyone who visited a bookstore with a well-stocked YA section a couple of years after the surprise success of TWILIGHT can attest, many similar storylines did in fact see publication as publishers raced to replicate the book’s appeal. But the mere fact that thousands of aspiring writers will inevitably look at that blockbuster and say, “Oh, I can write something like that,” means, necessarily, that a writer who embraces the copycat route will be facing a great deal of competition.

Not to mention running the risk of boring Millicent. Believe me, when you’re seeing the same essential storyline or plot elements in every fifth or six query — not at all out of the realm of possibility, about a year after a major blockbuster’s release — you’re going to get tired of it fast.

The same holds true for voice — and for manuscripts that don’t really have a distinct, individual authorial voice. As I mentioned in passing yesterday, part of the reason that many aspiring writers become confused about voice is that not all published writing exhibits an original narrative voice.

That “Wha—?” you just heard was from the chorus of readers who missed yesterday’s post, I’m guessing. “But Anne,” these intrepid souls protest as soon as they have regained their gasped-out breath, “I don’t understand. I’ve been going to conferences and writing seminars for years, and unless I wasn’t paying attention, published writing and good writing were used as essentially synonymous terms. At minimum, I’ve always assumed that writing needs to be good to get published. But how is that possible, if not all published work has a unique voice?”

Whoa there, gaspers — take a nice, deep breath. In the first place, I’m going to go out on a limb here and state categorically that not all published writing is good.

(A long pause while everyone waits to see if a vengeful deity is going to strike me down for sacrilege. Evidently not; let’s move on.)

Books get published for all kinds of reasons, after all. The writer’s platform, for instance, or the fact that he’s a movie star. (I’m looking at you, Ethan Hawke, not Rupert Everett — although, on the whole, I would prefer to gaze upon the latter, for aesthetic reasons.) An eagerness to replicate the success of a freak bestseller. (Ask anyone who tried to sell historical fiction before COLD MOUNTAIN hit the big time.) Having been a prominent publisher’s college roommate. (One hears rumors.)

In the vast majority of cases, though, a published book without a strong, distinctive narrative voice will at least be clearly written. Perhaps not stuffed to the gills with insights or phraseology that makes you squeal and run for your quote book, but at least unobtrusively straightforward, informative, and decently researched.

You know, like newspaper writing. Clear, non-threatening, generic, ostentatiously objective.

But to have a literary voice is to take a side. At least one’s own. For some stories, that’s not the best option.

In fact, your more discerning professional readers have been known to wrinkle their august brows over a manuscript and ask, “Is the voice the author chose for this appropriate and complimentary to the story?”

Not all voices prove a good fit for all material, after all — and if you doubt that, would YOU want to read a novel about a grisly series of child murders written in the light-hearted voice of a Christmas card? Or a bodice-ripper romance told in the vocabulary of a not-very-imaginative nun?

I’m guessing not.

One of the great fringe benefits of gaining a broad array of writing experience and building up a solid knowledge of craft is developing the ability to switch voices at will. You have to come to know your own writing pretty darned well for that. At the moment, I habitually write in three distinct voices: in descending order of perkiness, my blog voice, the voice I have chosen for my novel-in-progress, and my memoir voice. (My memoir is funny, too, but as a great memoirist once told me, part of the art of the memoir is feeling sorry enough for yourself not to make light of your personal tragedies, for there lies your subject matter.)

Why not write everything in my favorite voice? Because it would not be the best fit for everything I choose to write.

For example, if I used my memoir voice here, to discussing the sometimes-grim realities of how the publishing industry treats writers, I would depress us all into a stupor. Author! Author!’s goal is to motivate you all to present your work’s best face to the world; to achieve that end, I use a cheerleading voice.

Minion, hand me my megaphone, please.

To be blunt about it, what will work for one kind of writing aimed at one kind of audience will not work for another. I speak from experience here: I’ve written back label copy for wine bottles (when I was underage, as it happens), as well as everything from political platforms to fashion articles. Obviously, my tone, vocabulary choice, and cadence needed to be different for all of these venues.

(Some professional advice for anyone who should find herself writing wine descriptions: there are only a certain number of adjectives that may be safely and positively applied to any given varietal; nobody is ever going to object, for instance, to a chardonnay description that mention vanilla undertones. Go ask the enologist who blended the wine you’re supposed to be describing to give you a list of five, then start seeing how many of them you can use in a paragraph. Voilà ! Wine description!

See? Every writing project is a potential learning opportunity.)

Granted, not all of those writing gigs were particularly interesting, and I would not be especially pleased if I were known throughout recorded history as primarily as the person who penned the platitude tens of thousands of people read only when their dinner dates left the table for a moment and the only reading matter was on the wine bottle. Yet all of my current voices owe a great deal to the discipline of writing for that very specialized audience, just as playing a lot of different roles in high school or college drama classes might give a person poise in dealing with a variety of situations in real life.

Right after I graduated from college, I landed a job writing and researching for the LET’S GO series of travel guides. The series’ method of garnering material, at least at the time, was to pay a very young, very naïve Harvard student a very small amount of money to backpack around a given area, fact-checking the previous year’s edition and writing fresh copy.

Often, in my case, by firelight at a dubious campground: my per diem was so small that I slept in a tent six nights per week and lived on ramen cooked over a campfire. A trifle ironic, given that most of what I was writing was restaurant and motel reviews for places I could neither afford to eat nor stay.

You might want to remember that the next time you rely upon a restaurant review published in a travel guide. (See earlier comment about not all published writing’s necessarily being good.)

Let’s Go’s tone is very gung-ho, a sort of paean to can-do kids having the time of their lives. But when one is visiting the tenth municipal museum of the week — you know, the kind containing a clay diorama of a pioneer settlement, a tiny, antique wedding dress displayed on a dressmaker’s form, and four dusty arrowheads — it is hard to maintain one’s élan. Yet I was expected to produce roughly 60 pages of copy per week, much of it written on picnic tables.

I can tell you the precise moment when I found my travel guide voice: the evening of July 3, a few weeks into my assignment. My paycheck was two weeks overdue, so I had precisely $23.15 in my pocket.

It was raining so hard that I could barely find the motel I was supposed to be reviewing. When I stepped into the lobby, a glowering functionary with several missing teeth informed me angrily that the management did not allow outsiders to work there.

“Excuse me?” I asked, thinking that he had somehow intuited that I was here to critique his obviously lacking customer service skills. “I just want a room for the night.”

“The night?” she echoed blankly. “The entire night?”

Apparently, no one in recent memory had wanted to rent a room there for more than an hour at a stretch. The desk clerk did not even know what to charge.

(If you’re too young to understand why this might have been the case, please do not read the rest of this anecdote. Go do your homework.)

I suggested $15, a figure the clerk seemed only too glad to accept. After I checked into my phoneless room with the shackles conveniently already built into the headboard and screams of what I sincerely hoped was rapture coming through the walls, I ran to the pay phone at the 7-11 next door and called my editor in Boston.

“Jay, I have $8.15 to my name,” I told him, while the rain noisily drenched the phone booth. “The banks are closed tomorrow, and according to the itinerary you gave me, you want me to spend the night a house of ill repute. What precisely would you suggest I do next?”

“Improvise?” he suggested.

I elected to retrieve my $15 and find a free campground that night. Independence Day found me huddled in a rapidly leaking tent, scribbling away furiously in a new-found tone. I had discovered my travel writing voice: a sodden, exhausted traveler so astonished by the stupidity around her that she found it amusing.

My readers — and my warm, dry editor back in Boston — ate it up.

I told you this story not merely because it is true (which, alas, it is; ah, the glamour of the writing life!), but to make a point about authorial voice. A professional reader would look at the story above and try to assess whether a different type of voice might have conveyed the story better, as well as whether I maintained the voice consistently throughout.

Pertinent questions for any projected revision, are they not? I asked them of myself: how would a less personal voice have conveyed the same information? Would it have come across better in the third person, or if I pretended the incident had happened to a close friend of mine?

Appropriateness of viewpoint tends to weigh heavily in professional readers’ assessments, and deservedly so. Many, many submissions — and still more contest entries — either do not maintain the same voice throughout the piece or tell the story in an absolutely straightforward manner, with no personal narrative quirks at all.

What might the latter look like on the page? Like a police report, potentially. Let’s take a gander at my Let’s Go story in a just-the-facts-ma’am voice:

A twenty-one-year-old woman, soaked to the skin, walks into a motel lobby. The clerk asks her what she wants; she replies that she wants a room for the night. When the clerk tells her they do not do that, she responds with incredulity. The clerk gets the manager, who repeats the information. Noting the seven-by-ten wall of pornographic videotapes to her right and the women in spandex and gold lame huddled outside under the awning, flagging down passing cars, the young woman determines that she might not be in the right place. She telephones her editor, who agrees.

Not the pinnacle of colorful prose, is it? A contest judge would read this second account and think, “Gee, this story has potential, but the viewpoint is not maximizing the humor of the story.” She would subtract points from the Voice category, and rightly so.

Millicent would probably just yawn and mutter, “Next!”

Another technical criterion often used in evaluating voice is — wait for it — consistency. Having made a narrative choice, does the author stick to it? Are some scenes told in tight third person, where we are hearing the characters’ thoughts and feelings, while some are told in a more impersonal voice, as though observed by a stranger with no prior knowledge of the characters?

Your more sophisticated professional reader (Millicent’s boss, perhaps, who has been at it a decade longer than she has) will often also take freshness of voice and point of view into account. How often has this kind of narrator told this kind of story before?

Which brings us back to the desirability of copying what you admire. If imitation is the sincerest form of flattery — which I sincerely doubt — then the narrative choices of bestselling authors must spend a heck of a lot of time blushing. Or so I am forced to conclude by the many, many stories told by the deceased in the years following the success of THE LOVELY BONES, for instance, or the many, many multiple-perspective narratives followed hot on the heels of THE POISONWOOD BIBLE.

I’m not going to lie to you — there is no denying that being able to say that your work resembles a well-known author’s can be a useful hook for attracting agents’ and editors’ attention. (“My book is Sarah Vowell meets household maintenance!” “My book is BRIDGET JONES’ DIARY set in a rehab clinic!” “The story is SCHINDLER’S LIST, only without the Nazis or all the death!”) However, as the late great Mae West liked to point out, while copies may sell in the short term, for the long haul, what is memorable is originality.

Perhaps that is one of the best measures of how effective a book’s narrative voice is: three days after a reader has finished it, will she remember how the story was told? Individual phrases, even? In a generic-voiced narrative, usually not.

Of course, after Millicent and her cronies take all of these factors into account, whether the professional reader happens to LIKE the narrative voice is still going to weigh heavily into her calculations. That’s inevitable, and there’s nothing a writer can do about it — except to make her narrative voice as strong and true and individually hers as she can possibly can.

Because then one reader, at least, will be satisfied: you. Give it some thought, please, and keep up the good work!

Finding your voice, part II, or, why am I introducing you to a small, annoying bug?

My apologies to those of you looking forward to Sunday’s promised foray into book promotion. I shan’t bore you with the details of why it didn’t happen; suffice it to say that I will be really, really grateful when the universe stops finding such amusement in causing the lady with the cane to tumble over sideways. I’m hoping to do a couple of posts on subject this coming weekend, lenient gravity permitting.

I’m walking upright again today — Darwin would be so pleased — but I must confess, I’m feeling a bit stuffy-headed. It’s all in a good cause, however: my backyard lilac tree has been waving bushels of lavender flowers in my general direction. Very beautiful, very pollen-laden.

It reminds me of the small town — a village, really, ensconced within an agricultural preserve — where I grew up, in the Napa Valley. (Note to those not from those parts: please, whatever you do, don’t refer to the entire area as Napa; it makes the locals apoplectic. Napa is a well-developed city on the south end of the quite rural Napa Valley. If you’re thinking of vineyards, you actually mean the latter, and if you’re thinking of a quaint little tourist trap, you’re probably thinking of my home town, 20 miles north of Napa. Believe me, when you’re living there, the difference between a city of 130,000 and a town of 5,000 could not be greater.)

Tourists overrun the Napa Valley in the autumn, when the grapevines sport leaves ranging from bright green to mellow gold to sunburned red, but my favorite time there has always been the early spring. The vines are dormant then, blasted-looking and leaf-free, but the vineyards are full of knee-high fluorescent yellow mustard flowers: acres and acres of neon brilliance.

The local truism runs that if you don’t suffer from pollen allergies during a Napa Valley spring, you never will. Because I am inherently contrary, I never suffered from pollen allergies while I was growing up. Then, years later, I moved to Seattle, where the pollen is evidently virulent in a completely different fashion.

Particularly, I notice, lilac pollen. A-choo.

I bring this up, not merely so you will excuse me if I pause occasionally for a ladylike wipe of the nose, but as an apt metaphor for today’s topic, a continuation of Sunday’s discussion of voice. Let’s cut right to the central issue, as expressed by intrepid and curious reader Gordon’s comment:

Anne — How do we tell if our voice is actually ‘our voice’? Is there an easy answer, or do we rely on our early reader to tell us? Or our editor?

Terrific question, Gordon, and one that is surprisingly rarely discussed at literary conferences or in writing classes. There’s a pretty good reason for this: while craft is general, voice is individual. While craft must be learned — and should be learned, as a means of clarifying and amplifying one’s voice — authorial voice is, like talent, inherent. And, like talent, individual voice is not always apparent in even a very gifted writer’s early efforts.

Which is, I must admit, why my first response to Gordon’s question was, “Please, don’t expect your future editor to define it for you — by definition, the best arbiter for a truly original voice is its author.” Authorial voice can’t really be taught (although there are some writing teachers who would disagree with me on that point). It arises organically, often after years of cultivation.

And I already hear some disgruntled muttering out there. “A very pretty notion, Anne,” these mutterers say, “but we’re looking for practicality here, not philosophy. What precisely is voice, and why should I worry about whether my work exhibits a unique one?”

For those of you who have heard the term bruited about in literary circles but were afraid to ask for a definition, voice is that combination of tone, worldview, vocabulary, rhythm, vocabulary, and style that makes one author’s work differ from another’s, even if they are telling the same story.

It is, to put it as simply as possible, what makes YOUR work sound like YOU, and not like someone else. In a book with a strong, well-developed voice, every paragraph — indeed, every sentence — will be in that voice, a phenomenon the pros call consistency.

And that’s darned hard for a writer to pull off, particularly (as is often the case for those new to the craft) if the writer in question isn’t quite sure what her voice is. “Is my voice how word patterns appear in my brain?” she might catch herself wondering. “Or on the page of a first draft? Or is my voice what ends up in a final revision? And how is what I like to read in other writers’ work different — and the same — as my personal voice?”

Yes, in response to what half of you just thought exceedingly loudly, those are some mighty weighty questions, ones that a thoughtful writer could spend a productive lifetime answering. But think about it on a practical level: as a reader, don’t you expect consistency of voice in a published book? Haven’t you ever read a book where the tone, vocabulary, and/or style abruptly altered so much that it jarred you out of the storyline?

Millicent the agency screener has, alas. So have her cousin Maury, the editorial assistant, and their aunt, Mehitabel, the veteran contest judge. Lovers of literature that they are, it genuinely saddens them to see a voice that they have come to like and respect suddenly transmogrify into something else 150 pages into a manuscript. Or 50. Or 10.

And how do you think they are likely to react if the voice is uneven on page 1? Avert your eyes, children — it’s not a pretty image.

Nor are they alone in preferring consistency. Most readers dislike that feeling of being pulled out of the story, so pros tend to edit with an eye to removing it. The result: the authors we tend to love are those whose voices are so consistent that if we took a two-line excerpt from Chapter 2 and another from Chapter 8, we could tell that the same person wrote them.

“Golly,” say the scoffers we met above, “voice sounds awfully important. Why doesn’t every writers’ conference devote immense amounts of time to helping aspiring writers seek out and develop theirs?”

Beats me — unless it’s because by definition, teaching a group means catering to commonalities; to help a writer develop his voice, an instructor would have to read enough of his work to figure out what he does better than any other writer on the planet. That’s assuming, of course, that the instructor has the literary acumen to weed out those elements that are borrowed from other authors’ styles (more common than you might think), as well as the time to encourage the writer, draft after draft, to cater to his own strengths.

Kind of a tough brief for a one-time two-hour seminar with twenty students, no?

To be fair to conference organizers, most submissions do fall under the weight of formatting, grammar, and clarity problems long before your garden-variety Millicent would take issue with inconsistency of voice, so it does make some sense to offer instruction on those issues first. When a writer is still struggling to express herself clearly and in a way that will appeal to an established market, those are definitely the skills she should master up front. And it’s not all that uncommon for an aspiring writer only to begin addressing herself to acquiring craft skills until after she is relatively happy with the overall story she wants to tell.

Or, to put it another way, at the submission stage, if her manuscript is not in standard format, contains many grammatical errors, and is confusing to read, an agent or editor’s rending his garments and crying, “But the voice is not consistent!” is probably the least of her worries. Nor is it likely to be Millicent’s first concern if the story has been insufficiently thought-out.

But let’s assume that you’ve been working tirelessly on these foundational issues, and now are pondering Gordon’s question: how does a writer know when he’s found his voice?

Does his writing abruptly jell in a way it had not before — and, if so, will that appealing congealing be immediately apparent to him? Or will he stumble upon a passage when he is reading his completed manuscript IN ITS ENTIRETY, IN HARD COPY, AND OUT LOUD (I couldn’t resist) before responding to a request for pages, causing him to cry out, “Wow, I would like my entire book to read like this! I shall instantly drop everything to go back through this entire manuscript, page by page, line by line, to apply this engaging voice consistently throughout the book!”

Um, no, on all three counts. Not usually. Especially that bit where the writer realizes that if his newfound voice is going to work qua voice, he’s going to have to use it consistently throughout the manuscript.

So how does a writer discover her own voice? Well, for starters, it’s extraordinarily rare that an author’s distinctive personal voice shows up in her first writing projects, except perhaps in flashes. Why? Well, as much as we might like to think of ourselves as expressing ourselves as no one else does, doing so in writing is a rather difficult skill to master. Even for those most beloved of the Muses, it takes time, and it takes practice.

It takes, in other words, more than just sitting down and writing a complete draft of a book. That’s the first step, typically, not the last: most writers will experiment with quite a few voices, vocabulary levels, approaches to scenes, etc. in drafting their first book or two. And that’s perfectly fine: after all, how are you going to know what you can and can’t pull off, or even what you like in your own writing, if you don’t try a variety of styles?

That’s why, in case you’ve been wondering for the last few paragraphs, professional readers like Millicent, Maury, and Mehitabel tend to have a knee-jerk negative reaction to manuscripts featuring a smorgasbord of voice experiments. To them, inconsistency of voice is a sign that the writer in question has not yet decided what she wants the book to sound like overall. So why not throw that fish back into the sea, to wait for it to grow bigger, stronger, and more consistent?

Okay, so that analogy crumbled a bit at the end; try as I might, I can’t figure out what an inconsistent fish would act like. (Attempt to breathe air every second Thursday of the month, maybe?) But that’s precisely why I used it: see how jarring even a single consistent sentence can be to a narrative?

Besides, most writers begin by imitating the voices of authors they admire, so it’s not at all uncommon to see a manuscript scene that contains a patch that reads a bit of Annie Proulx, a terse dialogue reminiscent of Ernest Hemingway, and a blistering line or two of Jay Mcinerney cynicism, all tied together by a few straightforward declarative sentences.

Tell me, out of all of those disparate elements, which part is the writer’s own voice? Is it really Millicent, Maury, or Mehitabel’s job to guess?

Most of the time — and you might want to sit down for this one, campers; some of you may find what I have to say next rather discouraging — a writer comes to recognize her own voice because over time, it becomes the most natural for her to use. Its consistency sits up and announces itself to be how she should be writing all the time.

Which means, Gordon, that you may not yet know what your voice is, but you will probably recognize it when you see it.

I know, I know; that sounds very woo-woo, but I swear that it’s true. For most good writers, one day, after seemingly endless writing, a personal voice abruptly emerges and takes over the narration. Like all of those lilac and mustard flowers bursting into bloom on a rainy spring morning, its essence will waft over the page, marking it.

And the writer says, “Hey, I like that. I think I’m going to write like that all the time.”

To complicate matters, just as those early spring flowers make some people smile and others sneeze violently, a strong, original voice will not appeal to all readers. That’s why, in case you had been wondering, no not all published writing exhibits an distinct narrative voice. The more distinctive the voice, the greater the risk, in a way — it can irritate in a way that a merely clear, pleasant, generic voice may not.

Oh, you didn’t know that was one of the many reasons that journalists are trained to sound so much alike on the printed page? They are urged to keep their individual voices out of the story, so as not to distract the reader.

The ambient mutters have been steadily growing to a near-roar. “Okay, now I’m really confused. If I understand you correctly, it’s safer not to write in an individual voice — but if I want to be known for the beauty of my writing, I need not only to do just that, but to do it consistently throughout my manuscript.”

Nicely summarized, ghostly mutterers: it is a genuine paradox. It’s also a choice that every writer has to make for himself. Or herself, as the case may be. (I’ve alternated so often in this post that I’m not sure whose turn it is.)

Feet continue to shuffle out there, and hips to shift uncomfortably on computer chairs. “What I’m really asking, I guess,” my muttering friends continue, “is what separates a good voice from a bad voice. Or, to put it another way, how on earth can an agent, editor, or contest judge rate voice on anything but personal preference?”

Remember last autumn’s Querypalooza series, when I pointed out early and often that contrary to popular opinion amongst the aspiring, a savvy writer shouldn’t want to sign with just any agent — she should aspire to signing with one who truly loves her work? This is precisely why: response to voice is quite individual. No matter how beautifully-written a manuscript may be, it’s not going to be every agent’s proverbial cup of tea.

Is the common rejection line I just didn’t fall in love with it making a bit more sense now?

In order to represent you successfully, an agent needs not only to like your voice, but be able to identify what is individual about it lucidly enough to be able to go to an editor and say truthfully, “Look, based on the books you have been buying lately, I think you are going to like this manuscript, for these twelve reasons…”

Because a runny nose is apparently conducive to decoding cosmic mysteries, allow me to add: that’s why nonfiction is reputed to be easier to sell than fiction; fiction is inherently much more heavily reliant upon voice, right? Particularly literary fiction, where the freshness and strength of the voice is the book’s primary selling point.

And, let’s face it, no matter how strong a story is, few readers will finish a novel if they dislike the author’s voice. “I just couldn’t get into it,” they will say, setting it aside.

Nonfiction, on the other hand, is much more concerned with the interest of the subject matter, the slant of the approach, and — yes, I must say it — the credentials of the author. (Oh, stop your groaning — you didn’t honestly expect me to talk about selling NF without bringing up platform, did you?) Just think of the many, many nonfiction books sold each year by journalists: while a strong voice may be an additional selling point, clarity is generally the main desiratum.

Unless, of course, it’s a memoir, where voice is nearly as important as in a novel.

Is your head spinning from all this? Not to worry; tomorrow, I shall discuss voice choices in greater detail. (And I’m going to try like heck to do it on the literal morrow, not merely the next time the pratfall-happy medical gods happen to allow me enough energy to post.)

For today’s purposes, it’s less important that you come away from this with a clear idea of the strategic uses of voice than to realize that you may well have more than one voice lurking inside your creative mind at this very moment — and that before you can make it consistent throughout the narrative, you are going to have to (a) identify the contenders, (b) decide which one you want to dominate the narrative, and (c) set aside some serious revision time for implementing that decision. If, as sometimes amuses the Muses to facilitate, you happen to like more than one of your voice options, you might want to (d) give some thought to which would be most appropriate to the book project at hand (which would fit most comfortably into your chosen book category, which is most likely to appeal to your target readership, etc.), reserving other options for your second, third, or fourth book.

Hey, no one ever said that developing a unique voice was easy. Or uncomplicated.

“I’ve got just one more question,” the disgruntled mutterers who have been dogging me throughout this post are piping up to say. “Why did you decide to start talking about voice at the end of the Pet Peeves on Parade series? If my authorial voice is what is most distinctively me in my manuscript, shouldn’t we have been talking about it all along?”

Ah, but remember what I said above about the usually progression of the authorial learning curve: first comes story, then craft, with voice discovery generally lollygagging to a distant third-place finish. That’s necessary and appropriate — and, frankly, it’s a heck of a lot easier for a writer who has already invested energy in polishing up storytelling and craft issues to tinker with voice than one who has not.

There is more to revising a manuscript than deciding whether this sentence is necessary, that paragraph is clear, or a scene tells rather than shows. All of these are necessary, of course — but ideally, a revising writer should also be asking himself, “But does this part of the manuscript fit with the overall voice? Does it sound like ME?”

Just a small, noisy bug to stick in your ear while you’re reviewing your manuscript in the wake of the Pet Peeves on Parade series. Allow it to jump around freely until next time; perhaps it will awaken an exciting aspect of your voice that’s been napping, waiting until you were ready to hear it. Keep up the good work!

Pet peeves on parade, part XXII: a stay of execution for some of those oft-doomed darlings, or, how can I tell which of this array of beauties to keep?

Because we have been concentrating quite heavily on craft issues of late — and very satisfying it has been, too — I had planned to devote Memorial Day weekend entirely to book promotion skills: author interviews, book trailers, guest blogs, and similar increasingly essential but seldom discussed wrenches for the first-time author’s toolkit. I do plan on getting to that material tomorrow. I realized this morning, however, that due to a heavily-booked last couple of days, I had left those of you in the throes of revision without a meaty homework assignment for the long weekend.

That will never do, will it? You might have to resort to sending out a few more queries, writing fresh pages, spending time with your kith and/or kin, or some other non-revision-related activity.

Practice is essential for building up the revision portion of that toolkit — and not just experience correcting one’s own manuscript on a sentence level. Being able to produce and polish a lovely sentence is, after all, the best-known part of an author’s job description. It often comes as a surprise to first-time novelists and memoirists, though, that most of the feedback agents, contest judges, and yes, even many editors give is not line-specific, but general requests to change precisely the type of patterns we’ve been discussing throughout this series: ramping up the showing, rather than the telling; tinkering with the pacing to keep the reader turning pages; revealing more character complexity in the dialogue, and so forth.

You didn’t think I’d been going on and on about these matters just to get your work past Millicent the agency screener, did you? Once you’ve landed the agent of your dreams, you will need to be able to translate sometimes rather vague revision requests (which can run the full gamut from cut out all of the semicolons to more should happen in the first 50 pages to does your protagonist’s brother absolutely have to be gay?) into concrete changes on the manuscript page. Sometimes very quickly.

How quickly, you ask with fear and trembling? Well, let me put it this way: my agent once called me on Thanksgiving to ask if I could rewrite the last third of a novel to an editor’s specifications before Christmas. I had it on her desk in three weeks.

Well may you react with horror — but if you’re not afraid of having your hair turn white on the spot, think about how much more difficult that would have been to pull off if I hadn’t already amassed a pretty hefty array of tools already honed in my writer’s toolkit.

That hellscape you just envisioned is a fairly standard experience for first-time novelists and memoirists, by the way. See why I am constantly badgering you to improve your revision skills, even if you happen to have a brilliant manuscript already in hand? You never know when you’re going to need ‘em.

Want to know what the most challenging part of revising on a deadline? Maintaining consistency of voice. It’s terribly easy to become so fixated on details — or on a certain part of the text — that one ends up with the requested changes, true, but also with a Frankenstein manuscript.

For those of you new to Author! Author!, a Frankenstein manuscript meanders in voice, tone, perspective, structure, and/or style; like the body parts of Dr. Frankenstein’s creature, the text may create the illusion of a whole entity, but it lacks the spark, the true-to-life continuity of a story told from beginning to end by a consistent authorial voice. Often, FM tendencies are the result of multiple or partial revision; even more often, they spring from a writer’s learning the tricks of the trade while writing a book.

How do I know? You’d be surprised how frequently the voice is quite different at the end of the manuscript than at the beginning. Or polished in parts, but rough in others.

Part of the point of this series has been to help you identify these FM tendencies in your own work. To that end, we’ve been talking a great deal about what to take out of a manuscript. Today, I would like to discuss what to leave in, or even what you might want to add.

And the masses rejoice! “Oh, that’s such a relief, Anne,” burnt-out revisers shout from every corner of the globe. “I’ve been working my fingers to the elbow, excising redundant text, spicing up my dialogue, and, of course, getting rid of all of those ands, all the while steeling myself for the inevitable moment when you would talk me into axing my favorite sentences and phrases. Because, after all, we’ve all been told time and time again to kill your darlings. But may I, kind lady, dare hope that you’re going to tell me to keep a couple of my favorites?”

Oh, you poor dears — no wonder you’ve been quivering in your boots. How could you not be, when writing teachers all over North America have been shouting at their students to axe their favorite bits of prose since practically the moment the classic piece of advice fell out of Dorothy Parker’s well-rouged lips sometime during Prohibition?

Well, I’m not going to do it. While a willingness to consider cutting even one’s pet bits is indeed useful, in my experience, most talented writers — published and as-yet-to-be-published alike — actually have a pretty good sense of the little things that shine in their manuscripts. They may not be right that all of the pretty bits are indispensable to the story they are telling, but they usually know which sentences sing and which merely croak.

Especially if the writer in question has been honing her craft, her pet parts of the text are likely to be telling little details, original, fresh, surprising specifics that bring joy to the eyes of agents, editors, and contest judges when they appear nestled in a manuscript — particularly on the first page of the text, where they act like miniature neon signs reading, “Hello? This one can WRITE!” causing Millicent to sit up straight for perhaps the first time that screening day and cry, “By gum, maybe I should not toss this one into the rejection pile.”

As lovely as eliciting this reaction is, there is more to catching a professional reader’s attention than a charming and detailed first page, I’m afraid. Of course, it’s a necessary first step to that reader’s moving on eagerly to the second, and the third, and so forth. Yet an initial good impression is not enough, however much writing teachers emphasize the importance of including an opening hook: as I believe I may have mentioned before in this series, in order to wow an agent into asking to see the entire manuscript, or into reading the entirety of the one you’ve already sent, the impressive writing needs to continue consistently throughout.

Ah, some of you formerly joyous revisers have wilted a bit, haven’t you, under the realization that keeping your favorite writing may require more work than cutting it wholesale? “But Anne,” you whimper, “how can a revising writer tell if the proportion of telling little details falls off throughout a manuscript enough to harm the narrative? More importantly for submission purposes, what density of telling details is enough to continue pleasing a professional reader’s eye?”

Excellent questions both, revisers: we’re all aware that the answer to the first is not necessarily the answer to the second, right? The first is largely a matter of personal style, after all, as well as the narrative expectations of a particular book category. Some writers wrangle generalizations better than others, after all. Generally speaking, though, the higher the proportion of exquisite detail to generalization, the more literary the writing; the more summary statements predominate, the lower the expected reading level of the audience.

And if the three repetitions of general in those last two paragraphs drove you crazy, I’m proud of you. You’ve been doing your editing homework.

In answer to the indignant collective gasp I hear echoing about the cosmos, literary is not simply a synonym for high-quality when we’re talking about writing. Let’s face it, there is plenty of good fiction writing that isn’t literary fiction — and plenty of excellent writing that isn’t literary. Just as the various striations of YA presume specific reading levels, literary fiction assumes a college-educated audience, or at any rate readers with a college-level vocabulary.

Thus, literary fiction is a book category, not a value judgment. It is quite possible, however, to bring a literary voice to other book categories — one sees literary-voiced memoir (like, for instance, Barbara Robinette Moss’ extraordinary CHANGE ME INTO ZEUS’ DAUGHTER from time to time, and many breakout novels are literary-voiced genre works.

That doesn’t mean, however, that a highly literary voice would be appropriate to every book category — or indeed, to every story. Only you, as author, can decide the best voice for your story, but in order to figure out the detail/generalization level appropriate to your book category, you can pick up some external clues.

How? By keeping up with the market in your chosen field, of course. I’ve said it before, and I’ll say it again: unless you are willing to read recent releases in your chosen book category — as opposed to what was coming out 5, 10, or 50 years ago — you’re going to have a much harder time querying, submitting, and yes, revising your own work.

Why? Because you won’t know what the current expectations and conventions are. Case in point: detail vs. summary statements.

Think about it: could you really get away with a summary sentence like, “She had legs that stretched all the way from here to Kalamazoo,” in a genre other than hardboiled mystery, bless its abstraction-loving fan base? (All right, I’ll admit it: one of the all-time best compliments I have ever received came from a writer of hardboiled; he commented on a dress I was wearing by telling me, “You look like trouble in a B movie.” I shall continue to cherish that to my grave.)

That’s one of the many, many reasons agents and editors tend to expect aspiring and published writers alike to read a whole lot of recently-published books within the category they write, in case any of you conference-goers out there had been wondering: to gain a working sense of the abstract/concrete statement ratio habitual readers of that type of book will expect to see. Some other reasons for keeping up with the latest releases: learning what that particular readership likes, figuring out what is and isn’t appropriate vocabulary for that specific readership, gaining currency with what’s being published right now, rather than in, say, 1858, and other practical benefits.

Some of you are sniffing disdainfully, aren’t you? “But Anne, none of this can possibly apply to me or my manuscript. My book is ART, you see: it is totally original. It cannot be forced into an artificial category.”

I can understand why you might feel that way, oh sniffers, but I have a news flash for you: there’s no such thing as a published book that doesn’t fall into a particular book category, no matter how genre-busting it may be. It’s simply how agents, publishers, and booksellers think of books. (If that is indeed news to you, and for some tips on figuring out which conceptual container might best house your manuscript for marketing purposes, please see the HOW TO FIGURE OUT YOUR BOOK’S CATEGORY posts on the archive list at right.)

Because that’s the case, the pros’ eyes tend to glaze over whenever an aspiring writer refuses — or even hesitates — to say to which category his manuscript belongs. To them, that just sounds like, you guessed it, a lack of familiarity with the current book market.

It’s not enough, though, to have a general (there’s that word again!) sense of what kind of writing is currently highly regarded in your chosen category. You also need to get a feel for your own personal style. Before you can decide where you want to pitch your manuscript on the detail scale, you need to figure out where the telling details already tend congregate in your work — and where they do not, so you may work toward overall voice consistency.

Which brings us right back to close textual analysis, doesn’t it? Funny how that worked out. Whip out your trusty marking pens, campers, and try this experiment:

1. Print out three chapters of your manuscript: the first, one from the middle, and one toward the end of the book.

Don’t use the final chapter; most writers polish that one automatically, doubtless the effect of our high school English teachers making us read the final pages of THE GREAT GATSBY so often. Second or third from the end will give you a better idea of your voice when you’re trying to wind things up.

Do print out Chapter 1, though, because if Millicent reads any of them at all, she will start there.

2. Make yourself comfy someplace where you will not be disturbed for a few hours, and start reading.

Easier said than done, of course, especially for those of you with young children gladdening your daily lives, but this isn’t relaxation: this is work. So don’t you dare feel guilty about taking the time to pore over your prose.

Yes, I know: your three-year-old will not be all that impressed that I said so. But you owe it to your writing to get to know your own voice.

3. While you are reading, highlight in nice, bright yellow every time the narrative gives information about a character in summary form.

Yes, this will be a phenomenal amount of work, but trust me: it will be worth it. Mark everything from Angelique felt envious to Maxine was a shop welder of immense proportions to Zeb was a compassionate soul, drawn to injured children, limping dogs, and soup kitchens.

4. Now use a different color of pen — red is nice — to underline any character-revealing information that the narrative conveys indirectly, through specific detail or speeches that demonstrate a characteristic or an environment that is reflective of a character’s internal mood.

Remember, you are not judging the quality of the sentences here — you are looking for passages that encourage the reader to draw his or her own conclusions about what the character is like, rather than simply stating it as a fact. To revisit the trio from above, red-marked sentences might include:

Unable to contain herself, Angelique surreptitiously poked her rival with a pin, or

Maxine’s broad shoulders barely fit through the doors to her metal shop, or even

Zeb was late for work again, having been sidetracked by a child’s scraped knee, a search for the same little girl’s lost cocker spaniel, and the absolute necessity to track down and fund the homeless person he had been forced to overlook yesterday because he’d already given away the last dollar in his pocket.

Beginning to spot some patterns? Good. Now that your manuscript is color-coded to tell you at a glance what your summary statement/telling detail ratio is, how consistent is your narrative being about preserving those proportions?

That’s a big concept to get your mind around, I know. While you’re pondering, let’s get back to that colorful text.

5. Now that you’ve identified these different species of sentences, double-check immediately before and after the indirect indicators in red for summary statements telling the reader precisely how these dandy little details should be interpreted. Circle bottom-lining conclusion statements in a third color — let’s say green, and complete the Rastafarian triumvirate.

Such summaries tend to lurk in the environs of telling details — usually unnecessarily, as vivid details by definition speak for themselves. You may find them elsewhere, naturally, but these will be the easiest to spot.

6. For each green-marked sentence, ask yourself, “Self, is this summary absolutely necessary here, or does the indirect statement cover what I wanted to say? Could it in fact be cut, and would the manuscript be both shorter and better for it?”

Applied consistently, this question can strip a lot of unnecessary verbiage from a manuscript relatively painlessly. It’s a good strategy to know, because it’s often difficult for a writer to notice redundancy on a page he has written himself — from a writerly perspective, saying something in two different ways often just looks like creative emphasis.

Or — and this is more common — the writer may not trust the reader to draw the correct conclusion from the more delicate indirect clues, and so rush to provide the logical extrapolation. But readers are pretty smart, especially those lovers of good writing (in every sense) who dote on marvelously revealing details.

Again, that’s not to say that specifics should trump generalities every time. Abstract statements that bottom-line a character’s ever-changing array of feelings, thoughts, and actions (Eileen was morose, Teddy was sexy, Elvira was a tall, cool hunk of woman, etc.) can save a lot of time in a narrative, quickly providing the reader a sense of what’s going on and who is doing it.

Sometimes, that can come in very handy. In a scene where the action is pretty mundane, a swift summary statement like Bernadette spent the next fifteen hours yawning her way through book shelving can act like a fast-forward button for the narration.

The effect can be even greater when there is a lot going on. When an action scene suddenly requires fifteen thugs to jump Our Hero, describing each one individually and in a nuanced manner would slow the scene down to a crawl — which, inevitably, would convey the impression that O.H. is being beaten up in slow motion.

Fast-paced action deserves fast-paced narration, short, tense sentences that get the blood pumping. Short, to-the-point summary statements like Edmund ducked sideways. The anvil thudded into the wall behind him. may well serve the scene better than long, lyrical, detail-rich ones that go on for line after line.

Oh, you wanted a second example? Okay: As Edmund veered sideways, the rush of air by his ear, percussive and harsh, reminded him of that long-ago summer of fireflies and BB guns, unwashed berry juice climbing up to his elbows after braving the bees for an afternoon’s blackberrying. Funny, how something as dangerous as an anvil flung at his head could awaken such long-dormant memories.

Yes, the second set was prettier — but which would work best for this SPECIFIC action scene in this SPECIFIC story, told in this SPECIFIC voice?

By contrast, concrete characterization statements depict what a character is saying, doing, feeling, and so forth in a particular moment. In a story told primarily through concrete statements — and again, writing with a high concrete/abstract ratio is considered more stylistically sophisticated — the narrative expects the reader to draw conclusions about what characters are like based upon an array of specific actions, feelings, words, and so forth, rather than simply providing a summary statement.

Does that distinction sound at all familiar? It should: this is yet another manifestation of everyone’s favorite writing bugbear, the difference between showing and telling.

Yet constructing an effective narrative is not as simple as eschewing the latter and embracing the former. Obviously, every manuscript ever produced needs both abstract and concrete statements. Because, let’s face it, there’s no such thing as a chapter, paragraph, or even sentence that’s appropriate for every book in which the creative mind might choose to have it appear.

Context matters — and so does book category.

Avoiding summary statements wherever possible may serve a high-end women’s fiction writer very well, for example, but actually harm certain types of genre novel. The rash of semicolons that might make an academic book look learned is unlikely to fly in a Western — but you’d be surprised how much more acceptable it would be in a science fiction novel. And while those of us devoted to literary fiction do occasionally marvel at a story intended exclusively for a college-educated readership written in very simple language, the vocabulary range of most literary fiction is quite different from that of well-written YA.

But you knew that already, right?

And don’t even get me started on how much more acceptable rampant summary statements are in most types of nonfiction than in fiction. Memoirs in particular tend to rely upon them pretty heavily.

Why? Well, as a reader, how eager are you to hear every detail of what happened to even a very interesting real-life narrator over a two-year period? If a memoirist steers too clear of abstract statements like Auntie Mame’s famous My puberty was bleak, she’s going to end up expending quite a bit of precious page space on illustrating just how bleak it was, right?

So much for my carefully non-judgmental speech on the subject of abstract vs. concrete statements. It is worth noting, though, that on any given day of manuscript-screening, your garden-variety Millicent sees a whole lot more summary sentences than concrete ones.

Which, obviously, can render a genuinely original detail quite a refreshment for weary professional eyes. So, generally speaking (ooh, there’s that pesky word again), if you can increase the frequency with which such concrete details appear, you’ll be better off.

Ready to take gander at the ratio in the manuscript you’ve been submitting — or are planning to submit to professional scrutiny anytime soon? Fantastic. Let’s revisit those yellow, red, and green pages from above. But this time, grab a fourth color of pen –- how would you feel about embracing something in the purple family?

7. Mark all the sentences where your protagonist (or any other character whose thoughts are audible to the reader) thinks a response to something that has just happened, instead of saying it aloud or the narrative’s demonstrating the reaction indirectly.

Remember, you’re not judging the quality of writing by determining what to highlight, or sentencing any given observation to the chopping block by marking it. You are simply making patterns in the text more visible.

These kinds of sentences are hard to show out of context, so let me mark up a bit of text for you. The sentences destined for purple overcoats are in caps:

I CAN’T BELIEVE SHE SAID THAT, ZACHARY THOUGHT.

WHY WASN’T HE ANSWERING? “What’s wrong?” Nanette asked, rubbing her tennis-sore ankles. “Are you feeling sick to your stomach again?”

OH, WOULD ONLY THAT HIS ONGOING DISSATISFACTION WITH THEIR MARRIAGE STEMMED FROM A SOURCE AS SIMPLE AS NAUSEA. WAS HIS WIFE HONESTLY SO SOULLESS THAT SHE COULDN’T FEEL THEIR WELL-MANICURED LAWN CREEPING UP THE DOORSTEP TO SMOTHER THEM IN SEDUCTIVE NORMALCY? “No, I just had a long day at work.”

Everyone clear on the distinction I’m making here? Excellent. Now humor me a little and dig up a fifth color of pen — blue, anyone?

8. Mark any sentence where your protagonist’s reactions are conveyed through bodily sensation of some sort. Or depicted by the world surrounding him, or through some other concrete detail.

You’re probably going to find yourself re-marking some of the red sentences from #4, but plow ahead nevertheless, please. Starting to notice some narrative patterns? Expressing character reaction via physicality or projection is a great way to raise the telling little detail quota in your manuscripts.

Does this advice seem familiar? It should, for those of you who regularly attend writing workshops or have worked with an editor. It is generally expressed by the terse marginal admonition, “Get out of your character’s head!”

I wish feedback-givers would explain this advice more often; too many writers read it as an order to prevent their characters from thinking at all, ever. But that’s not what get out of your character’s head! means, at least not most of the time. Generally (ooh!), it’s an editor’s way of TELLING the writer to stop telling the reader about the character’s emotional responses through dialogue-like thought. Instead, (these feedback-givers suggest) SHOW the emotion through details like bodily sensation, noticing a significant detail in the environment that highlights the mood, or…

Well, you get the picture. It’s yet another way that editors bark at writers, “Hey, you — show, don’t tell!”

What will happen to your manuscript if you take this advice to heart? Well, among other things, it will probably be more appealing to Millicent — because, believe me, protagonists who think rather than feel the vast majority of the time disproportionately people the novels submitted to agencies and publishing houses.

And when I say vast majority of the time, I mean in practically every submission they receive. To put it bluntly, a novel or memoir that conveys protagonist response in ways other than thought a significant proportion of the time will at very least enjoy the advantage of surprise.

Why are characters who think their responses — essentially summarizing what they might have said or done in response instead of saying or doing it — so very common, especially in memoir? One theory is that we writers are so often rather quiet people, more given to thinking great comebacks than saying them out loud.

A girl’s best friend is her murmur, as Dorothy Parker used to say.

Or maybe we just think our protagonists will be more likable if they think nasty things about their fellow characters, rather than saying them out loud. That, or there are a whole lot of writers out there whose English teachers made them read HAMLET one too many times, causing them to contract Chronic Soliloquization Disorder.

Whichever it is, Millicent would be happier about most submissions in practically every book category if they exhibited this type of writing less. Done with care, avoiding long swathes of thought need not stifle creative expression.

Don’t believe me? Okay, let’s revisit our little scene of domestic tranquility from above, this time grounding the characters’ reactions in the flesh and the room:

By the time Nanette was midway through her enthusiastic account of the office party, Zachary’s stomach had tied itself into the Gordian knot. The collected swords of every samurai in the history of Japan would have been helpless against it.

“Zach!” Nanette’s back snapped into even greater perpendicularity to her hard chair. “You’re not listening. Upset tummy again?”

He could barely hear her over the ringing of his ears. He could swear he heard their well-manicured lawn creeping up the doorstep to smother them in seductive normalcy. The very wallpaper seemed to be gasping in horror at the prospect of having to live here a second longer. “I just had a long day at work.”

See the difference? The essentials are still here, just expressed in a less obviously thought-based manner. The narrative’s gotten out of the characters’ heads — and stepped right into their bodies.

Go back and take another look at your marked-up manuscript. How blue is it? How heavily purple is that prose? (Sorry; I couldn’t resist setting you up for that one.)

No, but seriously, it’s a good question: all of the types of sentence you just identified are in fact necessary to a successful narrative, so ideally, you have ended up with a very colorful sheaf of paper. Using too many of one type or another, believe it or not, can be boring for the reader, just as using the same sentence structure over and over lulls the eye into skimming.

If you doubt this, try reading a government report sometime. One declarative sentence after another can be stultifying for the reader.

The telling details of your manuscript will be nestled in those red- and blue-marked sentences, Note how frequently they appear in your chapters. If you find more than half a page of yellow and/or purple between patches of darker colors, you might want to go back and mix up your abstract/concrete ratio more.

If you find any pages that are entirely yellow and/or purple, I would suggest running, not walking, to the nearest used bookstore, buying three or four battered paperback editions of books that sell well in your chosen genre, and carting them home to perform the five-marker experiment on them. Could you revise your manuscript so that the color ratio in it replicates that in those books?

Yes, this is a time-consuming exercise, now that you mention it. A test like this is rather nerve-wracking to apply to your own work, but it’s a great way to start getting in the habit of being able to see your pages as someone who does not know you might. (If you want to get a REALLY clear sense of it, trade chapters with a writer you trust, and apply the same experiment.)

At the end of it all, however, you will have a much, much clearer idea of what your narrative voice sounds like — not only at its best and worst, but when it is just trying to do its job. You’ll gain a sense of what it sounds like when you’re tired or excited, trying desperately to get a thought down before it vanishes or having the time to allow your words to revel in their own beauty.

Once you gain that working sense of your own voice, editing your own work will become easier, I promise. You’ll be able to spot the telltale signs that the narrative has slipped away from it; you may even come to feel the drift before the words hit the page.

It sounds like magic, but it isn’t: it’s narrative consistency.

What does all of this have to do with saving your darlings? Plenty. How wonderful would it be if your best writing did not jump out at the reader because the entire manuscript was that good?

A lovely thought, isn’t it? Your darlings will be comfortably housed in a strong, sure narrative; they may — and this happens more than one might think — be your pets because they are already written in your personal narrative voice.

But you won’t know that for sure until you know your voice inside out, will you? Keep up the good work!

Pet peeves on parade, part XIX: there was something about his eyes, something indescribable…



I could not allow another week to end, campers, without filling you in on yet another common professional readers’ pet peeve. Specifically, one that drives your humble servant up the wall, not only because it is ubiquitous in manuscript submissions, but because when it does appear, its context usually makes it pretty obvious that the writer who penned it considers it (a) original, (b) philosophical-sounding, or even profound, and (c) pretty darned good writing, rather than what it actually is: (a) a hackneyed phrase, (b) descriptively vague, and (c) see (a) and (b)

What is this pervasive descriptive shortcut, you cry, famous for causing gentle souls like me — and our old pal, Millicent the agency screener — to rend our garments and wail when good writers foist it upon us? Let’s see if you can spot it in its natural habitat.

Here are five sterling examples of it, ripped from five different manuscripts. Let the garment-rending begin!

“If that’s really the way you feel, I have nothing more to say.”

Something in his eyes made Aileen pause, reconsider, turn back. “What is it you’re not saying, Jeremiah?”

He smiled, slowly, cruelly. “Ah, that would spoil the horrible surprise, wouldn’t it?”

Did anything in that exchange strike you as odd? If you are shaking your head at the computer screen, you’re not alone — most aspiring writers would see nothing wrong with it.

Millicent, to put it mildly, would. To gain a sense of why, let’s examine the phenomenon in another incarnation.

A feeling washed over Emily, strong and powerful. She couldn’t have put it into words, even to her closest friends, but it shook her to the core of her being.

“Yes!” she cried, startling everyone in the courtroom. “I shot the sheriff!” She turned to her incredulous husband. “But I swear to you, Archibald, I did not shoot the deputy.”

See any similarity between those last two examples? Millicent would. She’d also spot a definite familial resemblance between both of them and this:

Oliver walked her forward, keeping his hands over her eyes. Some ten feet of awkward stumbling later, he gently removed them. “Look.”

Perdita gasped. A vista of indescribable beauty spread out before her. “Oh, my! Why hadn’t I noticed this before?”

“Beats me.” Oliver returned to his game of solitaire. “I would have thought the Grand Canyon was kind of hard to miss.”

Starting to feel an inkling of Millicent’s well-justified irritation? One more time, maestro, please.

The audience swayed on its feet, blasted by the power of Mervin’s voice. It was not what he said, precisely, or even the words he chose to express it that moved them so strongly: it was an indefinable manner, a confidence that told them as surely as if he had shouted it that this man was telling the truth.

It’s begun to feel redundant, hasn’t it, even though I assured you at the outset that each of these examples came from a different source? Welcome to the world of the agency screener: if 35 out of the 127 first pages Millicent reads today contain the same descriptive shortcut — certainly within the bounds of possibility, with a trope this popular — Instance No. 34 is going to seem as repetitious as if it had appeared on the same page as Instances Nos. 28-33.

“Not this again!” she mutters, rending her aforementioned garments. “Show me something original, I beg you!”

We could feel smug, of course, that Millicent has just fallen into precisely the same phrasing trap to which she is objecting: the writer would be entirely justified in inquiring what precisely she had in mind. We could also point out that it isn’t particularly fair to the writer of Instance No. 30 that a professional reader might well have been more annoyed by the sight of this descriptive shortcut than she was by Instance No. 2. And who could fail to feel for the aspiring writer who decided that Instance No. 34 is just what his page 1 needed but did not call upon the descriptive device again for another 273 pages being treated as precisely as repetitious as the writer who elected to place Instances Nos. 5-9 all on the same page?

Oh, you don’t think that really happens? Au contraire, mes amis. I can beat that record in two sentences flat.

There it was again, that odd, vague sensation. It told Erminia without words that something, somewhere, somehow, was wrong.

What sensation?” Millicent demands, ripping her cuffs to shreds. “What is Erminia feeling, precisely? What does she think is wrong, and for what possible narrative reason has the writer chosen to hide the content of her fears from the reader?”

You must admit, these are perfectly reasonable questions. After all, it’s the writer’s job to describe what’s going on in sufficient detail for the reader to be able to picture it, not the reader’s job to fill in the details when the writer prefers to remain vague.

You wouldn’t know it, though, from a hefty minority of the submissions that cross Millicent’s desk on a daily basis. Apparently, there are a whole lot of aspiring writers who believe — wrongly, according to the overwhelming majority of professional readers — that leaving crucial sensations, thoughts, intuitions, and even physical descriptions to the reader’s imagination is not only permissible, but stylish. It’s hard to blame them, really: unless one happened to have had the privilege of reading many manuscripts or contest entries back to back, one wouldn’t have any idea just how common this descriptive shortcut is.

Trust me, it decorates many, many first pages. And contest entries. And dialogue. You’d be astonished at how many novels (and memoirs, actually) open with this well-worn trope — it’s an extremely popular (and thus Millicent-annoying) means of establishing suspense from line 1.

A noise came from behind her, causing Jemima to jump. Silly to be so nervous, when she had been through these woods more times than she could count. Admittedly, she had never been carrying quite this heavy a load of goodies for her grandmother, bread and sausage and pears and three whole roasted chickens.

There it was again. Something was following her; she was sure of it now.

Already, Millicent’s collar is in tatters. “What noise?” she wails, beginning on her right sleeve. “What did it sound like? What does she think is following her, and upon what auditory clues is she basing that conclusion. Also, what do three ands in a row add to this description that would not be adequately conveyed by the grammatically correct bread, sausage, pears, and three whole roasted chickens?”

Does the general pallor that just spread over half my readership’s faces indicate that some of you were under the impression that featuring this kind of and repetition within a single sentence was (a) stylish, (b) technically correct, (c) a narrative choice unlikely to annoy Millicent if done more than once every 50 pages or so, (d) a narrative choice unlikely to annoy Millicent if done more than every 50 lines or so, (e) a narrative choice unlikely to annoy Millicent if done more than once per paragraph, or (f) all of the above? I’m afraid I have some bad news for you, then.

It’s even worse news if you happen to subscribe to the rather pervasive school of thought that holds that regardless of whether the point of view is in the first, second, or third person — heck, even if it is from the omniscient perspective of Somebody Up There who can pry into every character’s mind — it is always an effective writing technique to make the narrative voice sound like someone speaking out loud in casual conversation in the year in which the manuscript was written. While this can work beautifully for novels and memoirs set in the recent past and written in the first person, chatty contemporary spoken word styles will not fit comfortably with every storyline.

It’s especially jarring in stories set in eras of the past when people spoke more formally — which is to say pretty much anytime prior to the last decade. Every era has its own slang, of course, but there’s no denying that the vagueness of modern conversation would have puzzled Jane Austen exceedingly, either in dialogue or narration.

Everybody knows that a single man who happens to be rich must be looking to get married. Or something.

Whatever you do or don’t know about his feelings or beliefs, no sooner does he set foot in a neighborhood than everyone decides he belongs to one of their daughters. Whatever!

“May one inquire,” Miss Austen demands, ripping her delicate handkerchief in long, clean lines, “to what this author is referring? Why has he elected to dispense with subject-object agreement, that well-belovèd and inflexible rule denoting that the subject of a sentence — in this case, everyone — should agree in number with its object. I would lay it down as a general principle, then, that everyone and his daughter would always be preferred by right-thinking readers to everyone and their daughters. And what, if I may be so bold as to ask, is the significance of whatever in this context?”

Search me, Aunt Jane. Millicent and I have been wondering about that, too.

Another popular species of vagueness in openings — also frequently born, I suspect, out of a desire to create suspense by omission, rather than via a detailed depiction of an inherently tense situation — is a little something we pros like to call the unnamed protagonist cliché. Tellingly, it is also known by another moniker: she ran through the forest…

Oh, you may laugh, but you wouldn’t believe how many manuscripts begin rather like this:

She fled through the forest, her long, red hair whipping against the bundle she hid ineffectually under her cloak in an attempt to shield it from the driving sleet. All she knew was that something was pursuing her, something terrible, something violent. Something that had forced her to leave behind everything she had ever known. Something that had changed her life forever.

Suddenly, a noise came from behind her…

By this point in the afternoon’s reading, poor Millicent’s wardrobe is in tatters. “Who is this woman, and why should I care that her life has changed forever when the narrative hasn’t yet told me anything about her previous life? From what is she fleeing? Am I supposed to think that the bundle is a baby, or am I only thinking that because it was a baby in 15 out of the last 37 similar openings? And why oh why not just tell me what’s chasing her?”

Again, perfectly legitimate questions — but not, it’s probably safe to assume, reactions the author would prefer this opening to elicit from a screener. Or indeed, any reader. Presumably, the writer is hoping that lay reader would read the opening above and murmur, “Heavens, will she get away? What is pursing her? Is the baby alive?” — and be spurred by those questions to keep reading.

Millicent, however, is unlikely to scan even one more line; had I mentioned how frequently she is treated to this kind of false suspense? “Is there any particular reason that I’m being kept in the dark about this broad’s name?” she murmurs, the frayed edges of her garments wafting gently in the air conditioned breeze. “Is it a state secret? Is it really my job to read on until the narrative deigns to tell me something that basic? Or maybe this writer has seen too many movies; in a book written in the third person, you don’t need to wait until someone addresses the protagonist to find out her name.”

Trust me, you’re better off identifying your characters right away.

A few valiant specificity-haters have had their hands in the air for paragraphs on end. “But Anne,” they point out, “in that last example, the writer was obviously just trying to start the story with a bang. You must admit that there’s no shortage of action in that opening, nor is there any serious question about what the book is about: the story that follows is obviously going to concern this woman, her bundle, and all of that red hair in their collective attempt to reach safety from the unnamed threat. Millicent can’t deny that it is exciting!”

Actually, she could — you would be astonished how efficacious sheer repetition can be in sapping the thrill from an exciting-but-common opening scene. And let’s face it, the long, red hair cliché and the everything she had ever known exaggeration would not exactly stun Millicent with their originality, either. Fleeing maidens habitually forget to tie back their long red or blonde hair while they are leaving everything behind, burning their bridges and changing their lives forever, whilst fleeing unnamed pursuers.

Those of us born brunette and/or bob our hair should be deeply grateful, evidently. An alien from the Planet Targ dropped into Millicent’s desk chair to form opinions of life on earth from manuscript submissions would undoubtedly conclude that we dark-haired females alone remain safe at home, rather than being chased by noises offstage into some conveniently nearby woods.

One more omnipresent variety of rend-inducing narrative vagueness, then I shall sign off for an evening of peaceful brunette serenity. See if anything in the following little gem strikes you as a potential Millicent-irritant.

As smoke curled up Blair’s nostrils, the irreality of the situation smote his consciousness head-on. It was like a movie: he simply observed his nearest and dearest go up in flames. As much as he longed to change the channel, he couldn’t.

Actually, there were two classic pet peeves cunningly concealed in that compact paragraph; did you catch them? First, the it was just like a movie trope has been so widely used in submissions since the 1920s that even the most recently hired Millicent is likely to regard it as a cliché at this late date. A more experienced Millicent might also regard it as the narrative shorthand it is: rather than showing readers precisely how and why Blair experienced the situation as divorced from his real life, the narrative not only chooses to tell us in just a few words what it was like — the writer is presuming that every reader will know precisely what she means by it was like a movie.

In essence, then, the writer is expecting the reader to guess in what specific ways Blair’s experience was filmic. And we all know how Millicent feels about that species of narrative expectation, right?

“Is it my job to provide the necessary description?” she fumes, taking a stapler to her hitherto undamaged skirt. “Isn’t it the writer’s responsibility to, well, write?”

Come on, admit it: she has a point. She would also be well within her rights to call out the narrative for its other professional reader-piquer, the mixed metaphor.

Oh, you didn’t catch it? Although we are told that Blair’s current situation is like a movie, he longs to change the channel as if he were watching television.

Someone didn’t reread this submission IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD, clearly.

What’s the cumulative moral here? Select your words with care — remember, all Millicent, or any reader, actually knows about the scene you are presenting is what you describe on the page. Yes, it’s undoubtedly quicker and more convenient to allow the reader to fill in the minutiae, but if you resort to vagueness or shorthand, how can you be sure that every reader will come up with the specifics you intend?

Or to put it another way: isn’t your creative vision worth conveying in detail?

And for heaven’s sake, tempestuous redheads and blondes-in-peril, grab a barrette or a baseball cap on your way out the door. Perhaps without all of that hair flying about in your eyes, you can finally get a good look at who or what is pursuing you.

Maybe then you could describe it to us. Keep up the good work!

Pet peeves on parade, part XV: speak to me, protagonist. Or blink twice to let me know that you’re alive.

After yesterday’s unusually lengthy post, even by my standards (which is saying something), I thought I’d limit myself this evening to a light, sparkling addendum to last time’s intensive session of nit-picking. It will be a struggle, I fear; well-constructed dialogue is a subject upon which I, like Millicent the agency screener, hold quite passionate views.

Why work ourselves into a lather over dialogue, you ask, instead of, say, punctuation placement? Well, while I, for one, have been known to wax eloquent about our friend, the humble comma, its placement is largely a technical issue: it’s rare that a great new writer will stake her claim to fame upon her bold and innovative use of commas.

Seriously, would you want your name to be passed down to posterity as King of the Commas? Wowing the literary world with an unusually good ear for dialogue, on the other hand, is a goal to which many a fledgling writer of fiction and/or memoir aspires. It’s certainly a worthwhile one: writing dialogue well requires not merely a strong sense of what people actually say and the rhythms in which they say it, but also the creativity to pepper the dialogue with enough originality that it won’t seem ho-hum.

Yet for some reason that perpetually escapes me, even writers who pride themselves on their fresh, original notions and execution frequently choose to bore poor Millicent to extinction with uninteresting dialogue. “But people really talk like that,” they hedge. “It’s not my fault if most people are not scintillating conversationalists.”

Well, that’s not entirely true, realism-huggers. While no one can hold you accountable if the couple at the next table elects to immerse themselves in dull chit-chat (“How about this rain?” “We sure do need it.” “I’ll say.”), it’s not fair to expect readers to suffer through dialogue that has no legitimate claim to attention other than its fidelity to real-life talk.

Or, to put it a bit more bluntly: not everybody in the world is under an obligation to produce entertaining sentences. Writers are.

Messes with your head a little to think of dialogue in those terms, doesn’t it? If so, you’re not alone: most dialogue in submissions is clearly aimed at realism, rather than entertainment. Only a relatively small percentage of submissions demonstrate a commitment to developing character through speech by having characters say interesting and unexpected things in their own distinct voices.

Which is to say: you’d be amazed — at least, I hope you would — by how frequently otherwise creative narratives are bogged down by mundane, unrevealing, or cliché-ridden dialogue.

How common is it? Let me put it this way: if an alien from the planet Targ were to drop from the sky into Millicent’s cubicle tomorrow, determined to learn about how human beings communicate by leafing through a few hundred submissions, it would stroll out of her office sounding just like that couple at the next table. If you ran into it at a cocktail party, you’d be eavesdropping on nearby conversations within a couple of minutes.

What a pity — it might be fascinating to hear about living conditions on Targ these days. But even someone with something interesting to say can seem boring if he doesn’t express himself in interesting terms.

Or if, as we saw last time, if he chooses not to vouchsafe an opinion of his own. All too often, supporting characters — or even more common, passive protagonists whose idea of solving a mystery is to ask one or two questions, then sit back and wait while someone who has defined her very existence by the secret she has kept just blurts out the long-hidden truth — are only nominal participants in dialogue scenes. By not engaging the primary speaker with an alternate point of view, the character becomes simply a monologue-encourager.

Trevor glanced around the musty basement, wondering how anyone could possibly survive for an hour there, much less thirty-eight years. “So you have been in hiding all of this time?”

“You call it hiding.” Veronica’s teeth wobbled visibly with every word. “I call it saving my skin.”

“Really?”

“Oh, yes. When I first sought out the basement, it was merely as temporary shelter from the horrors of the street. I had no idea that I would be spending the better part of my life here.”

“Wow.”

She flipped her lank gray bangs out of her eyes, and just for a second, she resembled the seventeen-year-old she had been when she last stood in natural light. “Well might you say wow. Do you know how long it took me to figure out how to transform the disused washer/dryer unit into a convection oven? Eight long years. Before that, I had to eat the rats that sustain me raw.”

“Eww.”

“Oh, you get used to it. It’s the right seasoning that’s the trick. The same holds true for cockroach goulash, incidentally.”

“Weren’t you going to tell me about the horrible incident that drove you underground?”

She clutched her mouse fur bed jacket around her fiercely. “I swore I would never tell. Never!”

Trevor’s heart sunk within him. He had come so far in the last forty-eight hours; he couldn’t turn back without one last push. “Pretty please? With sugar on top?”

Veronica looked at him, and her last reservation melted. “It was a dark and stormy night in 1973. I was just a girl then, getting ready for the prom. My dress was hanging over my David Cassidy poster, waiting for me to pick out which of my six sets of platform shoes I would wear. Suddenly, I had the eerie feeling I was being watched.”

“Uh-huh,” he prompted breathlessly.

Trevor’s not adding very much to this interaction, is he? By choosing to be a mostly passive listener, rather than a participant in the conversation, he’s done more than abdicate his role as the reader’s guide through this part of the plot; he’s basically pulled up a chair and plopped himself down right next to the reader, drinking in Veronica’s story as though he were just another audience member.

But at least he is responding in a manner that reveals his feelings about what she is saying. All too often, passive protagonists in interview don’t even do that.

Trevor glanced around the musty basement. “So you have been hiding here all this time?”

“You call it hiding.” Veronica’s teeth wobbled visibly with every word. “I call it saving my skin.”

“Saving your skin?

“Oh, yes. When I first sought out the basement, it was merely as temporary shelter from the horrors of the street. I had no idea that I would be spending the better part of my life here.”

“The better part of your life? Why, how long has it been?”

“That depends. What year is it?” She laughed loudly before he could answer. “Just kidding. It’s been thirty-eight years.”

“Thirty-eight years!”

“The trick was keeping myself busy. Do you know how long it took me to figure out how to transform the disused washer/dryer unit into a convection oven? Eight long years. Before that, I had to eat the rats that sustain me raw.”

“Rats? Raw?”

“Oh, you get used to it. It’s the right seasoning that’s the trick.”

Pardon my asking, but couldn’t Trevor’s part in this scene be very adequately played by a parrot? Or a very high, cavernous ceiling that could echo Veronica’s words back to her?

Certainly, he’s providing neither conflict nor any additional information to the scene. Heck, he’s barely contributing any new words.

So what is he doing in the scene at all? Perhaps he is seeking clues to an ongoing mystery he is trying to solve, and is merely going about it poorly. Or maybe he is actually an immensely clever sleuth, trying to lull poor Veronica into a false sense of security by giving incisive questions about what he wants to know a wide berth. Or he could have just suffered a brain injury that deprived him of the ability to understand what someone is saying until he’s heard every part of it twice.

Or maybe he’s just rather stupid. At least, he appears so on the page.

That made some of you real dialogue-echoers sit bolt upright in your desk chairs, didn’t it? “But Anne,” you point out with some vim, “I know that you’ve just been saying that the fact that people actually talk that way shouldn’t be the only justification for a line of text, but people actually do talk this way. Repeating what’s just been said is a standard means of asking for clarification. Why, I can barely watch five minutes of any TV drama without hearing a character repeat a phrase that’s just been said to her.”

I believe it — and that alone might be a good reason not to embrace this conversational tactic in your dialogue. Since the rise of reality television (does anyone but me remember that producers originally embraced the format because the writers’ guild was on strike?), we’ve all become accustomed to highly repetitious speech pouring out of characters’ mouths, often with a blithe disregard for the rules of grammar. Heck, it’s become quite normal for even speakers who should know better to misuse words.

And I’m not talking about tiny gaffes, like saying further when the speaker really meant farther, either. (In response to that silent plea for clarification: the first refers to concepts, the second to distance.) I’m talking about the increasingly common practice of substituting the intended word or phrase with one that sounds similar to it — a doggy-dog world instead of a dog-eat-dog world, for instance, or mano y mano instead of mano a mano — as if getting it right simply didn’t matter. Or simply using a term so loosely that its original meaning dissipates, as when someone dubs an outcome ironic when it’s merely symbolically apt (in itself ironic, since irony is when the intended and literal meaning are at odds). Or says unironically, “We will be landing momentarily,” when he means “We will be landing in a few minutes,” not “We will be landing for a few moments, then taking off again.”

Yes, yes, I know: if I were correcting these commonly-misused phrases in the middle of an actual conversation, I would come across as a joy-killing curmudgeon. (Blame my upbringing: children in the Mini household were expected to be both seen and heard, but never to end a spoken sentence with a preposition.) And to tell you the truth, I wouldn’t have a problem with a writer’s reproducing these gaffes on the manuscript page — provided that their use was limited to dialogue and not every character made similar mistakes.

Which character would I select to talk this way? The one the reader is supposed to regard as a little slow on the uptake, of course.

Oh, you laugh, but back when writers composed and refined every word that fell out of characters’ mouths on TV and in movies, placing improper grammar and malapropisms into dim-witted characters’ mouths was a standard comic device. It was also a time-honored means of establishing a character’s level of education, social class, or susceptibility to prejudice: much of the recent furor over whether it was legitimate to clean up the language in HUCKLEBERRY FINN so that it could be assigned in more high school classrooms turned on Mark Twain’s devastatingly frequent use of a certain pejorative term to illustrate his protagonist’s change of perspective on issues of race throughout the book.

Even now, one of the quickest means of making a character come across as less intelligent on the page is to have him misuse words or repeat what’s just been said to him. The latter can be particularly effective, enabling the dialogue to convey that he doesn’t understand what’s going on without having to resort to the blunt expedient of having another character call him stupid.

Don’t believe that a few misused or repeated words can have that great an impact on character development? Well, they might not to a reader who habitually makes similar mistakes, but to a literate reader — and Millicent, her boss the agent, and the editor to whom the agent pitches pride themselves on their literacy — conversational faux pas will leap off the page. They’re a way to show, not tell, that a character has trouble expressing himself.

I sense that some of you are still not convinced. Okay, here’s an anecdote about how the repetition of a single misused word made a university professor seem substantially less intelligent.

When I was in graduate school, I took several small seminars with Professor Baker, an elegant, well-spoken woman who delighted in quoting Ancient Greek playwrights in even the most informal conversations. No mere cold intellectual, she was deeply interested in her students’ personal development. “Don’t cut off your options,” she would tell us frequently. “Go out and explore. I want to see you living a fulsome life!”

The first time she said this, I was convinced that I must have misheard. Fulsome, after all, means grossly overabundant or insincere; a fulsome complimenter would heap on praise after exaggerated praise until it was impossible to believe anything he said at all. It can also mean disgusting or offensive to the sensibilities. Somehow, I doubted that my professor was wishing me a life that resembled rotting meat.

Yet at the end of practically every seminar session, she would repeat her admonition: she seemed pretty darned insistent that my fellow students and I should be actively pursuing fulsome lives.

What she meant, of course, was that we should lead full lives; she must have just thought the -some bit added emphasis. But when I suggested that she truncate the word, she snapped at me like an irate turtle.

“Are you questioning my erudition?” she demanded. “I would hardly use a word if I were unaware of its definition.”

In that moment, to paraphrase Emily Dickinson, she dropped so low in my regard/I heard her hit the ground. Not because she had consistently been using her favorite word incorrectly, but because she was too inflexible even to consider the possibility that she might have been wrong. And because had she been right, all she would have had to do was stretch that elegant, beringed hand across her well-appointed desk, open a dictionary, and show me the definition.

If she had wielded her pet piece of advice with more discretion, she would probably have gotten away with it, right? I might have chuckled over my notebook, but her momentary gaffe would soon have been obliterated in my memory by other, more lucid statements. But by repeating it so often, essentially turning it into her catchphrase, she made sure that single mistake would become entrenched in my mind as the key to her entire character.

Would this tactic work on the page? You bet, although I would advise giving a fictional character a wider array of conversational missteps. Repeating the same one over and over might well backfire: since professional readers are trained to spot textual repetition — how else would they be able to point out to you that you used the same metaphor twice in 157 pages? — the second iteration might strike Millicent as unintentional. (In answer to what half of you just shouted mentally: oh, you’d be surprised how often aspiring writers will plagiarize themselves within a manuscript. They don’t mean to be repetitious; they simply forget that they have used an image or even a sentence earlier in the book.)

Speaking of low-level carelessness, there’s another reason it might behoove Trevor’s creator to ramp up his contribution to the scene. You really don’t want Millicent to start wondering if the only reason he’s in the scene is to provide the narrative an excuse to show the reader what it’s like down there.

You’re chuckling again, aren’t you? Think about it: in a close third-person (or first-person) narrative, Trevor would have to be there to justify the reader’s venturing into that basement. Including a scene in which he did not appear would necessarily entail jumping into someone else’s perspective — or slipping out of the dominant voice of the book into an omniscient point of view.

“Whoa!” Millicent cries. “This manuscript is breaking its own rules!”

You can hardly blame her for being hyper-sensitive on this point: since tight third person and first person are the two most popular point of view choices, she sees an awful lot of protagonists wander into an awful lot of situations where they have no business being, simply because writers want to include specific scenes in their books. She’s also privy to a great many instances of a narrative’s abandoning the strictures the writer had been following for the rest of the story — sticking to a single perspective, allowing the narrative to be colored by the chosen character’s prejudices, and so forth — because the writer apparently could not figure out a way to show a desired activity from the dominant perspective.

In answer to that collective gasp: yes, she will notice, whether the point of view slips for an entire scene or a single paragraph. She’s going to be on the lookout for such voice inconsistency problems, in fact. It’s all a part of her fulsome rich and meaningful life.

Make sure your protagonists pursue existences almost as full as hers: don’t allow them to become bystanders in their own lives, even for a page. Show them engaging in the world around them; let their presences add substantially to any scene they grace. Those contributions do not need to be limited to the dialogue, either: in a close third-person or first-person narrative, even a protagonist forced to remain stock-still and silent can interrogate her boss in her thoughts, signal another prisoner with a poke of her toe, struggle to breathe calmly while that cursed monologue-happy teacher bellows in front of the chalkboard…

The possibilities are, as they say, limitless. In a universe both frequently fulsome and perpetually full, why restrict the scope of your creativity by not taking complete advantage of your protagonist’s ability to react?

Worth pondering, anyway. Keep up the good work!

Pet peeves on parade, part XIII: repetitive activities and other things that wouldn’t be interesting to most readers if you set them on fire

Before I launch into today’s festivities, campers, I would like to call your attention to some festivities on this coming Saturday, April 9th. At 6 p.m., Seattle’s Wing Luke Museum of the Asian Pacific Experience will be holding its annual fundraising dinner and auction. A door prize for all attendees: a pre-release copy of Harold Taw’s The Adventures of the Karaoke King.

What a creative promotion idea, eh?

If Harold Taw’s name sounds familiar to those of you who have been hanging out here at Author! Author! for a while, it should: Harold is the long-time member of our little community whose first novel got plucked out of the plethora of entries in the Amazon Breakthrough Novel contest and brought to publication through AmazonEncore. I plan to be raising a toast to his book’s astonishing journey to publication at his book release party at Elliott Bay Books on April 27th, by the way, while folks are marking calendars; I’d love to lead the wave in an Author! Author! cheering section.

As eagle-eyed readers may have been able to discern through the lines of that last paragraph, I love announcing my readers’ triumphs along the long and bumpy road to publication. Keep that good news rolling in, everybody!

While we’re on the subject of subtleties of the tossing-a-brick-through-the-nearest-window variety — how’s that for a light-handed segue? — I’d like to devote today’s post to a species of manuscript problem that seems to be practically invisible to most writers who produce it. The fact that it is so hard for a self-editor to catch, however, in no way impairs its ability to irritate professional readers like our old pals, Millicent the agency screener, Maury the editorial assistant, and Mehitabel the veteran contest judge, to madness.

“Not again!” Millicent exclaims, her fingers itching to reach for the form-letter rejection pile. “This submission has gotten caught in a conceptual repetition loop!”

Surprising that a subtle problem could engender such a strong reaction? Don’t be: professional readers are trained to focus on the little stuff. Millicent in particular is trained to be on the look-out for typos, formatting problems, missing words, and all of the other signs that a manuscript is at least one revision away from being ready to market to editors.

Or, to express it in her terms, a submission that causes her itchy fingers to make actual contact with that stack of rejection letters. “Next!” she cries.

Yes, I know: I harp quite a lot on the importance of a manuscript’s being completely clean — at least in the opening pages — in order to skirt the specter of knee-jerk rejection, but I’m continually meeting very talented aspiring writers who complain about how often their work is getting rejected…but haven’t taken the time to remove, or even notice, the seven typos within the first two pages of their texts. While it’s certainly understandable that someone who wants to write for a living would be shocked or even horrified upon learning just how high professional standards actually are, this is no time to be in denial: assuming that one’s first draft is going to meet those standards without further revision or even proofreading has led thousands upon thousands down the primrose path to rejection.

Has that sunk in this time, or shall I play another verse on my harp? My fingers are all warmed up now.

To be fair, even writers who have been working on their craft for years are often stunned to realize that the pros pride themselves on noticing everything. And with good reason: contrary to popular opinion, to a pro, the proper use of language is an integral part of an author’s literary style and voice, not a purely cosmetic addition to it.

As a freelance editor, I find it fascinating how often aspiring writers equate Millicent’s focus on proper language use — which is part of her job, incidentally — with a dislike of good writing. In reality, quite the opposite is usually true: the people who choose to work in agencies and publishing houses almost invariably love beautiful writing and strong stories.

Paradoxically, this affection for the well-constructed sentence often renders reading a promising submission or contest entry more irritating than one where the writing just isn’t very good. “Oh, dear,” Mehitabel says, shaking her head regretfully over a page full of potential, “I hate it when this happens. If only this writer had taken the time to notice that he’s made the same point four times over the course of this scene, it would have been so much more compelling. Next!”

Seem like a petty reason to knock an otherwise well-written entry out of finalist consideration? Actually, it’s a rather common one. As I hope has become clear over the course of this series on notorious professional readers’ pet peeves, the manuscript problems that cause Millicent, Maury, and Mehitabel to rend their garments are not always major gaffes like an authorial indifference to punctuation or a storyline that provokes the ejaculation, “Huh?” every other line.

They see those kinds of submissions, of course, but astonishingly often, the irritant is simply a page of text that makes the same point too many times. Why, here’s an example of that species of scene coming along right now.

See if you can catch the subtle narrative problem that might elicit a cry of, “Next!” Actually, you might want to hunt for three of them.

“What is it you are trying to say, Carol?” With infinite care, Alphonse flicked the blindingly white tablecloth over the polished oak surface. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He settled the cloth over the table. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities, Alphonse.”

“Nonsense.” He smoothed the tablecloth over the flat surface, checking for any lingering wrinkles his iron had missed. “It’s a pleasure to work here.”

“But Alphonse, we can’t afford to keep you.”

He lowered a fork into its proper place. “I don’t cost much, Carol. I live mostly on my tips.”

She pounded the table, making the fork dance. “Alphonse, you live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” Alphonse reached to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” Carol shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the fork and spoon he had just placed. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

Alphonse laid down a soup spoon. “You always do, Carol. You always do.”

Come on, admit it — by halfway through this excerpt, you wanted to shout, “Criminy, Alphonse, enough with the table-setting! Move on to something else.”

So would Millicent, and she has the power to enforce that preference. Being editorially trained, she’s more likely to express it as, “Um, couldn’t most of the inter-dialogue narrative have been replaced very adequately by Alphonse set the table with care?” but you get the picture, right? To an intelligent reader who is paying attention, attenuating the description of a process by mentioning each and every step can make a scene seem much longer than it is.

In a case like this, where the activity is not inherently interesting — he’s setting a table, for heaven’s sake, not cross-checking the details for the first manned flight to Venus — it can be downright irritating. That page space could have been used for far more fascinating ends.

We’ve discussed a version of this phenomenon before, right? The Walking Across the Room (WATR) problem dogs many a manuscript submission: instead of just stating that a character does something relevant, like answer a ringing doorbell, the narrative will describe him hearing the ring, rising from his seat, taking step after step across the room, opening the door into the hallway, passing down the hallway, approaching the front door, grasping the knob, turning it, and pulling.

All of which could quite nicely be summed up as The doorbell rang. Yves answered it., right?

The meticulous-minded have had their hands politely raised for the last few paragraphs. Yes? “But Anne,” process-huggers protest, “I don’t agree that Alphonse has a WATR problem. The passage above merely shows his attention to minute detail, showing (not telling) that he’s a perfectionist. That’s legitimate character development, isn’t it?”

Well, in a way, detail-hounds. Yes, it demonstrates character; it’s just not the most interesting way to do it. Nor are these details in and of themselves likely to hold the reader’s attention.

Hey, I wasn’t kidding about these problems being difficult to catch in one’s own work. To Alphonse’s creator, all of the mundane specifics above may well be gripping.

Remember, though, just because a character might conceivably perform an action isn’t necessarily enough reason to include it a manuscript. Since this is a process that it’s safe to assume every reader will have observed before, however, the page space would be better spent demonstrating his attention to detail in an activity with which most readers will be less familiar — constructing a multi-layered wedding cake, for instance.

Or at least one that tells the reader a little more about what kind of restaurant it is. Take a gander at how much more revealing this scene is if our Alphonse busies himself prepping the restaurant’s signature dessert.

“What is it you are trying to say, Carol?” With infinite care, Alphonse sharpened his personal paring knife — off-limits to the rest of the wait staff — on the whetstone he kept in his left pants pocket. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He wiped the gleaming knife on his handkerchief. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities, Alphonse.”

“Nonsense.” Holding his breath, he began cutting the zest off an orange in one long strip. “It’s a pleasure to work here.”

She held her breath, too; if his blade slipped, the curly peel would be too short for the flames to dance down its liquored length to the customer’s coffee cup. “But Alphonse, we can’t afford to keep you.”

A perfect peel tumbled from his knife into the waiting silver bowl. “I don’t cost much, Carol. I live mostly on my tips.”

“Alphonse, you live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” Alphonse studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” Carol shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the brandy awaiting his match. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

With a pointing finger, Alphonse laboriously counted all of the ingredients on his café brulôt cart. “You always do, Carol. You always do.”

Nice way to combine character development for him and information about the restaurant, isn’t it? By killing the proverbial two birds with one stone, the reader is not only treated to a more interesting process to observe, but is faced with far less repetitive and predictable activity throughout the scene.

Speaking of repetitive, did you catch the two subtle narrative problems remaining in the text? Hint: one is on the scene level, and the other is on the sentence level.

If you grasped the nearest tablecloth, waved it over your head, and exclaimed, “The constant name repetition is visually most annoying,” help yourself to an extra orange off Alphonse’s cart. The characters’ names are mentioned far too often than is necessary for clarity. Indeed, since the only two characters in the scene are of different sexes, the narrative sections could dispense with all but the first of those eye-distracting capital letters.

But the narrative repetitions of their names actually account for relatively few if the iterations. The real culprit here is the extremely pervasive phenomenon of having the characters address one another by name far more often than people actually do in real life.

As a group, aspiring writers seem to adore this. Editorial opinion on why varies: some of us maintain that writers tend to compose lines of dialogue in short bursts, rather than entire scenes, so they don’t notice how often their characters are barking their names at one another; others assert that writers just like the names they have picked for their characters to want to see them again and again. (It’s not all that uncommon for first-time novelists to believe that simply changing a name will completely destroy the reader’s conception of the character, as if the name choice were so significant that no other character development was needed or wanted.) The more practical-minded believe that writers sometimes overuse name repetition in dialogue deliberately, to make it easier for readers to follow who is speaking when; the more cynical think that writers repeat the names to remind themselves who is speaking when.

If it’s the last, it’s not a bad strategy — at the composition stage. Alternating lines of dialogue where the count has gotten off is another of Millicent’s pet peeves, after all. It’s surprisingly common in submissions, and it’s often an instant-rejection trigger. Proofreading each and every line of dialogue that does not contain a tag line (the he said bit that identifies who is speaking), then, can make the difference between Millicent’s remaining involved in a dialogue scene and “Next!”

At the polishing stage, though, the training wheels should come off: the extraneous name markers need to go. Fortunately, if the scene is clearly written, with each character’s dialogue being distinct from the other’s, these cuts can be made with virtually no cost to the story.

“What is it you are trying to say, Carol?” With infinite care, Alphonse sharpened his personal paring knife — off-limits to the rest of the wait staff — on the whetstone he kept in his left pants pocket. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He wiped the gleaming knife on his handkerchief. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities”

“Nonsense.” Holding his breath, he began cutting the zest off an orange in one long strip. “It’s a pleasure to work here.”

She held her breath, too; if his blade slipped, the curly peel would be too short for the flames to dance down its liquored length to the customer’s coffee cup. “But we can’t afford to keep you.”

A perfect peel tumbled from his knife into the waiting silver bowl. “I don’t cost much. I live mostly on my tips.”

“You live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” he studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” she shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the brandy awaiting his match. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

With a pointing finger, he laboriously counted all of the ingredients on his café brulét cart. “You always do, Carol. You always do.”

Did it surprise all of you self-editors that I kept Carol’s shout of “Ambrose!” That’s the one that has the strongest emotional resonance: essentially, she is trying to call him back to reality. Now that all of her other repetitions of his name are gone, it stands out as it should.

There’s one final pet peeve that remains uncorrected — and no, it’s not the dubiously-constructed clause about the pointing finger. I’ll give you a hint: there’s an improperly-formatted tag line haunting this scene.

Or, as Millicent would put it: “Studded is not a speaking verb! Neither is reach! Next!”

Not positive what she’s talking about? Okay, here are the offending sentence from each version, ripped out of context.

“Well, then,” Alphonse reached to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

“Well, then,” he studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

See Millie’s point now? No? Okay, would it help to know that what the author originally meant was this?

“Well, then,” Alphonse said, reaching to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

The problem lies in the first two versions of this sentence using reach or stud, respectively, as substitutes for said. Since only verbs that refer to speech may legitimately be used in a tag line, the end result is improper — and a misuse of that first comma.

How so? “Well, then,” he studded the peel with whole cloves, is a run-on sentence. In a tag line, the comma indicates that a speaking verb is to follow. So while this is correct:

“I’m coming, Harry,” Celeste said.

This is not:

“I’m coming, Harry.” Celeste said.

Nor is:

“I’m coming, Harry,” Celeste put on her hat.

Those last two look very wrong, don’t they? Yet you would not believe how often these errors appear in otherwise well-written dialogue. My theory is that it’s a Frankenstein manuscript phenomenon: aspiring writers may write tag lines correctly the first time around, but come revision time, they change the verb without noticing that they have not altered the punctuation to match.

Millicent, Maury, and Mehitabel can’t believe the frequency with which tag line problems crop up, either, but their explanation tends to be less charitable. “If these people want to write dialogue professionally,” they ask one another over flaming cups of coffee, “why wouldn’t they take the time to learn how tag lines work? Or to proofread?”

You have to admit, those are pretty darned good questions. If you’ll just hang around while I set the table for 18 people, perhaps we could discuss them at length.

Just not, please, on the manuscript page; both life and Millicent’s overloaded reading schedule are too short to read repetitive descriptions of uninteresting activities. Keep up the good work!

Crowing for good reason: Author! Author! Award for Expressive Excellence winner Bruce Alford’s ROOSTER

Today, I am delighted to bring you the winning entry in the recent Author! Author! Rings True literary competition, Bruce Alford of Mobile, Alabama. In addition to carrying off top honors in Category I: literary fiction, Bruce’s breathtakingly delicate first page and well-constructed 1-page synopsis for ROOSTER also garnered the coveted Author! Author! Award for Expressive Excellence. Well done, Bruce!

As has been the case for all of the winners in this contest, I sat down to discuss this exciting opening and premise with the ever-fabulous Heidi Durrow, author of the intriguing recent literary fiction debut, The Girl Who Fell from the Sky. (The contest was timed to celebrate the paperback release of her novel.) She writes literary fiction, and I edit it, so our appetites were very much whetted.

Especially for this entry. When the judges first clapped eyes upon it, the opening seemed almost eerily apt for this contest: the primary protagonist of Heidi’s marvelous literary fiction debut, The Girl Who Fell from the Sky, is half Danish, half African-American. It just goes to show you, campers — no matter how carefully a writer prepares a submission or contest entry, there’s no way that he can control what happens to be on Millicent the agency screener or Mehitabel the contest judge’s mind at the moment she happens to start reading it.

What’s that I hear you muttering, campers? You feel that’s a trifle unjust, that the imperatives of literature require that all manuscript assessments be made from a completely clear mind, as if Millicent and Mehitabel had not read 27 first pages earlier in that sitting? Or perhaps as if they had not previously screened any literary fiction at all, and had not become jaded toward common mistakes?

Fine — you try it. Here are Bruce’s materials as they might appear in a submission packet: page 1, synopsis, author bio. (As always, if you are having trouble seeing the details, try holding down the COMMAND key and hitting + to enlarge the image.) To make this an even fairer test, I shall not comment on the technical aspects at all until after Heidi and I discuss the content.

I’m going to stop you right here: quick, what’s your assessment of this book?

Approaching a new writer’s work with completely fresh eyes is more difficult than it might seem at first blush, isn’t it? Everything you have ever read, from your all-time favorite novel to your high school English literature textbook, contributes to your sense of what is and is not good writing.

So let me simplify the central issue for you: based on that first page alone, would you turn to page 2?

I would certainly read further. On the strength of that, let’s take a peek at the other materials in this packet.

Bruce Alford, a personal trainer, aerobics instructor and a former journalist, has published creative nonfiction and poetry in various literary journals. Alford’s “How to Write a Real Poem” was selected for Special Merit in the 2010 Muriel Craft Bailey Poetry Competition. His book of poems, Terminal Switching (Elk River Review Press), was published in 2007.

For a decade, he worked on drafts of Rooster. The book draws on tragedy in his family. His wife’s brother was missing for a week. Then migrant workers stumbled on his brother-in-law’s body near a tomato field in Louisiana. Over the years, as Alford wrote and re-wrote, he noticed that his relative’s short life and death said much about what being an American meant.

As an assistant professor of creative writing at the University of South Alabama, he teaches a full schedule of classes, including British and American Literature, Poetry Writing and Creative Non-Fiction. He is a reviewer for First Draft, a publication of the Alabama Writers’ Forum.

Does ROOSTER’s plot sound vaguely familiar? It should: it’s Hamlet, cleverly updated and set in an unexpected setting. Many highly successful novels have taken time-honored stories we all know and transformed them. Alice Walker’s THE COLOR PURPLE, for instance, is a retelling of the Ugly Duckling; there have been so many versions of Cinderella that I cannot even begin to enumerate them.

While some writers might have chosen to conceal the eternal nature of the tale, Bruce has done something very interesting here: from the first line of the book, he evokes a fairy tale resonance. There was a girl in Denmark might be the opening of half of the stories in a Hans Christian Andersen storybook. That’s a definite marketing risk — chant it with me now, campers: most professional readers have been trained to regard the passive voice as stylistically weak writing, regardless of how and why it is used — but here, it may well pay off.

Did it? Heidi and I discussed that very question.

It’s all about the writing: Author! Author! Rings True literary fiction winners Daniel Light and Austin Gary


Daniel, author of Wider Than the Sea


Austin, author of Genius

I’m most excited about today’s group of winners in theAuthor! Author! Rings True literary competition — and not just because they write in a category near to my heart, literary fiction. Daniel Light and Austin Gary’s entries are a far cry from the literary fiction stereotype of being about nothing but the writing: their pages and synopses present strong storylines, interesting premises, and interesting writing, told in unique authorial voices. Well done, both!

Adding to the excitement: I shall be discussing these intriguing entries with the ever-fabulous Heidi Durrow, author of the blockbuster literary fiction debut, The Girl Who Fell from the Sky. (Now available in paperback!) Since Heidi writes literary fiction and I edit it, we both waxed poetic in discussing it.

I’m also rather tickled by how many of this contest’s array of winners (and entrants in general) come from far-flung corners of the earth. Daniel wins the long-distance entrant prize — he lives in Jerusalem — while Austin inhabits lovely British Columbia. John Turley and Fiona Maddock, of Rings True freestyle category fame hail from Colorado and the United Kingdom, respectively; memoir winners Kathryn Cureton and Margie Borchers are from Missouri and Washington state. For a blog that started out five and a half years ago as the voice of a regional writers’ association, the diversity of entries is most gratifying.

This contest’s winners are really interesting people, too; I’m so glad that I asked for author bios this time around. Fair warning: I’m going to make this a regular feature for Author! Author! contests, so now would be a great time to start thinking about your own bio, as well as what you would use as an author photo if the agent of your dreams asked for either or both tomorrow. (For tips on pulling your own together, take a peek at the aptly-named HOW TO WRITE AN AUTHOR BIO category on the archive list at right.)

A moral that I hope everybody will take from these winners’ posts: an author bio need not be crammed to the gills with publication credentials in order to make the writer sound interesting. Austin and Daniel’s bios are very different, but they both would make Millicent the agency screener want to chat with these writers over a steaming-hot latte. First, check out Austin’s more traditional bio:

Austin Gary is a BMI award-winning songwriter (as Gary Heyde), with recordings by artists such as Tammy Wynette, John Berry & Jeff Carson. He’s been an editor of a weekly newspaper; an actor/director; copywriter; director of radio and TV broadcast; a jingle writer; owner of a music production company; and a teacher of English, speech, drama and film. Austin’s been seriously writing since 2007. In 2008, he was a fiction finalist in the PNWA lit contest (“Ask Me No Secrets:); 2009 semi-finalist in the Faulkner-Wisdom fiction competition (“Miss Madeira”); and 2010 a finalist in the Faulkner-Wisdom novel-in-progress (“Genius”). He recently moved from Des Moines, WA to Port Moody, B.C., where he’s writing full-time.

Makes him sound pretty formidable, does it not? Now take a gander at Daniel’s less standard, but equally interesting bio:

Daniel Light is an ordained rabbi who has taught Talmud and Bible part-time in several schools in Israel and has run a listserv dedicated to essays that harmonize between Judaism and popular culture. He holds a Bachelor of Commerce from McGill University and a Bachelor of Law from Hebrew University and, following a year-long internship in corporate law, is currently living in Jerusalem and studying for the Israeli Bar exam. WIDER THAN THE SEA is his first novel and the fruit of his experiences in, and knowledge of, law, medicine, religion, psychology, morality, and life.

Not as many publishing credentials, admittedly — but if you were inviting luminaries to a literary luncheon, you would want both Austin and Daniel on your guest list, wouldn’t you? So would Millicent. Except as someone who habitually thinks in terms of book marketing, she would also make a mental note that either of these writers would probably give a great interview and be genuinely interesting public speakers.

If you think those are not a selling points for a writer, I can only assume that you do not attend many book readings. Unfortunately, new authors (and even established ones) who spend entire hours-long promotional events with their noses three inches from their own books, assiduously avoiding eye contact, are the norm, not the exception. It’s not even all that uncommon to see authors who evidently experience difficulty reading out loud.

Yet another reason to get into the habit of reading your manuscripts IN THEIR ENTIRETY, IN HARD COPY, and OUT LOUD, should you need another. If your critique group doesn’t set aside time for members to read to one another, you have my permission to tell yours that I said it was excellent training for future author readings. (And while we’re on the subject, would any of you regular readers be interested in my running a series of public reading dos and don’ts?)

As interesting as the bios are, however, for literary fiction, what matters most is on the manuscript page: more than in any other book category, literary fiction readers pay attention to sentence structure, vocabulary, and imagery. As folks in the industry like to say, it all depends on the writing.

Specifically, how literary the writing is. Lest we forget, in publishing terms, there is no such thing as universally good writing: what constitutes good writing on the literary fiction page is quite different from stylistic excellence in a mystery and vice-versa. And while agents have been known to say, “It’s a {fill in book category here}, but in a literary voice,” they don’t mean that the author of the book in question has jettisoned the conventions and expected vocabulary of the category; they merely mean that the narrative contains unusually pretty writing.

Do I spot some raised hands out there? “But Anne,” the many, many aspiring writers who have been assuming that their work was literary fiction protest, “isn’t pretty writing half the definition of literary fiction? And isn’t the other half a story driven by character, rather than by the needs of the plot?”

Well, yes and no on both counts, literary assumers. Yes, nice writing and a character-driven story are standard elements of literary fiction. No, that doesn’t mean a book without a plot that features impeccably-crafted sentences. Nor — and this may come as more of a surprise to some of you — does it mean that any well-written character development is literary fiction.

Don’t feel bad if you thought this — if that giant gulping sound we just heard out there in the ether is any indication, you were certainly not alone in conflating good writing with literary writing. Aspiring writers presume that literary fiction is merely a euphemism for good writing; if their writing is stylistically strong, they reason, and if it is fiction, it must therefore be literary fiction.

Which renders it rather confusing when the pros state categorically that there is good writing in every book category, doesn’t it?

But book categories are not subjective judgments about authorial voice and style; they are marketing containers for books that share certain expectations about plot, character development, subject matter, and audience. Literary fiction is its own distinct book category — consisting of narratives more prone to dwell on character, true, but also written in a vocabulary and sentence style aimed to please a college-educated readership. In the U.S. market, that readership is between 90-95% female, depending upon whom you ask and whether the respondent considers John Irving’s work literary or mainstream fiction.

Oh, you may laugh, but for many years, debate raged over how to categorize THE WORLD ACCORDING TO GARP. (If you don’t believe me, check out The New York Times’ extremely uncomfortable original review.) Until fairly recently, one of the best ways to find out how a literarily-aware person felt about the desirability of high literature’s being accessible to a mainstream readership was to bring up the inimitable Mssr. Irving and ask whether the aforementioned reader regarded him as a writer of literary fiction or not.

Bearing this ongoing debate in mind, let’s step gingerly into Millicent’s moccasins and peruse Daniel’s page 1. (As always, if you are having trouble making out the details, try holding down the COMMAND key and pressing + to enlarge the image.) Is it literary fiction, or is it just good writing?

Have you made up your mind? Good. Now take a gander at Daniel’s synopsis, and see if your opinion about the book category changes.

Have you come to a conclusion? Or, after our discussion last time about the differences between fiction and nonfiction synopses, did the analytical statement the novel reaches a climax distract you too much to be able to form a firm opinion? If it’s the latter, you’re thinking like Millicent: in a synopsis for a novel, regardless of book category, she expects to see the story told directly, not to see the plot talked about indirectly, in academic terms.

That’s another common misconception amongst aspiring writers: the notion that using technical terms like climax, protagonist, antagonist, central conflict, etc. will make their queries and synopses sound professional. In practice, however, while people in the publishing industry do occasionally use these terms, an agent pitching fiction to an editor or an editor pitching it to an editorial committee would rarely describe it this way.

Instead, they would tell the story — as should the writer. As beautifully as possible. After all, part of what’s being sold here is the writing style, and (feel free to chant it with me now, long-term readers) every sentence a writer submits to an agency, publishing house, or contest is a writing sample.

Again, those assessments are not going to be based solely upon whether the writing is strong in a general sense; every book category has slightly different standards for what constitutes good writing. As you may see for yourself, even two habitual readers of literary fiction may disagree on whether an opening page is or not. (Please forgive the giant BOOM! in the background; we know not whence it came.)