Do you mind if we talk about something else? Like, say, the times that try editors’ souls?

redundant sign 2

Or, to put it in more practical terms, if I promise to show you more properly-formatted pages while I’m at it, will you forgive my devoting tonight’s post to a foray into a notorious editorial pet peeve? What about if I talk about several?

It’s not as though there aren’t dozens from which to choose: as I may have horrified you with depressed you into a stupor by bringing up mentioned in passing last time, those of us fortunate enough to read for a living are expected — and often rigorously trained — to notice patterns in writing. How often a manuscript uses the word blanched, for instance, or describes anything as being mauve.

Not that there’s anything inherently wrong with either word choice, mind you, when used sparingly. Surely I will astonish no one, however, if I suggest that your garden-variety reader might prefer not to see characters blanching at the sight of mauve objects on every other page. Adult readers, if you must know, tend to become bored by word and phrase repetition every bit as quickly as they lose interest in a slow-moving plot, dull explanation, or unsympathetic protagonist’s plight. In order to spare the reading public that pain, editors strive to catch not only larger narrative issues, but also redundancies, whether they be of concept, image, or phrase.

And, bless our hearts, we are seldom shy about pointing them out, sometimes as early as the second or third time an author uses a pet word or action. “For heaven’s sake, Mavis,” we have been known to scrawl in manuscript margins, “Jeremy has blanched, went pale, and felt the blood drain from his face already in a 4-page scene — need he also waste the reader’s time noticing his ashen face in the nearest mirror? What’s a mirror doing in the middle of a forest, anyway? And while we’re talking plausibility,” Mavis would be expected to turn the page over here, to read the editorial scribblings on the back of the page, “are you planning at some point to provide the reader with some explanation for all of the mauve leaves on the purple trees? Is the water supply in this forest somehow tainted? Are the trees subject to some sort of lavender mite infestation? Or have you perhaps forgotten that the trees on the other side of the world you’re describing were also on the mauve side?”

Given so much provocation on the page, it is perhaps not altogether surprising that one of the great long-term liabilities of reading for a living — or one of the great advantages, depending upon how one chooses to look at it — is that over time, the dedicated pro becomes decreasingly able to read anything without scrawling corrections in the margins. I’m not merely talking about manuscripts, synopses, and queries here, mind you, but all typed words on a page. The New York Times, for instance, once the standard of American prose, now seldom passes under my long-lashed eyes without picking up some entirely justified marginalia. Nor do magazines go unscathed: I’m looking at you, Radcliffe Quarterly.

Heck, I routinely take a corrective pen to menus, fliers, and wedding programs. One recent November, I had to be restrained bodily from correcting a grievous misprint on my ballot for a county election; the proper spelling would have confused the counting machine, I’m told.

But would that not have been preferable to asking the citizenry to select a superior court joge? Possibly to serve in mauve robes?

While in some walks of life, this level of habitual scrutiny might prove somewhat problematic, for professional readers like agents, editors, and contest judges (or, in this county, joges), it’s a positive boon. So what if in some benighted professions, it is neither expected nor considered particularly sane to look one’s coworker in the eye and say, “I like the content of you’re saying, Ziggy, but the fact that you uttered the word exciting fourteen times over the course of a six-minute speech, insisted upon using impact as a verb, and failed to define a good third of your basic terms detracted from your presentation’s effectiveness,” without finding oneself cordially disinvited from all future meetings? Someone has to defend the language. And by gum, if that means rending our garments and wailing to the heavens, “You’ve used this metaphor twice in 137 pages! And phrased it almost identically each time, you…you?torturer,” well, we’re up to the task.

I see some of you blanching, doubtless at the thought of that manuscript you recently sent out to the agent of your dreams. Well might you turn pale, ashen-faced ones. If the same metaphor graced page 1 and page 241, a good editor would catch it. So is it really so much of a surprise that an even ordinarily conscientious agent — or, for that matter, Millicent, the agency screener — felt all of the blood draining from her face when that metaphor cropped up on pp. 1 and 5? Or — sacre bleu! — twice on page 1?

Half the good professional readers I know would not only have become impatient at any of these levels of metaphor repetition — they would have leapt to the conclusion that the writer was repeating himself so much on purpose. Clearly, this is an authorial plot to get away with lazy writing. As opposed to, say, an authorial failure to recognize that his pet phrase of today was also the pet phrase of three months, eight days, and sixteen hours ago.

How could you? You know how much such things upset Millicent.

Actually, you probably didn’t, at least when you first began to write. Until a writer has enjoyed the incomparable pleasure of having her work dissected disemboweled subjected to professional critique, she tends not to have any idea of how closely an agent or editor is likely to read, much less a Millicent. As we discussed yesterday, the overwhelming majority of first-time queriers and submitters fully expect their pages to be read with, if not a completely charitable eye, than at least a willingness to look past little things like conceptual redundancy and an over-reliance upon a select group of particularly nice words. It’s the overall writing that counts, right?

Can you hear Millicent giggling? From a professional reader’s perspective, the very notion that repetitious word choice, recycled notions, or even frequent typos would not be considered part of the authorial voice being offered in a submission is pretty funny. A screener can judge writing only by what’s on the manuscript page, after all. And is Millicent really so wrong to believe that a manuscript in which every inanimate object is apparently mauve-tinted might be indicative of a slight compositional problem?

Then, too, most writers radically underestimate how good a well-trained professional reader’s memory for text will be. Remember, Millicent is usually in training to become either an agent, who would be expected to read a client’s fourth revision and be able to tell how it had changed from the three previous drafts, or an editor, who might conceivably find himself telling a bestselling author, “By jingo, Maurice, I’m not going to let you do it! You used precisely that simile in Book I of this five-part series; you can’t reuse it in Book V!”

Oh, you think I’m exaggerating, do you? Earlier today, I found my text-addled mind drifting back to a novel-cum-memoir I had read, I kid you not, in junior high school. And not merely because Memorial Day is a natural time to consider the noble calling of memoir-writing. A pivotal scene in that book, I felt, would provide such a glorious illustration of a common narrative mistake — both in manuscripts and in queries, as it happens — that I just had to drop our series-in-progress and track down the book.

Yes, yes, I know: sometimes, even other editors are surprised at how well I remember text. A few years ago, when my own memoir was lumbering its way through the publication process, my acquiring editor scrawled in my margins, “Oh, yeah, right — you remember a biography of the Wright Brothers that you read in the third grade? Prove it!” I was able not only to give him a chapter breakdown of the book, but tell him the publisher and correctly identify the typeface.

That’s how little girls with braids grow up to be editors, in case you had been wondering. If anyone wants to talk about the estimable Katharine Wright Haskell, apparently the only member of the Wright family bright enough to realize that heaving the first airplane off the ground might be of more significance if somebody bothered to alert the media, I’m still prepared and raring to go.

So I had good reason to believe that my recollection of a fictionalized memoir ostensibly written by a childhood friend of Joan of Arc was reasonably accurate. A lighthearted burrow through the roughly two thousand volumes I carted up from California after my mother moved from my childhood home, so she would have to tote only the remaining eight thousand with her (long story), and voil?! The very pages I had in mind.

Care to guess whether I’d remembered the font correctly?

I’m delighted that I did, as this excerpt provides excellent examples of the kind of narrative missteps that Millicent thinks so many of you do on purpose, just to annoy her. For starters, it exhibits the all-too-common narrative trick of echoing the verbal habit of using and as a substitute for a period in first-person narration, in a misguided attempt to make the narrative voice sound more like everyday speech. It can work, but let’s face it, quite a bit of everyday speech is so repetitious that it would be stultifying if transcribed directly to the printed page.

It also, you will be pleased to hear, beautifully demonstrates another classic memoir bugbear: telling an anecdote on the page as one might do out loud at a cocktail party, with practically every sentence a summary statement. (Hey, there’s a reason that show, don’t tell is such a pervasive piece of editorial feedback.) And, most common of all in both memoir and fictional first-person narratives, the pages in question much character development for anyone but the protagonist.

All sounds pretty terrible, doesn’t it? Actually, the scene isn’t badly written; the aforementioned garden-variety reader might not even have noticed some of these problems. Nor, unfortunately, would most aspiring writers prior to submission, for the exceedingly simple reason that far too few of them ever actually sit down and read their work beginning to end, as any other reader would. The writer already knows what’s on the page, right?

Or does he? My guess is that in this instance, the writer had very little idea that what he was slapping on the page was even vaguely problematic.

But you shall judge for yourself. To render the parallels to what Millicent sees on a daily basis more obvious, as well as to continue our exercises in learning to know properly-formatted manuscript pages when we see ‘em, I’m presenting that memorable scene here in standard format. As always, my blogging program is for some reasons best known to itself a trifle hostile to page shots, so if you are having trouble reading individual words, try holding down the COMMAND key and pressing + to enlarge the images.

Twain page 1

Twain page 2

Twain page 3

Come on, admit it — while you might have excused all of those ands if you had heard this tale told out loud, they’re a trifle eye-distracting on the page, are they not? Ditto with the word repetition — could this author possibly have crammed any more uses of to be, to get, or to see into these three pages? And don’t even get me started on concept repetition.

I sense those of you committed to the noble path of writing memoir — or writing reality-based fiction — shifting uncomfortably in your chairs. “But Anne,” you protest, averting your eyes, “this isn’t the powerful negative example you led us to expect. I get what you mean about the sheer volume of ands, but other than that, there’s nothing wrong with the narrative voice here, given that this is a memoir. Isn’t part of the point of any memoir that the voice does sound like someone might speak? Is that not, in fact, one of the charms of first-person narration in general?”

Well, yes, but just as an event’s having actually occurred in real life (and it’s true, too!) does not necessarily mean that it will inevitably strike the reader as plausible on the page, first-person narration’s reading like everyday speech does not guarantee readability. In print, narrative chattiness may work against the reader’s enjoyment, because chatty people, like the rest of us, reuse words and phrases so darned much. Even talented verbal anecdotalists seldom embellish their tales with the level of detail that the most threadbare of written accounts would require. And funny out loud, let’s face it, does not always equal funny on the page.

Which is to say: as delightful as our example above might have been tumbling out of the mouth of a gifted storyteller, as a story on a page, it’s lacking quite a few elements. A sense of place, for one — is there a reason, the reader must wonder, not to give us some sense of what either the woods or the village were like? If both are left so completely to the reader’s imagination, is there not some danger that a Millicent fresh from polishing off the manuscript before this one might automatically assume that those trees were mauve, and those villages occupied by the wan?

Oh, you thought I’d dropped that running joke? In a blog, I can get away with going back to that same well this often. How many times, though, do you think I could revisit the joke in a book before the reader got bored? Or Millicent became irritated?

While you’re pondering those troubling questions, let’s return to our example. How else does it fall short?

Well, as so often happens in memoir, we’re just told that the action is happening here or there, rather than shown what those places were like. And lest anyone be tempted to shout out that old writing truism, “But it’s stylish to leave something to the reader’s imagination!, let me ask you: based upon the pages above, could you tell me where these people are with enough specificity that a reader would be able to feel like she’s there?

“But that’s not fair!” I would not blame you for shouting indignantly. “It’s the writer’s job to establish a sense of place, not the reader’s job to guess.”

Precisely what Millicent would say. She would object, and rightly, to this scene’s providing her with too little description to enable her to picture Joan and her young friends operating within an environment. Nor are those friends fleshed out much, either in character or physical trait.

Heck, poor Millie doesn’t even get to see the frightening Benoist: instead, the memoirist merely asserts repeatedly that he and Joan were getting closer, without showing us what that have looked like to a bystander. Like, say, the narrator of the scene.

Speaking of the narrator, were you able to glean much of a sense of who he is as a person? How about what his relationship is to Joan? Are you even sure of their respective ages? Any idea what year it is? Heck, if you did not already know that the girl would grow up to be the patron saint of France — actually, one of four, but Joan of Arc is certainly the best known in this country — would anything but the children’s names tip you off about what part of the world these characters inhabit?

While I’m asking so many rhetorical questions in a row — another occupational hazard, I’m afraid; margins absorb them like a sponge does water — let me ask a more fundamental one: did you notice that although this excerpt is apparently about how the village’s children reacted to Joan, there’s practically no character development for her at all?

That’s at least marginally problematic, in a book entitled — wait for it — PERSONAL RECOLLECTIONS OF JOAN OF ARC. What, we are left to wonder, does she look like? Why doesn’t she stand up to her playmates (beyond, of course, the justification of being “so girlish and shrinking in all ways”) or, failing that, why doesn’t she simply walk away from the nasty little beasts?

And don’t stand there telling me that the narrator had no choice in the matter, because that’s how it really happened. Yes, a memoir or fact-based fictional story should be true, but it also has to be both interesting in the page and plausible. Reality, unfortunately, is not always plausible; it’s the writer’s job to make it so on the page.

Which begs another editorial question: why can’t a kid brave enough to face down the village madman’s axe (or ax, depending upon where it falls in this passage; the error is in the book in front of me), a rather interesting thing for a person to do, come up with more revealing answers to questions than a simple yes? This is another notorious editorial pet peeve: almost without exception, the least character-revealing way for anyone to answer a yes-or-no question is with — again, wait for it — a simple yes or no.

Are some of you writers of the real blanching now? “But Anne,” you gasp, clutching your ashen cheeks so heavily drained of blood, “people actually do answer questions that way! And isn’t the point of written dialogue to reproduce the feel of actual speech?”

Well, that’s one of the points of dialogue. Another is not to bore the reader to death, isn’t it? And, if at all possible, it should be entertaining.

Just holding a tape recorder up to nature tends not to be the surest means of hitting any of those excellent goals. Why? Chant it with me now: most everyday speech is repetitious.

I can stand here and keep saying that as long as necessary, people. Again and again and again.

As we may see in the scene above, a character that keeps saying nothing but “Yes” isn’t exactly thrilling the reader with deep insight into her thought processes. Or even into the scene itself: little Joan is not, after all, a hostile witness in a murder trial, but a child talking with her playmates. Wouldn’t it ultimately be more realistic, then, if she sounded like the latter?

Speaking of realism, would it be too much to ask the narrator to explain why the villagers left an axe lying anywhere near the madman’s cage in the first place? Might not the locals’ efforts have been more productively expended making sure he can’t get out than chopping off his fingers?

And yes, in response to what half of you just thought: this is precisely the kind of thing an editor would have gripped her pen angrily and inked into the margins of a manuscript. Not because she’s mean, but because she’s trying to help the writer give the reader a more enjoyable reader experience.

That’s a noble calling, too, you know. But in the unlikely event that some writer out there might care less about the moral beauty of Millicent and her ilk’s devotion to textual excellence than how to worm his way past it in order improve his submission’s chances of getting picked up by an agency, let me hasten to add that the sooner a writer learns to read his own manuscript the way a professional reader would, the easier he will find self-editing. Not to mention being able to catch the Millicent-irritants that can prompt a screener or contest judge to stop reading.

In the interest of helping you fine people develop that ability, let me ask you another question about today’s example: if you had previously known absolutely nothing about what the what the real-life Jeanne d’Arc achieved, wouldn’t you find it at least a trifle too pat that her playmates choose to picture her doing more or less what she grew up to do — and to laugh at her about it? If the girl had suggested this role herself, it might merely have been not-particularly-subtle foreshadowing, but honestly, can you think of any reason to include this at all except to make the reader feel cleverer than St. Joan’s playmates?

Millicent wouldn’t be able to think of one. Neither would most professional readers; it’s our job to deplore this sort of narrative ham-handedness.

“Just how ill-informed would a reader have to be not to find that first bit clumsy?” we mutter into our much-beloved coffee mugs. “Isn’t it safe to assume that anyone who would pick up a book about Joan of Arc would know that she lead an army and was burned at the stake, even if that reader knew nothing else about her? And if your garden-variety reader knows that much, isn’t it an insult to his intelligence to drop a giant sign reading Hey, dummy, this is foreshadowing?”

Was that mighty gust of wind that just whipped the cosmos the sound of half of the memoirists out there huffing with annoyance, or was it merely the first-person novelists sighing gustily? “But Anne,” both groups think loudly in unison, rather like the remarkably collective-minded children in the anecdote above, “this is how I was taught to write first-person narration. It’s supposed to sound exactly like a real person’s speech. So why shouldn’t St. Joan’s unnamed childhood buddy sound like anybody else telling anecdotes out loud?”

A couple of reasons, actually. Yes, good first-person narration takes into account the narrator’s individual speech patterns; no dialogue should sound like just anybody. Which is precisely the problem with all of those yeses, right? All by themselves, yes and no are generally presumed to mean the same thing, regardless of who is saying them. So, like polite spoken clich?s of the “Excuse me” and “I’m so sorry for your loss” ilk, they are too generic to convey personalized content.

Strong dialogue also typically reflects the narrator’s social status and education, personal prejudices, and what s/he could conceivably know in the situation at hand. And then there are those pesky individual quirks and, yes, the century in which s/he lived.

So I ask you, first-person writers: just how does the narrative voice in this passage indicate that this particular anecdote took place not too long after the Battle of Agincourt in 1415? As opposed to, say, the 1890s, when this account was first published?

And if you were tempted even for a nanosecond to mutter in response, “Well, if the 1980s is when readers would have been seeing this dialogue, sounding like that just would have seemed normal,” let me ask a follow-up question: if this scene were narrated in the voice of a pre-teen texting this to a friend today, would that make this scene ring truer to today’s readers? Or would it merely read as though the writer either hadn’t thought much about how Joan and her friends might have communicated with one another — or was presuming that today’s readers were not capable of following any type of dialogue than their own?

Those of us who read for a living have a term for that kind of assumption: insulting the reader’s intelligence. We often find ourselves scrawling it in margins.

How often, you ask, your faces a mask of pallid horror? Well, operating on the assumption that internal monologues have both always sounded pretty much like modern speech and don’t vary much from individual to individual is as common a mistake in first-person narratives as having all teenage characters sigh and roll their eyes is in YA submissions. Yes, some people do think and talk that way, but must everybody? Should Helen of Troy formulate her innermost thoughts in the same way as, say, Eleanor Roosevelt, Louisa May Alcott, or Confucius?

There’s a dinner party, eh? I’ll bring the stuffed grape leaves.

Doesn’t it make for more interesting narration if your narrator’s speech bears at least some marks of time? And if she has some individual quirks of thought and expression?

Besides, if we are going to be true to the rules of first-person narration, shouldn’t we be objecting to how often our narrator here professes to read the other children’s minds — although, notably, not Joan’s? I don’t know about you, but I find that most of the time, my thoughts are located in my own head, not floating somewhere in the middle of a group of bystanders. Millicent, too, tends to regard her own thoughts as separate from other people’s. The inevitable consequence: characters who think together tend to annoy her, unless their shared brains crop up within science fiction or fantasy context, where they can be plausible.

That cast a different light upon the narrative choice here, doesn’t it? As an editor might well scrawl in the margin, are we supposed to believe that our narrator in this instance is a mind-reader, or that the local children were too simple-minded to be able to form individual opinions about what is going on in front of them? Is the narrator just not familiar enough with the individual characters to be able to guess how their thoughts might have differed, or, (turn page over here) since he’s of a different social class than they are — not abundantly apparent in this scene, is it? — does his reporting that they all thought the same way a function of his views of their training in rational thinking? Or does it indicate the opposite, that he feels so close to them that he presumes that his beloved friends and he could only have thought and felt identically?

“Or, Mark,” the editor might conclude, “did you originally write this scene in the third person, with an omniscient narrator that could plausibly read everyone’s thoughts? If so, you can’t legitimately endow your first-person narrator with that ability. Pick a narrative perspective and stick to it!”

In fairness to Mark, as well as all of the blanching first-person narrative writers out there, plenty of writers actually were taught to write first-person narration this way — in short stories in their high school English classes. And with good faith, too: in short bursts, run-on sentences do indeed come across as ordinary speech-like. In the published examples of this type of narration that tend to turn up in class, it’s not all that unusual for the author’s voice and the first-person narrator’s voice to merge into colloquial harmony.

Or, to put it another way, Mark Twain tends to sound like Mark Twain, for instance, no matter whose perspective is dominating a particular story. That’s part of his branding as an author, right, his distinctive narrative voice and humorous worldview?

Admittedly, adopting a chatty voice makes quite a bit of sense for narrative voice in memoir. The reader is going to have to like how the narrator/protagonist talks about her life well enough to want to follow the story for a few hundred pages, after all; we might as well get friendly. Yet in practice, the primary danger of relying on the repetitive phrasing, clich?s, and percussive and use to achieve realistic-sounding narrative cadence is precisely that it will put off the reader because as the pages pass, it can become, at the risk of repeating myself, rather boring.

Think about it: even if a memoir were being told as a collection of verbal anecdotes, wouldn’t you rather listen to a storyteller with some individual flair for phrasing, instead of someone who just sounded like everyone else? No matter how inherently exciting a personal story is, a great telling can make it better reading. So can a narrative voice reflective of the time, place, and society in which that tale takes place.

But just try telling that to Mark Twain — who, as the sharper-eyed among you may already have noticed, wrote the scene above, in what he considered his best book. Although that retrospective assessment is a trifle hard to take seriously, in light of the fact that he published the book both under a pen name and in serial form. Actually, he took it to even one more remove: he wrote a preface under a nom de plume, presenting himself as the translator of a memoir written by one of young Joan’s contemporaries.

Why go to all that trouble? Because by all accounts, he felt that the poor sales of THE PRINCE AND THE PAUPER were largely attributable to his established audience’s expecting anything published under the name of Mark Twain to be a comedy. Good branding has its drawbacks for a creative artist.

Take that, purists who would like to believe that writing with an eye toward market concerns is a product of an increasingly cynical publishing industry over the last twenty or thirty years. Twain and his publisher worked out that tactic in the 1890s.

But I digress. As a reader, how well do you think his narrative choices worked here, either as fiction narration or as the memoir narration it originally professed to be? In your opinion as a writer, how do you feel about those slips into the first person plural — is the reader carried along with the we perspective as a narrative choice, as we were in Jeffrey Eugenides’ THE VIRGIN SUICIDES, or does it read like a perspective slip?

In today’s example, do you feel that the mostly distinctly modern narrative voice, coupled with the almost entirely uncritical view of Joan, was the best way to tell this tale? Reviewers in Twain’s time did not think so — they believed (and I must say I agreed with them back in junior high school) that a protagonist who never does anything wrong is a trifle on the dull side, as far as the reader is concerned. Twain’s Joan never sets a wee foot wrong; even in her earliest youth, he tells us, she raised her voice in anger only once, and even then it was to voice a patriotic thought.

A taciturnity unusual in a rabble-rouser, you must admit. Also an unusual characteristic for someone who challenged social norms enough for anyone to want to burn her at the stake: Twain’s narrator presents her as a quiet, universally beloved little girl. Butter, as folks used to say, would not melt in her mouth.

But is that how little girls with braids grow up to lead armies?

Twain evidently thought so. No matter how outside-the-box her observations or actions are shown to be (or, as we saw above, summarized to be), in this narrative, nothing she did or said from birth to the age of fourteen so much as ruffled the composure of the inhabitants of a querulous small village in wartime. Surprising, to say the least, in a young lady who by her own account had been engaging in frequent heart-to-heart chats with a couple of your more illustrious virgin martyrs since the age of twelve.

Perhaps the querulous small village where I spent my formative years was atypical, but I’m inclined to think that had I gone around snatching murder weapons from the clutches of local lunatics or holding confabs with deceased ancient Roman maidens, the locals might have had a thing or two to say about it. I’m also inclined to think that their observations would not have been entirely favorable, regardless of how winsome and girlish I might have been while disarming the maniac in question. It doesn’t strike me as the type of endeavor best undertaken in a party dress.

I’m not saying that Twain is necessarily factually incorrect about any of this; naturally, his best guess is as good as ours on a lot of these points. The little lady lived rather a long time ago, so the issue here is less historical accuracy than dramatic plausibility. Still, just because something really happened does not mean it will necessarily come across as plausible on the page; as agents like to say, it all depends on the writing.

As an editor, though, I think it was Uncle Mark’s job as a writer’s to make me believe his take on this. Presuming you agree with me — speak now or forever hold your peace — I ask you: was this narrative choice the best fit for the story he wanted to tell? And if not, should Millicent accept this manuscript?

Does the fact that a good third of you just began hyperventilating mean that it had not occurred to you that whether a story is not only well-written, but attacked from an appropriate narrative angle is a potential rejection trigger? It is, inevitably. Wouldn’t it have been nice if your last rejection letter had told you that, if Millicent or her boss thought that your first-person story would have worked better as a third-person narrative, or vice-versa?

Literary taste is, of course, to a very great extent individual, so only you can answer my question about Uncle Mark’s narrative choices to your own satisfaction. Am I correct in presuming, though, that you are at least a tiny bit curious about how an editor currently holding down the literary fort in the U.S. publishing world might respond to the choices he did make? Glad you asked. Let the scrawling begin!

What am I hoping you will take from this, you ask, eyes wide with horror and previously rosy cheeks drained of blood? Not merely that being a brilliant writer does not necessarily preclude turning out a clunker of a first draft from time to time — although that’s not a bad thing for aspiring writers to bear in mind. The popular conception of true literary talent’s consisting of letter-perfect creative phrasing dripping from one’s fingertips directly onto the page, with no further polishing necessary, each and every time, does not match up particularly well with reality. As any experienced editor could tell you, most of the books people regard as semi-miraculous productions of pure inspiration have actually been worked, reworked, and run past half a dozen critical readers.

And I mean critical readers. The kind who will remember what the author did in the same scene in each previous draft.

Remember that, please, the next time you’re struggling with a scene that just doesn’t seem to want to hit the page gracefully — or with much specificity. In moments like that, it can be very tempting to embrace the tack Twain did above, writing up the scene in summary form, with few vivid details, just to get the darned thing committed to paper as rapidly as humanly possible.

What makes me think that this was written quickly? Editorial instinct, mostly: I find it hard to believe that a humorist as gifted at reading out loud as I know Twain to have been would have killed the comedy — or bored the reader — with this much word repetition unless he was writing on a pretty tight deadline. Serialization tended to be submitted that way back then, you know, as Dickens would have been only too glad to tell you. Had Uncle Mark taken the time to revisit this scene and iron out its wrinkles, I don’t think there would have been quite so many references to eyes — and, frankly, I don’t think that he would have had his narrator faint at the climax of the scene. He was too good a storyteller.

But that choice certainly saved the author the trouble of having to figure out how the girl convinced the wild man to give up the axe, though, didn’t it? Trust me on this one: experienced editors — and Millicents — see this type of narrative shortcut often enough to recognize it for what it is.

So what should a savvy writer do when faced with this sort of first-draft dilemma? Go ahead, give in to temptation; there is value in getting a full scene on paper. Just make sure to set aside time later in the writing process to return to that scene and flesh it out.

Unless you would prefer to have your future editor bark at you, “This is lazy writing, Ambrose. Didn’t anybody ever tell you to show, don’t tell?”

Just in case nobody has yet snarled that in the general direction of your manuscript: show, don’t tell. Immerse your reader in sufficient details for her to be able to feel as though she is part of the scene, rather than leaving her to fill in the specifics for herself.

Oh, you don’t think that’s what Twain is doing here? Okay, rise from your chair, grab the nearest willing partner, and try to act out this interaction between young Joan and Benoist, based solely upon the choreography the narrator above chose to provide us:

She stood up and faced the man, and remained so. As we reached the wood that borders the grassy clearing and jumped into its shelter, two or three of us glanced back to see if Benoist was gaining on us, and this is what we saw — Joan standing, and the maniac gliding stealthily toward her with his axe lifted. The sight was sickening. We stood where we were, trembling and not able to move. I did not want to see murder done, and yet I could not take my eyes away. Now I saw Joan step forward to meet the man, though I believed my eyes must be deceiving me. Then I saw him stop. He threatened her with his ax, as if to warn her not to come further, but went steadily on, until she was right in front of him — right under his axe. Then she stopped, and seemed to begin to talk with him. It made me sick, yes, giddy, and everything swam around me, and I could not see anything for a time — whether long or brief I do not know. When this passed and I looked again, Joan was walking by the man’s side toward the village, holding him by his hand. The axe was in her other hand.

Not much practical guidance for the actors there, eh? Other than all of that seeing (a word most writers tend to overuse in early drafts, incidentally), the actual movements mentioned here are pretty routine: one party standing still, the other moving toward her. The mover threatens, but we are not told how. Admittedly, a lifted axe doesn’t have to move much to seem threatening, but did you notice how pretty much all of the sense of danger is conveyed via the narrator’s dread, rather than through showing the reader vivid, terrifying specifics? And how virtually all of that dread is summarized, rather than shown in any detail?

From an editorial perspective, that lack of specificity distances the reader from what should have been a thrilling scene: by leaving us to fill in the details, the narrator abdicates his proper role here. It’s his job to make us feel that we were there, or at least to show us the scene engagingly enough that we have that illusion.

Yes, he grounds us in his experience by telling us repeatedly that he is seeing this or that, and that these sights made him feel sick (and ultimately pass out). But great heavens, man, if you’re going to narrate a story like this, isn’t it your job to at least ask a bystander what happened, so you could share that information with the reader?

Don’t tell me that once you’ve seen one axe-wielding madman, you’ve seen ‘em all. As both a reader and an editor, I want to know what this particular madman looked, sounded, moved, smelled, and felt like. I want to know precisely what our heroine did that gave Benoist pause; I want to be shown how he crept up on her stealthily while apparently walking straight into her line of vision. And gosh darn it, I want to know how an axe of 1415 differed from one I might buy at the corner hardware store today.

Without those details, and phrased in fairly ordinary terms, this excerpt is indeed like everyday speech, in the negative sense, despite the inherently exciting subject matter. Substitute a memo-wielding boss for the axe-bearing madman, and this could have been an anecdote overheard in a coffee house after work, couldn’t it?

Please don’t limit your answer to a simple yes or no. I was hoping to learn something about you.

Distancing the reader from the action in this manner is an unfortunately common tactic in memoirs and first-person fictional narratives alike. Instead of showing the reader what happened through a fully realized scene, the narrator simply summarizes; rather than demonstrating relationship dynamics through dialogue or action, the narrator just sums up what was said. And by describing subsequent actions in the same words or in hackneyed terms (I believed my eyes must be deceiving me? Really, Mark?), the action may move forward, but the reader’s understanding of what’s going on does not.

Joan stood; Benoist glided. Then Joan stood while Benoist glided. Then she stopped — odd as the narrative had not shown her going forward. Then the narrator conveniently blacks out so we cannot see what is going on. Then the problem is solved. The end.

A bit mauve, isn’t it? Well might you turn pale.

Seldom is this the most interesting way to convey a story, in my experience. Like having characters answer yes-or-no questions with yes or no, as opposed to more detailed (and thus more character-revealing) responses, the summary route closes off story possibilities. And by definition, repeated phrasing adds nothing new to the scene.

Neither, incidentally, do all of those thens: logically, they are unnecessary. Why? Well, in a story in which events are being presented in chronological order, the occurrences in Sentence 1 are presumed to have happened before those in Sentence 2, which in turn came before what’s described in Sentence 3.

Thens, then, as we have seen them used in that last example, are logically redundant; most editors would advise you to reserve them for moments when what happens next is genuinely unexpected. Take a gander:

Joan stood; Benoist glided toward her with an axe. Then the Wright Brothers and their sister, Katherine, swooped through an opening in the forest canopy in a motorized glider to snatch the weapon away.

Admit it — you didn’t see that last twist coming, did you? As a reader, didn’t you get a kick out of that?

Remember, there’s more to telling a story than simply listing its events in the order they occurred. Racing from its beginning to its end may not be the best way to engage the reader. You want the journey to be both memorable and enjoyable, right? And if the narrative can manage either to surprise the reader with an unanticipated turn of events, delight her with astonishing imagery, or intrigue her with beautiful phrasing — ideally, all three — all the better.

Before I release you to ponder the challenges of expanding a first-person narrative from the anecdotal level into a completely inhabited scene, I want to talk about another common faux pas: the further distancing effect of the narrative’s reminding us repeatedly that the narrator is seeing, hearing, or observing this or that. Obviously — at least from a professional reader’s perspective — if an action or object is depicted in a first-person narrative, the narrator perceived it; otherwise, she could not legitimately bring it up, right?

So when Twain’s narrator tells us repeatedly that he saw Joan do this or Benoist do that, it’s logically redundant. Of course, he saw it: he was standing right there. Why bother to remind the reader of that self-evident fact? Or, to put it as a garment-rending professional reader might, does the author think the reader is too brain-dead to remember who the narrator is and that he is present?

Oh, you don’t want the pros to take every word you commit to the page that seriously? But it’s how they show their respect for your eventual readers!

And for your literary gifts. Again: if it’s on the page and the writer appears to possess even the slightest vestige of talent, Millicent is going to assume that you put it there on purpose. She’s also going to believe, with good reason, that if a writer has set up rules for how the story is to be told — in this case, from the point of view of a childhood friend of Joan’s, and only from his perspective — the narrative will follow those rules consistently.

This, too, trips up quite a lot of memoirists and other first-person narrator-wranglers. Once a narrative is committed to a single perspective, it cannot report anything outside of it without shattering the illusion of a limited point of view. Thus, when the narrator slips into the first person plural, informing us that we saw this or thought that, it’s jarring to the reader’s sensibilities.

And when, like Twain’s narrator, he professes to know what we all are thinking…well, let’s just say that maybe Joan isn’t the only one who needs to be worrying about going on trial for dabbling in the supernatural. Unless the narrative establishes some means by which a first-person narrator could possibly have reliable insight into other characters’ thoughts and feelings, he should really stick to his own.

If his thoughts and feelings are somehow different from every Tom, Dick, and Benoist who might be hanging around in the same place at the same time, great. If he can manage to express them in language evocative, memorable, and tailored to his individual worldview, though, even better. And if he can work in a little character development, perhaps through revealing dialogue, terrific.

Which is not a bad definition of memoir voice, if you think about it: a narrator with a strong personality and specific worldview recounting situations of significance to an overall dramatic story arc in language and from a perspective unique to the teller. If every sentence of your memoir — and, to bring this back to our series-in-progress, every sentence of your query’s book description — does not rise to that level, you might want to think about revising it.

Millicent will thank you. So will your readers.

So Mark, darling, as much as I admire your writing in general and short stories in particular, if I were your editor — oh, you thought that editors don’t live in the hope that this type of activity would be the first, best use of a time machine? — I would insist that you sat down and revised these three pages. Actually, I would do it because I admire your writing: your narrative voice, even in this rather serious book, is better than what we’re seeing here.

And that axe you keep telling us you’re seeing, narrator? Try to think of it as your editor, chopping away all of that phrasing and conceptual redundancy. Trust your reader’s intelligence a bit more, please.

Do bear in mind, too, that while reality itself can be convoluted and devoid of point, readers have a right to expect a book based upon real events to be a good story possessed of an identifiable story arc. It should be dramatically satisfying. And if the real-life version is not, believe me, Millicent isn’t going to be inclined to take that as an excuse.

No need to go pale about this. You can do it. But in order to pull it off successfully, you’re going to have to be able to read your work not only like a writer, but also like a reader.

Oh, it feels good to be delving back into craft. Would anyone mind if I continued to keep standard format illustration on the back burner for a bit and made narrative voice my topic of the week?

Actually, that’s a rhetorical question, come to think of it. Keep up the good work!

At the risk of repeating myself, part V: I’ve got three favorite cars that get most of my job done — no, wait, make that four

Sorry about the slower-than-expected follow-up post, campers: I honestly did intend to devote this week to structural repetition — because, as we all know, there’s nothing like a sexy topic for drawing in the readers. Our cat began acting strangely, however, so I have been spending an extraordinary amount of time at the vet’s office. Fortunately, I had a good book on me, my buddy Nicole Galland’s new release, I, IAGO, and lordy, is it a great read. I’m seriously tempted to leave my copy in the vet’s waiting room after I’ve finished, to provide a lush mental escape for the worried.

Seriously, how often has a book made you laugh out loud while waiting for blood test results? From the publisher’s blurb:

From earliest childhood, the precocious boy called Iago had inconvenient tendencies toward honesty — a “failing” that made him an embarrassment to his family and an outcast in the corrupted culture of glittering, Renaissance Venice. Embracing military life as an antidote to the frippery of Venetian society, he won the glowing love of the beautiful Emilia, and the regard of Venice’s revered General Othello. After years of abuse and rejection, Iago was poised to win everything he ever fought for — until a cascade of unexpected betrayals propel him on a catastrophic quest for righteous vengeance, contorting his moral compass until he has betrayed his closest friends and family and sealed his own fate as one of the most notorious villains of all time.

Okay, I’ll admit it: I’m a sucker for any blurb containing the word frippery. One of my failings as a human being, I suppose.

One of my other failings as a human being, but a positive boon for my life as an editor, is a reading eye that leaps instantly to the anomaly on the page. Perhaps that’s not altogether surprising, as a have a doctorate in pattern recognition, but honestly, it does render casual reading a bit of a challenge. A slug line in the wrong place, for instance, will drive me mad, regardless of the quality of the writing lurking beneath it. So will adverbs beginning three out of five sentences in a paragraph: Clearly, there was something wrong here. Obviously, though, your garden-variety reader would not catch it. Bizarrely, any professional reader would.

Fortunately (God, there’s a fourth one!), however, in the publishing world, this sort of eye is not only an advantage — it’s pretty much a requirement for a good editor. Apart from accountancy and computer programming, you’d be hard-pressed to find a job better suited to the obsessive-compulsive. Thus, it follows as night the day, spring winter, and baby ducks their mother that those who cater to the tastes of editors would develop a similar seventh sense for patterns on a page.

Oh, you thought this wasn’t going to lead back to you and your manuscript? You and your manuscript keep me up nights. I worry so that your good writing might not get the fair reading it deserves at the hands of Millicent, the agency screener, if it exhibits too much word, phrase, and/or structural repetition.

Speaking of hands, a third of my audience’s just shot skyward. “Um, Anne?” the more eagle-eyed among you quaver. “I hate to pick nits here, but how precisely do Millicent’s hands read anything? Wouldn’t it be her eyes?”

That question brings a tear to my weary eye, campers. If you caught that logical gaffe, you’re starting to read like a professional. And if you also noticed that in the video above, we never actually get to see our hero’s eyeballs — a trifle disturbing, I think, in a cartoon devoted to developing reading and writing skills — you may be on your way to becoming a Millicent.

Although, admittedly some of us are born that way. I distinctly recall that the first time Conjunction Junction popped onto our small black-and-white TV screen, I tossed my wee braids and shouted, “Mother! How can he read with no eyes?” Fortunately, my mother had been editing for years, so she had been taken aback, too.

In case I’m being too subtle here: those of us that read for a living notice everything in a submission or contest entry. It’s our job, and if nature was kind enough to outfit us with specialized eyes and brains in order to be good at it, well, that has some ramifications for writers.

All of which is a long-winded way of saying that I cannot in good conscience round off my lobbying for reduced repetition in your manuscripts without discussing those most perennially popular transients passing through Conjunction Junction: and, but, and then.

This time, encouraged by positive reinforcement, legions of hands shoot into the air. Yes, newly-minted 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, or or — deserving of your august scrutiny?”

Quite right, hand-raisers: when used properly, then isn’t a conjunction, strictly speaking. We live, however, in a world overrun by scofflaws. Metaphors are mixed; semicolons are routinely misused. Jaywalkers abound — unwisely, given how many drivers do not come to a full stop at stop signs. Owners of outdoor-ranging cats discover that their pets have discarded their collars, complete with city-issued license, and do not replace the tags immediately, while owners of dogs occasionally take them off-leash even outside the parks designated for such activity.

We may deplore all of this, but we ignore it at our peril. At least, that hefty majority of aspiring writers whose submissions and literary contest entries positively scream, “The leash laws do not apply to my dog!” do so at their own risks — but does that mean that your Auntie Anne, friend of the struggling scribbler, should refuse on general principle to talk about those mutts?

No, I haven’t the heart. Call me a softie, but 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’s bloodshot 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 well-known SF short story writer in the 1950s, an editor at the LA Free Press, and a folklorist of great repute) used to scrawl in the margins of letters I wrote him in elementary school, 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, and a crayon is not an appropriate writing implement for correspondence. How’s your mother?”

There are easier things than growing up in a family of writers and editors. I thought until I hit puberty that writing in the first person was a narrative cop-out, embraced by only those authors who could not handle suspense in any other way. (A fairly common editorial opinion well into the early 1980s, incidentally.) 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?

Hey, I couldn’t resist. But why shouldn’t we slavishly adhere to his precepts? Well, time and the language have been marching merrily onward, 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 thunder 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 and visually. However, I suspect that most current readers of English prose would recognize a substantial difference in the rhythm.

Why? 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 legitimately be regarded as subtle narrative indicators of protagonist stress — a bit of authorial frippery, rather than a mistake. 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. We diagram sentences in our sleep.

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 machete pen and remove a couple of classic Millicent-irritants. Rather than merely noticing that this third version reads better, I shall challenge your revision skills by asking you to try to figure out why it reads better.

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? Lift a nice, shiny gold star from the reward cabinet if you immediately cried, “Why, word repetition is word repetition, Anne — which is why you removed the second Arbogast 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 award 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. Would the paragraph lose any actual meaning if I cut or not?”

I hear those of you who did not shout any of those observations muttering under your collective breath, and you’re quite right: this is incredibly 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 — perhaps best summed up as 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 boon to dialogue. Or to first-person narration, as it creates the illusion of echoing actual speech. That does not mean, however, that peppering third-person narrative prose with it will necessarily produce a flowing effect. Generally speaking, this structure works best in dialogue.

Not sure why? 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. And particularly when running (generally while identified only as she through wooded glens at the openings of novels. Yet you are astonishingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingenue sidekicks never seem to twist their ankles navigating. And, naturally, you are entirely unarmed at all times. Lest some particularly timid reader find you even remotely threatening for even an instant. 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, particularly when running (generally while identified only as she through wooded glens at the openings of novels, yet surprisingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingenue sidekicks never seem to twist their ankles navigating. Naturally, you are entirely unarmed, lest some particularly timid reader find you even remotely threatening for even an instant. 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, I’ll admit 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.

And, let’s face it, Spencer’s lengthy speech as presented in the second version would be darned hard to say within the space of one breath. Go ahead and try it; I’ll wait.

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) Launch into a lengthy anecdote, preferably one devoid of point, 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. But then, I’m a professional; you might not want to attempt that high dive your first time out.

The difficulty inherent to interrupting a non-stop speaker, in case you happen to be writing a book about such things, why university professors, 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 reply.

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.

“But I can’t pay the rent!”

“But you must pay the rent!”

Those buts don’t leave much doubt about the source of the disagreement, do they? Those capital Bs are like a beacon to Millicent’ eye. While that can work just fine in dialogue, it’s visually distracting in narration.

But I couldn’t pay the rent, not today, not tomorrow, not even next week. But I must pay the rent! I knew that, both ethically and practically. But that did not mean I had the means to do it. I mean, where was I going to get the rent? I wasn’t naïve enough to believe that a handsome stranger would appear on my dastardly landlord’s doorstep and announce, “I’ll pay the rent.” But that seemed more likely than my coming up with the dosh myself.

Pop quiz: did the word repetition bug you as much as all of those capital Bs? I should hope so, by this late point in the series.

I know, I know: the writer may well have repeated those words deliberately, to make a point. (Indeed, I have it on fairly good authority that the writer in this instance believed it would have some comic value.) Do be aware, though, that this is a strategy is not a particularly unusual one. Virtually any Millicent will see it in at least one submission per day.

Why? Well, as we have discussed, many aspiring writers just like that repetitive rhythm — but it’s also one of the most popular means of establishing 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. A fairly common way to open a manuscript:

And I thought it could never happen to me. I had always thought it was just a cartoon cliché. But here it was, happening: me pinned to the ground, struggling. While a mustache-twirling villain tied me to the railroad tracks. The railroad tracks, no less, as if anyone took trains anymore. And with my luck, I’d end up lying here for days before a locomotive happened by.

“That will teach you,” my captor gloated, “not to pay the rent.”

And 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?

Since false consecutiveness is stylistically ubiquitous, you might want to screen your submission for its frequency. Particularly, if you’ll forgive my being marketing-minded here, in the early pages of your manuscript. And absolutely on the first page.

Why especially there? 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 the instant they decide that the writing is weak.

Was that sudden blinding flash an indication that light bulbs just went off over a thousand 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. Again, I’m happy to 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 at any point in a submission or contest entry. If you lean too hard on 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’ editorial rantings? “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.

Ready to exercise some authorial autonomy? Excellent. 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, for our purposes. Nor is simply doing a Word search for conjunctions. 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 pen color for and, another for but (go ahead and use it for the howevers and yets as well), and a third for then. If you are prone to equivocation, you might want to designate a fourth for or.

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. Don’t fudge — the experiment will not be nearly so useful.

(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, then slid them onto the plate, and 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 entirely unnecessary here. In not entirely unrelated news, then is almost always omittable as a purely temporal marker.

“Pardon my asking,” Millicent says, wondering why I have a latté 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, Millie. To professional eyes, the 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, scarring him for life.

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 your attention 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!”

Good question, but-resters, but I did mean what I said. But, however and yet logically imply contradiction to what has already been stated. Yet 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, bottle of antihistamines, and seventeen homeopathic remedies were 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, though: 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 interlocutors, 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. Trust me, agents and editors alike will bless you if your manuscript is relatively light on these overworked conjunctions.

Or if you don’t overuse favorite words in general. Honestly, those of us that write for the American market have no excuse. 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.

I wish more first-time submitters knew that, but usually, US writers have been taught just the opposite: 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. To see why, we have only to glance at a genre- and character-inappropriate vocabulary shoved into the mouth of a protagonist — particularly common in memoir and autobiographical fiction, incidentally, in which the writer wishes to indicate, however subtly, that Our Hero is much, much smarter than everybody else in the story. To pile the pet peeves even higher, let’s make it a child that talks like an adult.

“Hey,” Mom shouted. “Did someone take the pie?”

“In the entirety of my five and a half years’ subsistence, situated upon this terrestrial sphere,” Babette murmured, “I have seldom been so incensed. Nay, apoplectic. That you, Mater, would indict me of having pilfered, purloined, and/or absconded with your irreplaceable peach pie, in lieu of interrogating my shifty-eyed sibling, flabbergasts me. I mandate an instantaneous act of contrition.”

“Yeah, you and what army?” Benjy sneered, kicking his high chair.

“Now, now,” Mom said. “Stop squabbling, children.”

Even if young Babette’s speaking like an 18th-century clergyman were somehow in character, it’s distracting that the text suddenly breaks out in SAT words. That’s not necessarily a deal-breaker for Millie, but there are few book categories in which the vocabulary level displayed above would be audience-appropriate.

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 particular character would ever use — or that his otherwise estimable daughter could spell. Yet from context, it wasn’t intended humorously: evidently, the screenwriter simply liked the word.

Nothing wrong with that, of course — but as I may have mentioned earlier in this series, 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, Josette, and Babette in 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 passages copying that?”

Well caught, Millicent: writers often harbor affection for similar names. But just as a skimming reader is likely to mix up those whose names begin with the same first letter — a real pity, as Joan, Jane, Joanne have virtually nothing in common otherwise — names with similar characteristics, or even ones that sound similar, may cause unnecessary confusion. Or don’t you believe that, Jon, Von, Van, and Alan?

Wow, we’ve covered a lot of ground today, have we not? But 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!

At the risk of repeating myself, part IV: evading the tentacles of the dreaded Millicent-irritating squid

Happy St. George’s Day, everybody! Traditionally, the streets of Barcelona are filled with rose sellers and bookstalls on this day: the custom has long been to give one’s love a rose and a book to mark the occasion.

Why the book? It’s Miguel de Cervantes’ birthday. DON QUIXOTE was one of the first large-scale bestsellers.

In the spirit of celebration, I’d like to share few bits of happy news before I launch into today’s peroration on all things repetitive. First, in recognition of William Shakespeare’s birthday (you still have an hour or so to run out and buy him a present, West Coasters, if you forgot to pick one up when you bought Cervantes’), magnificent historical novelist, lyrical actress, and all-around Bard maven Nicole Galland has written a lovely article on the Huffington Post about why his work remains well worth every English-reading person’s while. Nicely done, Nicki!

(And just between ourselves, Amazon is running an amazing deal right now on her soon-to-be-released novel, I, IAGO: today, they’re offering a whopping 32% off the cover price. Just in case you happened to be looking for a birthday present for anyone.)

As if that weren’t enough to set the Author! Author! masses rejoicing, brilliant fiction stylist and cook extraordinaire (isn’t it fascinating how often the two go hand-in-hand?) Bharti Kirchner’s fifth novel and eighth book, TULIP SEASON has just come out as an e-book, with trade paper to follow soon. This one’s a mystery, and thus a bit of a departure for this well-established literary novelist. Having read a couple of incarnations of this story — oh, you thought that once a writer became a professional, she dropped out of her critique group? — I have to say, I love her voice in the new genre. And that’s saying something, as I consider the ending of her novel Pastries one of my favorite of the last decade of literary fiction releases.

Why? Well, Bharti’s extraordinary eye for nuanced detail and subtle character analysis really shines here. I don’t want to give too much away, but here’s the publisher’s blurb:

A missing domestic-violence counselor. A wealthy and callous husband. A dangerous romance.

Kareena Sinha, an Indian-American domestic-violence counselor, disappears from her Seattle home. When the police dismiss suspicions that she herself was a victim of spousal abuse, her best friend, Mitra Basu, a young landscape designer, resolves to find her. Mitra’s search reveals glimpses of a secret life involving her friend and a Bollywood actor of ill repute. Following the trail, Mitra is lured back to India where she uncovers the actor’s ties to the Mumbai underworld and his financial difficulties –- leading her into a web of life-threatening intrigue where Mitra can’t be sure of Kareena’s safety or her own.

She had you at Bollywood actor of ill repute, didn’t she? It really is quite a ride.

Third, I decided this very morning that I am going to give in to the collective pleas of no fewer than seven apparently otherwise unrelated readers and run a series on the ins and outs of entering literary contests. Beginning later in this week (oh, you thought I had only one more post’s worth of things to say about structural and conceptual repetition?), I shall be talking at length and in my patented obsessive detail about how to select the contest most likely to recognize your particular writing gifts, how to read contest rules, how to follow them (not always the same thing), and most important of all to your entry’s success, what kinds of things judges seek and deplore in entries.

Having both won a major national writing competition and served often as a judge, I’m here to tell you: this stuff isn’t self-evident. Reading contest rules is an acquired skill.

Or so I surmise from the many, many questions I regularly receive on the subject; I have written about it at length before. As is so often the case, I had responded to the first two such requests this year with a cheerful suggestion that the question-askers check out my earlier posts on the subject, conveniently collected under the CONTESTS AND HOW TO ENTER THEM SUCCESSFULLY category heading on the archive list at right. By the fifth such question, I started to wonder if it wasn’t time to run an entire series about it again, rather then answering questions piecemeal. Then this very morning, when the seventh request rolled in, it occurred to me to check just how long it had been since I had tackled that Herculean task.

Let me put it this way: the last time I set aside a couple of months to blog about it, the economy was humming along just fine. So was the publishing industry: people were still buying new books in droves. . (One of the seldom-discussed aspects of the book world’s contraction: used book sales never declined; according to all of the data I have seen, they actually went up.) They were just the teensiest bit concerned about the rumored e-publishing phenomenon, but like every other fad, they were pretty confident that it would pass quickly.

It’s time, in short.

To make the timing seem even more apt, I’m going to resurrect my 2008 strategy of picking a specific contest to discuss. Why? Well, it’s always helpful to have a concrete example when talking theory — and, let’s face it, it’s more fun if we’re all working on a project together. This time around, I shall be taking a hard, close look at the entry guidelines for the Words and Music, November 28 to December 2. Dare I hope that I will see some of you accepting top honors there?

Okay, back to our business already in progress: craft. Specifically, that most pervasive of submission bugbears, word and phrase repetition?

Surprised that I have so much to say on the subject? Unfortunately, that’s a reflection of submission reality: just as every spring brings a fresh crop of tulips, similar to last years yet not the same, poor Millicent the agency screener’s inbox is continually refilled with manuscript that repeat themselves. And repeat themselves. And did I mention that they repeat themselves?

Not always as obviously as I just did, naturally — although you would be surprised how often even page 1 of a submission contains the same word or phrase three or four times. Why might that be the case? Quite a few, many, and/or a proportion of the writing public, the pushers of the pen, the haunters of the keyboard seem predisposed, have a tendency to, or just plain enjoy saying the same thing, speaking a similar concept, and stepping into the same river twice. Or thrice, three times, a trilogy. Or just plain throwing caution to the winds, grabbing their destinies with both hands, and jumping in that stream with both feet.

Are you thanking the Muses that most human characters possess only two feet, so the narration could not keep revisiting them until there seemed to be seventeen? I assure you, Millicent would be. She sees enough conceptual redundancy in one day of screening to compile her own dictionary of euphemisms.

And enough repetitive information to drive her to distraction. So does her aunt, our old friend Mehitabel the veteran contest judge. “Why are you telling me this again?” they wail in unison, rending their respective garments. “Are you afraid that I didn’t catch this particular plot point when it first appeared three pages ago? Or do you think I did read it, but I’m just a…”

Because my readership possesses such tender sensibilities, I shall spare you the word those of us who read for a living almost universally apply in these instances. Suffice it to say that it rhymes with squidiot.

As in, “What does this writer think I am, a squidiot?”

Alas for many an otherwise admirably-written manuscript or contest entry, the presumption of squidiocy is a common bugbear for new writers. It’s the squid that whispers in their ears, “Tell, don’t show,” and not just because squids are notorious shortcut-takers. Yes, it’s usually quite a bit quicker and easier to summarize action, dialogue, or emotional response with flat statements — Ambrose was sad. The pair discussed their marital difficulties. Melissa ran up fifteen flights of stairs, turned right, and sent the haunted portrait hurtling to the marble floor below. — rather than showing them through a series of specifics. But convenience is not the squid’s best lure for a rookie writer.

What is? Taunting her with the horrifying possibility that the reader might not draw the correct conclusion.

Has the squid just released a small battalion of you from its capacious arms, or are many of you shouting because you’ve had an insight? “But Anne!” the liberated masses shout. “That’s not what the classic writing advice show, don’t tell means, is it? I’ve always assumed that it referred to the proportion of action to contemplation in the text. Rather than having my protagonist sit around and analyze what’s going on, I’m supposed to stuff my scenes with conflict, right?”

That’s certainly good writing advice, former squid victims, but that’s about avoiding an equally common Millicent-irritant, the passive protagonist. By all means, consider excising scenes in which your protagonist ponders over coffee/tea/a beer/a meal/his cat/the steering wheel of his car what the reader has just seen happen. Ditto with the dialogue in which he explains it all to his best friend/partner on the police force/mother/George, the fellow that lives in his head, because, let’s face it, that’s recapping.

And, frankly, too much recapping can slow a novel’s pace to a crawl. Not to mention endangering Millicent and Mehitabel’s garments. “We just saw this happen!” they moan, shredding their hems. “What kind of a squidiot would I have to be to require a reminder that Hortense fell off a cliff in the previous chapter? In what kind of novel would that not be memorable?”

That’s a different problem than telling the reader what to think about it all, however. Show, don’t tell is what the pros bark at text that consists mostly of summary statements about relationships, activities, emotional states, etc. Instead of setting out a series of actions, revealing gestures, subtly suggestive dialogue, and so forth to demonstrate what is going on, trusting the reader to be intelligent and sensitive enough to draw the correct conclusions from that array of clues, the narrative simply states those conclusions. Or, as is astonishingly common in submissions, both shows the clues and tells the conclusions.

Not quite sure what each option would look like in practice? Okay, here’s a told interaction.

Blue to the bone, Miss M. walked across the room and sat on a tuffet. She was starving. “Where are my curds and whey?” she called crossly.

She was startled by the spider that dropped down beside her. He was polite, but he frightened her away.

Not devoid of interest, stylistically speaking, but hardly a subtle demonstration of human-arachnid relations. Here’s that same series events, shown rather than told.

Miss M. dragged her feet, listless, toward the kitchen, nearly deafened by the rumbling of her stomach. Halfway across the dusty floor, her legs crumbled beneath her. Thank goodness, a tuffet was handy.

“Where are my curds and whey?” she called. “Dag nab it, Goldilocks, you were supposed to have dinner ready an hour ago.”

A cold and slimy leg tapped her on the shoulder. “Excuse me,” a spider as big as a Volkswagen said, “but I believe that’s my seat.”

Palpating, she watched the venom form on its fang, threatening to drop into her eye. She wrenched herself off the tuffet and fled the room.

Makes for more engaging reading, does it not? That’s because the storyline is presented through specifics, not generalities. Yet the intended meaning comes across just the same; the reader is simply presumed to be free enough of pernicious squidiotic influences to be able to follow what’s going on without being told outright.

For the sake of argument, though, let’s allow the dreaded assumption of squidiocy to pervade the narrative. Here’s what might happen if the squid persuaded our example-writer that Millicent could not be relied upon to conclude that two plus two might render something in the neighborhood of four.

Miss M. dragged her feet because she was listless. She was headed toward the kitchen, nearly deafened by the rumbling of her stomach; she was hungry. That trip took her halfway across the dusty floor, where her legs gave out beneath her, as she was tired. Thank goodness, a tuffet was handy, so she sat on it.

“Where are my curds and whey?” she called crossly into the kitchen, where her fellow fable inhabitant was cooking. That’s what kitchens are for, in case you didn’t know. “Dag nab it, Goldilocks, you were supposed to have dinner ready an hour ago. I am hungry, so I would like to have it sooner.”

A cold and slimy leg tapped her on the shoulder. It belonged to a spider as big as a Volkswagen hanging over her, attached by a thin strand of web from the chandelier. “Excuse me,” it said, “but I believe that’s my seat.”

She reacted with horror. Palpating, her heart beating fast, she watched the venom form on its fang, threatening to drop into her eye, where it might poison and even kill her. Fearing for her life, she wrenched herself off the tuffet and fled the room to the kitchen, where her friend was. Goldy might save her; she had bear-fighting experience.

A trifle over-explained, isn’t it? Cue the garment-rending: “What does the writer of CHARACTERS FROM THE NURSERY IN SEARCH OF AN AUTHOR think I am? A — wait for it — squidiot?

No, Millicent and Mehitabel, the writer of that last example or any of the hundreds of thousands like it you have seen does not think you are a squidiot (although s/he may harbor that suspicion about the end reader). In all probability, s/he merely thought s/he was being thorough.

Or that the phrasing was so nice that it bore inclusion. Or because another part of the scene/chapter/book was running long, and the writer thought that s/he should bulk this part up for balance. Or — and this motivates writers more often than any of us care to admit — s/he just liked the way it sounded and/or looked on the page.

Unfortunately, writers often like the look of certain phrases a little too much — and not necessarily, as most professional readers presume, because they simply love the sight of their own words on the page so much that they cannot bear to cut a single one of them, or because they are so arrogant about their talent that they believe no one will care if they reuse text or concepts, as many contest judges reluctantly come to believe.

I think there is something else going on here, benign in intent but inadvertently harmful to the texts in question. I illustrate the phenomenon with a parable.

Around this time last year — the tulips had just begun blooming, as I recall, in slightly inaccurate salute to St. George — I was puzzled into wakefulness by my significant other’s waving a soy latté and a freshly-baked pretzel under my nose. A new German bakery had 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 and hot dogs baked into the middle of pretzel dough 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, my tastes run much more to sleep. If I must be awake, a cup of tea is more my cup of tea. Even if it were not, obtaining mustard-laden foodstuffs would not be my first order of business before, say, five p.m. 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. He’s the type of person that will give an 87-year-old a teddy bear for her birthday, because she collected them when she was 50, still liked them at 69, and smiled wanly when he presented her with one while she was blowing out 86 candles. Never mind that every surface in her apartment is covered with the darned things: she liked getting one once, therefore she must enjoy the replication of the experience in perpetuity.

He’s presuming, in short, that she’s the kind of squidiot who enjoys books that explain basic concepts over and over to her. “Show me that generic dialogue one more time,” he must imagine her begging. “The part where everyone is so polite that the characters are indistinguishable from any other people on the planet.”

That being his view of humanity, I suppose I should not have been surprised that his response to my expressing surprise at the advent of a warm pretzel in my mouth was 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, but just try explaining that to a kindly soul in the clutches of a manipulative squid.

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 unusual 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, wasn’t the parallel instantly self-evident? 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.

Resist all sea creatures that tell you otherwise. Millicent and Mehitabel will thank you for it.

Again, I’m sensing that for some reason best known to yourselves, a hefty proportion of my audience would like to see a concrete example of the phenomenon — nay, perhaps several — so you may recognize it in its natural habitat. It comes in a variety of stripes. There’s the version in which favorite phrasing and/or sentence structure is repeated close together, often for rhythmic effect:

What did she want? Mostly, she knew what she didn’t want. Snow White had had it with dwarves. She had had it with princes. Heck, she had even had it with being a princess.

All she wanted, all she ever had wanted, was to be wanted. What was wrong with wanting that?

Or, as Millicent and Mehitabel would see it:

What did she want? Mostly, she knew what she didn’t want. Snow White had had it with dwarves. She had had it with princes. Heck, she had even had it with being a princess.

All she wanted, all she ever had wanted, was to be wanted. What was wrong with wanting that?

Just a touch term-repetitious, is it not? Ditto with the sentence structure. Either can induce garment-rippage, I’m sorry to report.

“I get that the writer wanted to establish a rhythm here,” Millicent mutters, “but what kind of a squidiot would have a vocabulary this small? I certainly don’t, and I doubt the readers of a book like this will, either.”

Don’t believe that an isolated and obviously purposeful repetitive pattern would rise to the level of clothing endangerment? Okay, what if the manuscript in question also exhibited another ubiquitous stripe of repetition, tactic reuse? 37 pages after our last example, this gem accosted our Millie’s weary peepers.

Rapine was so tired of indecision, tired of equivocation, tired of not being able to make up her mind. She didn’t really know what she wanted out of life, but she had reached some conclusions about what she didn’t want. She wanted to be free of the tower. She wanted to be free of her Guardian Witch. But mostly, she wanted to be free of the crushing weight of all that hair.

All she wanted, all she had wanted since she was sixteen, was a sharp pair of scissors. What was wrong with a girl’s wanting a new hairstyle? It’s not as though her future depended upon sporting two-story locks.

Starting to get to you a little, or is the squid still murmuring in your ear that this is just an example of a unique voice demonstrating its uniqueness at two different points in the text? Sorry, Squidbo, but repeating the same words and structures over either the course of a paragraph or the course of a book is the opposite of original: it’s a style choice Millicent and Mehitabel see every day. Imagine, then, the state of their clothing after encountering this gem 153 pages later.

“How dare you accost me?” the first little pig said quavering under the remains of his straw house. “What you want of me that could not have been equally well accomplished by knocking politely?”

The rather large and certainly evil wolf scratched his furry head. “Oh, what do any of us want? To be wanted, I suppose.” He flopped down on the scattered straw. “Man, I’m depressed.”

Piggie rooted his way through the debris to sit by the wolf’s side. “I hear you, Wolfie, but had it ever occurred to you that we might all feel that way? That it might be the fairy tale condition? That it might even be perfectly normal not to know what you want?”

“Ah,” the wolf said, thoughtfully buttering the top of the pig’s head, “but we all know what we don’t want. We don’t want hate. We don’t want war. And as God as my witness, I don’t ever want to be hungry again.”

Is that pretzel starting to taste a little stale? Or would you like another one? No? How about now?

What’s that huffing and puffing I hear out there? Is someone trying to get into my house, or do a few of you want to make a collective observation? “Oh, come on, Anne,” those of you who have not reread your manuscripts recently object, gnawing your fingernails, “this last one isn’t very similar to the first two. Certainly not garment-rendingly similar. I’ll give you that the level of word, phrase, and sentence structure repetition is a bit extreme in the first two examples, but presumably, they didn’t bug M & M too much to read on. Aren’t you picking nits here?”

It’s my job to pick nits, rereading-avoiders. The same might be said of Millicent and Mehitabel. Which is why I can assert with confidence: in a submission, that last passage might as well have been stamped in bright red ink: DITTO. Not only is the trope about knowing and not knowing one’s own desires conceptually redundant (and, let’s face it, not all that original in the first place), but the galloping three-part sentence structure gets a trifle dull to read. At minimum, it encourages the eye to skim.

Admittedly, though, that might not strike writers less eagle-eyed than your good selves. Let’s take a peek at another common species of structural repetition, to see what too-similar sentence structure too close together on a page can do to even a conscientious eye. (Yes, yes, I know: body parts seldom have their own independent motivations. The squid made me do it.)

This time, try our trick of backing up from the computer, then walking slowly toward the screen. As soon as the words come into focus, try reading the following as fast as you can.

“Oh, go away,” Beauty moaned, pulling a silken pillow over her head, “and take your pruning shears with you. Can’t you see I’m trying to sleep?”

“But I fought my way through the briars for you, and I climbed over a fence,” the prince protested. “A stone wall blocked my path, and a pit of snakes slowed me down. Brickbats the size of baseballs beat upon my head, and a dragon singed my toes. Can’t you even make the effort to roll over and look at me?”

Angrily, she complied. “Look, buddy, I don’t know what manners are like where you come from, but in these parts, it’s considered rude to barge into someone’s chamber and start slobbering all over them. Can’t you make any allowance for local mores?”

“But I swam the moat and scaled the castle wall! I toted that barge and lifted that bale. I got a little drunk and I landed in jail.” He clutched at his head. “No, that’s not right. Can’t you see I’m exhausted here?”

Beauty tossed a pillow at him. “Try taking a nap. That’s what I’m going to do.

Notice any visual patterns? All of those rhetorical questions beginning with can’t you, for instance — did your eye try to skip directly from one capital C to the next, without reading what came between? And what about the fact that almost every sentence the prince uttered (as opposed to his stab at rhetorical question-asking) was structured identically: I did X and I did Y? Didn’t all of those ands distract you?

Okay, maybe they didn’t; the squid may have been living with you a bit too long. (You know what Ben Franklin said about fish and houseguests, right? They both begin to stink after three days. And if you think that was a long way to go to make an analogy, well, you have a point, but you wouldn’t believe how often Millicent and Mehitabel encounter this kind of failed humor attempt. The squid is almost as fond of telling writers they are funny as it is of urging writers to explain the obvious.) You must admit, though, that so much structural repetition quickly became pretty boring to read.

And that goes double for concept repetition, even over the course of a fairly lengthy run of text. Or are you saying that you don’t wish I would stop harping on the squid?

The same holds true, believe it or not, with repetitive characterization, recycling the same descriptors or actions every time a particular character sets foot in a scene. Our squiddy friend often tries to convince aspiring writer’s that’s a good idea. Many’s the manuscript in which the hero’s sidekick utters something like, “Well, beats me!” every time the pair meets a challenge, or in which the heroine’s sister sneezes every time a window opens. That makes the character in question memorable, right?

Perhaps, but not necessarily in the way you might hope. As a tactic, this stripe of conceptual repetition seldom works on the page. Trust me, by this late date in literary history, any reasonably experienced Millie or Mehitabel will already have seen thousands of characters announce themselves through personal stock phrases and/or activity tics that this characterization will strike her as neither effective nor amusing.

So how will it strike them? As redundant. And, if the dialogue keeps throwing around a stock phrase, repetitive as well.

At the risk of seeming to beat a dead horse, cross the same river twice, and not learn anything from experience, may I add that the same principle applies to retreads of descriptions, reused metaphors and too-similar similes? I’m not just talking about rhapsodizing about every flower in a garden-centered romance as fragrant as a breath of spring or consistently referring to the protagonist’s nefarious boss’ face as frog-like. Although that is indeed annoying for the reader: if you’d like Millicent and Mehitabel to remain fully clothed, varying your descriptions is a good place to start.

No, I’m warning you against waxing poetic about the wolfish fierceness of Brent’s eye on page 147 if you have already treated the reader to observations on the almost lupine ferocity in his eyes on page 83 and its angry canine expressiveness on page 52. Especially when the reader was assured on page 10 that his eyes held an ferocious, almost feral expression reminiscent of a wolf, and the book opened with a lengthy description of an eye in close-up. A distinctly wolfy eye.

“Yes, yes,” Mehitabel sighs, glancing sorrowfully at her shredded blouse. What make those claw marks, some sort of werewolf? “We all get that you’re making a point here: the eye in question is darned wolf-like. I got that the first time you mentioned it. How much of a squidiot would I have to be still not to get it by the fifth time that parallel appears on the page?”

Good question, Hitty. Perhaps squidiocy knows no bounds.

Something else that knows no bounds: professional readers’ astonishment at how many submitters and contest entrants apparently don’t read their own writing closely enough to notice that the same points, phrasing, and metaphors crop up again and again. People who read for a living tend to have quite retentive memories, especially for text. It’s flatly flabbergasting to us that a good writer would not remember having come up with a spectacular phrase, description, or parallel.

But many good writers suffer from phrase amnesia, apparently. Or so the squid would lead us to believe.

If we can convince the big guy to squiggle out of the room for a moment, I’d like to talk to you seriously about the usual result of listening to his blandishments: rejection. Just as using the same (or very similar) phrasing in three paragraphs on page 1 will generally discourage Millicent from turning to page 2, repeating phrases, dialogue, sentence structures, or even imagery too often over a long stretch of text can also lead a manuscript to the same grisly fate.

And although I hate to be the one to break it to you, it sometimes does not take a great deal or very flagrant redundancy to send a submission skittering into the rejection pile. Remember, screeners have to cover a lot of manuscripts in a workday. Once a text has established a repetitive pattern, can you really blame Millie for deciding pretty quickly that the rest of the book will continue it?

Or, to drag one of our running analogies back into the narrative: if Millicent didn’t like the second pretzel of the day, she is likely to take it as given that she’s not going to like the 145th. She will seldom feel the need to gobble up pretzels 3-144 to confirm it.

Why? Because she’s not a squidiot. She can learn from experience — and remember what she has already read.

More on structural repetition follows on the morrow. In the meantime, keep up the good work!

“Wait, haven’t I read that someplace before?” — Millicent

old-fashioned writing desk in Victoria

Please join me in a moment of silence, campers. Today, I received one of the saddest pieces of news a person can hear from a writer friend: an extremely talented author of my acquaintance reported that her hard disk had crashed, doubtless from overwork. Not a syllable could be salvaged.

In response to those of you who just gasped audibly: yes, she was almost finished writing her next novel. She had circulated only the first four chapters to her critique group, so physical copies of that much still exist. Beyond that, however…

On a not entirely unrelated note, when was the last time you backed up your writing files? Is it recently enough that you could reconstitute your most recent revisions or new text from your unassisted memory?

If the answer to that second question is no, feel free to stop reading right now and make a back-up. At minimum, e-mail them to yourself, for heaven’s sake. I’m perfectly happy to wait, if it means that we can all sleep better tonight, confident that hours, days, weeks, and/or months of your writing time won’t just vanish in the proverbial puff of smoke.

Or ozone, as the case may be. As undoubtedly conducive to creative expression as computers are, the permanence of the results can be illusory. At times like this, I occasionally find myself longing for my father’s good old Olivetti typewriter, or even a simple Edwardian writing desk, like the one above. (Note, please, the requisite photo of a loved one and apparently equally requisite liquor tray.)

True, one had to hit the Olivetti’s keys so hard that when my parents first plopped me down in front of it at age ten to compose the term paper that everyone else in my class was writing by hand, I couldn’t actually force the q, z, p, or ? keys to hit the ribbon with sufficient force to create any impression upon paper. It took me so many hours to write the definitive history paper on the Bonus March that my mother seized the opportunity first to sketch my profile — she had never managed to convince me to sit still long enough before — then to sculpt my head in clay. Considering that my parents insisted that I write it in standard format for book manuscripts, I should probably count myself lucky that she didn’t also have time to cast the sculpture in bronze.

Yes, it was a touch on the tedious side to be forced to retype an entire page in order to rework a single sentence. On the bright side, though, to lose a year’s worth of one’s writing, an author actually had to misplace it physically.

(Were you distracted from the pithiness of that last bon mot by a mental image of a 5th grader using two hands to wrestle the z key into submission? That memory haunts me, too. My mother, however, asks me to inform you that she had faithfully typed my newspaper articles prior to that term paper, and that a little pro of my caliber shouldn’t have graduated from elementary school without learning to touch-type, anyway. And to be fair, she didn’t actually make me try it blindfolded until after I’d turned in the paper.)

Writing on a computer boasts at least one monumental advantage over the all hard copy, all the time method, however: it’s possible, and indeed easy, to check whether that wry observation that just occurred to you also struck you as the last word in style back when you were composing Chapter 3. And Chapter 7. And possibly Chapter 16.

Oh, you hadn’t noticed that you had repeated yourself? Trust me, Millicent the agency screener will.

Since aspiring writers so seldom catch their own phrasing reuse, I’m going to spend the next couple of days talking about that ever-popular birthmark of Frankenstein manuscripts everywhere, the sentence — or paragraph, or footnote, or scene — that turns up more than once in a manuscript. Or more than once in a chapter. Or — are you sitting down? — more than once in a page.

Already, I sense some of you rolling your eyes. “Yeah, right, Anne,” writers of 384-page texts huff, “I’m so uncreative, so myopic, so prone to writing only one paragraph per session that I would repeat entire sentences within just a few pages, yet Millicent remembers phrasing so well that she will catch me if I recycle a description from page 73 on page 312.”

Actually, she might — and I hate to be the one to break it to you, but otherwise quite good manuscripts reuse pet phrases all the time. You’ve probably noticed the tendency in the later works of well-established authors, in fact; as television comedy has led us all to expect, revisiting the same premises, jokes, and yes, even descriptions can elicit chortles of delighted recognition from an audience already familiar with one’s work. Heck, Oscar Wilde used to trot out the same laugh lines in play after play after play; he was monumentally good at branding.

For the overwhelming majority of writers, though, self-plagiarism does not constitute a promotional strategy so much as a simple lapse in memory. In the course of writing an entire book, it should perhaps not come as a surprise if the creative brain revisits a favorite turn of phrase, a trenchant observation on the human condition, of striking bit of imagery that strikes a writer as particularly, well, striking.

Hey, if it sounded good in the writer’s mind the first time, what’s to stop it from sounding good the second? Or the fourth? Or the forty-seventh?

Perfectly innocent and understandable, right? Well, perhaps not so much to our old pal Millicent — or her cousin Maury, the editorial assistant, or their aunt Mehitabel, the veteran contest judge. To someone who reads manuscripts for a living, such inadvertent redundancy can take on a more sinister aspect: to an uncharitable reader, even a single repetition of a pet phrase can smack of authorial laziness. Or as an aftereffect of that perennial bugbear, insufficient authorial re-reading.

Or, sacre bleu! a first indicator that what she holds in her ink-stained hands is a Frankenstein manuscript.

We’ve all seen Frankenstein manuscripts, right, even if we have not had the misfortune to write one? Many of us have at least a partial monster lurking in a bottom desk drawer or haunting our hard disks, books written over such a long period, in so many moods, at so many different levels of technical skill, and — come on, admit it — under the influence of so many and such varied favorite authors that it would take a small army of literary detectives years of close textual analysis to discern even an embryonic similarity between the authorial voices on pp. 10, 143, and 412.

In a first draft of a first novel, that’s virtually inevitable, right? Contrary to popular opinion amongst those who have never actually sat down in front of the ol’ Olivetti and cranked out a book, few writers are born with completely polished voices; it can take a great deal of trial and error to figure out how to sound original on the page. Then, too, it takes a good, long while to write a book, particularly the first time around: as Millicent would be the first to tell you, it’s not all that uncommon for the manuscript to betray significantly greater technical skill at its end than at its beginning. Or for the first chapter or two to read a great deal more like the end of the book than like the middle, because the writer went back and revised those opening pages after polishing off the draft.

Why is Millicent an expert on the two most common stripes of Frankenstein manuscript? Care to estimate how many first-time novelists and memoirists start querying and submitting their work practically the instant they polish off the first draft? Or the second?

Trust me, those of us who read for a living learn to catch the early warning signs. When Millicent sees a sentence, image, or observation from page 1 turn up on page 26, Frankenstein manuscript warning bells start chiming wildly in her head. From that point on, her already sharp critical sensors turn downright predatory, eager to swoop down upon more tell-tale signs that this is one of those texts whose author either kept changing his mind about the style he wished to embrace — or tone, or target audience, or book category — or just kept revising it so often that the narrative reads like a patchwork of different prose styles.

That does not mean, however, that self-plagiarism does not turn up quite frequently in non-Frankenstein manuscripts. How can an experienced reviser tell the difference? While the Frankenstein manuscript varies substantially as pages pass, the self-plagiarized text merely becomes redundant: passing scenery always described the same manner, for instance, or a clever line of dialogue repeated in Chapters 2, 5, and 24.

Nonfiction writing in general, and academic writing in particular, is notoriously prone to redundancy. So are book proposals. Again, that’s quite understandable. Once you’ve gotten into the habit of footnoting everything in the least questionable, it’s pretty easy to reuse a footnote, for instance, or to come to rely upon stock definitions instead of writing fresh ones every time.

Or, in a memoir, to tell the same anecdote more than once. As, indeed, people who like to talk about themselves tend to do in conversation. (Did I ever tell you about the time my mother wanted me to learn touch-typing as a fifth grader?)

Or, in any kind of writing, for a particular way of describing something to sound good. Many a writer simply finds a certain turn of phrase appealing and forgets that he’s used it before. Or just doesn’t notice, despite the fact that great way to catch this sort of redundancy is — wait for it — to read your manuscript IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD, in as few sittings as possible.

Oh, had I suggested that excellent pre-submission strategy before? Had I in fact mentioned it about once per week throughout Queryfest? How silly of me not to notice.

You may laugh, but actually, it’s quite easy for even a fairly conscientious reviser to miss instances of self-plagiarism on the page, especially if — and most revisers do this — she is reading through the manuscript over several days or even weeks. After all, you have to be gifted with an unusually strong memory for phraseology to stop short in the middle of Chapter 15 and shout, “Hey, I’ve seen that image before, and it was on page 36, paragraph four!”

I don’t mean to frighten you (or do I?), but professional readers frequently have astonishingly accurate memories for text. Millicent might not be able to tell you precisely where she’s seen that Ch. 15 image before, but she will almost certainly have the dim impression that it has appeared earlier in the manuscript. I can positively guarantee you, though, that if the first instance of its use pops up on p. 36, and the second on p. 42, she will most assuredly spot the second as redundant.

She should: professional readers are trained for that.

For a self-editing writer, it can be harder to catch — and harder still to remember if you actually used that sentence elsewhere, or merely thought about it. As inveterate commenter and long-time FAAB (Friend of Author! Author! blog) Dave so rightly pointed out the last time we discussed this phenomenon, most good writers spend quite a bit of time mulling over any given scene in a book, not to mention revising it later on; it’s not uncommon, therefore, to have a positive welter of mental associations about the evolution of the aforementioned pp. 36 and 42. Add to that the fact that a reader’s eye will tend to pass over smoothly-written text pretty quickly, especially if it’s a scene he’s read before, and reading through one’s own manuscript by definition entails re-reading, and can we really be surprised when repeated phrasing passes unnoticed under the reviser’s gaze?

Even when the repeated phraseology or image does jump out at the rereading reviser (try saying that four times fast!), it won’t necessarily be for a negative reason. It’s not unheard-of for writers to prefer repeating bits of their own work: those turns of phrase are his favorites for a reason, presumably. They linger in his ears pleasingly when he reads them out loud; they strike him as some of his best writing on the page. If pressed, he might admit to wanting to see one of them chiseled on his gravestone.

Yes, those of you who have been jumping up and down with your hands raised for the last couple of paragraphs? “I know what this writer should do!” survivors of English 101 burble excitedly. “It was for precisely this kind of writer’s benefit that Dorothy Parker started urging all of us to kill your darlings. If he loves those phrases so much, they should be the first axed, right?”

Aspiring writers and the English composition teachers who love them just love this piece of revision advice, eager burblers, but if you want to hear anyone who reads for a living choke on the coffee that’s never far from her elbow (hey, you try staying awake uncaffeinated through the fiftieth YA paranormal novel you’ve seen this week), feel free to trot out this most misunderstood piece of writing advice. We’ve too often seen the slash-and-burn effects of this canonical advice in action. Indeed, going through one’s own manuscript, relentlessly slaughtering any writing that strikes one as excellent is a pretty good prescription for creating a Frankenstein manuscript, not healing one.

And it’s not even what Aunt Dorothy was advising writers to do. She wasn’t talking about ruthlessly excising every piece of writing you like and leaving the stuff you like less, people: she was suggesting that you consider taking a critical look at even your favorite sentences and paragraphs. All too often, inexperienced self-editors will simply skip over their pet bits.

That being said, kill your darlings (selectively!) is excellent advice for habitual self-plagiarists. Perhaps a writer need not sacrifice the first of the litter, but the second through seventeenth should definitely go.

That’s especially good strategy if the phrasing repetition was deliberate in the first place. If a line was clever once, many a darling-coddling writer thinks, the reader will find it so the second time — and the fifth, and the forty-seventh. Deliberate redundancy is particularly common with humor: since situation comedies tend to rely upon repetition of catch phrases, many aspiring writers believe that the mere fact of repetition will render a line funny.

On the page, it seldom works. Sorry to be the one to break it to you sitcom lovers, but it quickly becomes tedious on the stage and screen as well.

Don’t believe me? Consider this: as those of us who live in caucus states know to our perennial (or at least quadrennial) sorrow, nowhere is the practice of self-plagiarism more prevalent than in the garden-variety political speech. Not only from speech to speech — oh, you thought your favorite candidate gave a speech only once, then threw it away? She has fourteen more campaign stops today! — but throughout a political season. Heck, as anyone who has listened closely to two consecutive State of the Union addresses can tell you, they often contain the same phrases from year to year No matter how fiercely THE WEST WING tried to promote the notion of presidential speechwriters as ultra-creative writers, if you look at speeches given by the same politician over time, chances are that you’ll find self-plagiarism of epidemic proportions.

There’s a good narrative reason for that, of course: the repetition of an idea makes it memorable. The ideas — and usually even the actual phrases — of the beginning of a political speech invariably recur throughout, to drive the point home.

Doubt that? Okay, answer this: do you think people would remember that the Rev. Dr. Martin Luther King, Jr. had a dream if he had said it only once in his famous March on Washington speech?

On paper, phrase repetition is often problematic, but in and of itself, repetition does not necessarily equal self-plagiarism. On paper, repetition can seem very cool to the writer, as a means of creating a galloping rhythm. On paper, phrase repetition can be used for emphasis (as I have just done in this very paragraph, much to Millicent’s chagrin).

We all know how phrase repetition can create a sense of momentum in writing, don’t we? Take, for instance, the ending of the St. Crispin’s Day speech from HENRY V:

If we are mark’d to die, we are enow
To do our country loss; and if to live,
The fewer men, the greater share of honour.
God’s will! I pray thee, wish not one man more.
By Jove, I am not covetous for gold,
Nor care I who doth feed upon my cost;
It yearns me not if men my garments wear;
Such outward things dwell not in my desires.
But if it be a sin to covet honour,
I am the most offending soul alive.
No, faith, my coz, wish not a man from England.
God’s peace! I would not lose so great an honour
As one man more methinks would share from me
For the best hope I have. O, do not wish one more!
Rather proclaim it, Westmoreland, through my host,
That he which hath no stomach to this fight,
Let him depart; his passport shall be made,
And crowns for convoy put into his purse;
We would not die in that man’s company
That fears his fellowship to die with us.
This day is call’d the feast of Crispian.
He that outlives this day, and comes safe home,
Will stand a tip-toe when this day is nam’d,
And rouse him at the name of Crispian.
He that shall live this day, and see old age,
Will yearly on the vigil feast his neighbours,
And say ‘To-morrow is Saint Crispian.’
Then will he strip his sleeve and show his scars,
And say ‘These wounds I had on Crispian’s day.’
Old men forget; yet all shall be forgot,
But he’ll remember, with advantages,
What feats he did that day. Then shall our names,
Familiar in his mouth as household words-
Harry the King, Bedford and Exeter,
Warwick and Talbot, Salisbury and Gloucester-
Be in their flowing cups freshly rememb’red.
This story shall the good man teach his son;
And Crispin Crispian shall ne’er go by,
From this day to the ending of the world,
But we in it shall be remembered-
We few, we happy few, we band of brothers;
For he to-day that sheds his blood with me
Shall be my brother; be he ne’er so vile,
This day shall gentle his condition;
And gentlemen in England now-a-bed
Shall think themselves accurs’d they were not here,
And hold their manhoods cheap whiles any speaks
That fought with us upon Saint Crispin’s day.

Now that’s a political speech, caucus-goers: great spoken out loud, but Millicent-enragingly repetitious in print.

Did that last observation catch you by surprise? Yes, this particular speech happened to fall from an exceedingly talented pen, but unfortunately, a lot of poor writers favor this rhythmic device, too. Because it is ubiquitous, it tends to be a rather risky trick to try to pull off in a short piece, such as a synopsis, or in the first few pages of a manuscript submitted for a contest or as part of a query packet.

Please tell me that you aren’t even considering repetitive phrasing in your query. Or that the first line of your synopsis is the first line of your novel. Please. Please. Please?

Why is it dangerous? Well, to professional eyes, trained to search for the repetition of a single verb within a paragraph as evidence of boring writing, we few, we happy few will not necessarily jump off the page for the beauty of its rhythm. In an ultra-quick reading (as virtually all professional readings are, lest we forget), it may be mistaken for an incomplete edit: you meant to change we few to we happy few,” but you forgot to delete the words you did not want, Bill.

A pop quiz to see if you’ve been paying attention: why would a savvy submitter not want to convey the impression of an incomplete editing job? That’s right: because that’s the birthmark of the dreaded Frankenstein manuscript, the fish that Millicent is only too happy to throw back into the sea.

Remember, too, that it may not take many instances of repetition for Millicent to draw this conclusion. The writer may not realize that she has reused a particularly spectacular image from Ch. 1 in Ch. 3, but believe me, if there is repetition, professional readers will catch it.

And no, I don’t care how many times I have to repeat that point. It’s vital for your happiness as a writer to understand that the pros are trained to catch redundancy. Editors in particular are notorious for remembering entire pages verbatim.

It’s a specialized brain function, sharpened by use. When I was teaching at the University of Washington, I was known for noticing when term papers resubmitted in subsequent quarters, even though I read literally hundreds of papers per term. I would even frequently remember who wrote the original. As you may well imagine, I quickly acquired a reputation amongst the fraternities and sororities who kept files of A term papers for their members to, ahem, borrow.

Which is why, in case those of you who have had the good fortune/petrifying experience of receiving professional feedback, paraphrasing what you’ve said earlier in the manuscript tends to be significantly less frowned-upon in editorial circles than outright literal repetition. While very similar passages may earn you an ill-humored rebuke from Millicent, Maury, or Mehitabel, generalized repetition usually will not knock you out of consideration if the recurring bits occur far apart, such as at the beginning and end of a book.

In a shorter piece, however — such as, say, those first 50 pages of your novel that nice agent asked you to send for consideration, or the 15 pages plus synopsis — it certainly can cost you. Repetition sticks in the professional reader’s craw, nagging at her psyche like a pebble in a shoe. It’s in your best interest to do it as little as possible.

“Now wait a minute,” I hear some of you out there grumbling. “You told us just a few minutes ago that Oscar Wilde repeated the same quips in one play after another. It became his trademark, in fact. So why should I be punished for using a single particularly sterling line 150 pages apart in my novel?”

You have a point, of course, grumblers. The next time you trot out this argument, you might bolster it by mentioning that Aaron Sorkin reused not only lines and speeches from SPORTS NIGHTin THE WEST WING, but entire plot lines and basic characters.

Tell you what: after you make it big, I give you permission to establish a trademark phrase and use it as often as you like. Until you do — as I sincerely hope you will — all I can do is tell you that phrasing repetition tends to annoy agents, editors, and contest judges.

Seriously, I will repeat it all night. Don’t tempt me.

“But Anne,” I hear the well-read among you protest, and with good reason, “many of the classic novelists I studied in my English 101 class used phrasing repetition to create invocatory rhythms. They also repeated dialogue, because, as you like to point out early and often, real-life dialogue is hugely redundant. If it’s good enough for those long-ago greats, why isn’t it good enough for me — or for Millicent?”

One reason leaps to mind: you’re not writing on a typewriter, are you? You’re probably composing your book in a word processing program. Not only can you spell- and grammar-check with an ease that would have made the late, great Ms. Parker gasp with envy — with the touch of a button or two, you can search your own writing to see if you have used a phrase before.

You think Millicent is unaware of that capacity?

You are perfectly right, though, close readers: all writers of book-length works have repeated themselves at one time or another. If a simile struck us as the height of cleverness last week, chances are good that we will like it next week as well. Each time we use it, it may seem fresh to us. These little forays into self-indulgence are so common, in fact, that literary critics have a name for them: tropes.

F. Scott Fitzgerald was a notorious troper in his short stories. My least favorite: a thwarted heroine’s sobbing out (usually with her face hidden by her smartly-bobbed hair), “I’m so beautiful – why can’t I be happy?” immediately before she does something self-immolatingly stupid to remove herself from the possibility of marrying the story’s protagonist occurs at least four times throughout his collected works.

It may well pop up more; I merely stopped counting after four. That was, not entirely coincidentally, when I threw the book across the room.

Why Uncle Scott found that particular line so very attractive in a pretty woman’s mouth remains a mystery eternal — it’s hard to believe he ever actually heard a sane female utter it, even in jest. But he did, evidently, and now it’s stuck to his name for all eternity.

Learn from his unhappy fate, I beg of you: no matter how marvelous a line of text is, use it only once.

This will require careful reading to enforce. Your garden-variety self-plagiarism is less obvious to the untrained eye than ol’ Scott’s outright dialogue reuse. Spread out over an entire text — or, as it often appears in the case of successful authors of series, once per book — it may be fairly innocuous, the kind of thing that might only bug someone who read manuscripts for a living.

Like, say, Millicent or yours truly. Do not underestimate, for your own sake, our memories. Unbound manuscripts do not typically survive intact being flung across the room.

E.F. Benson, author of two delightful series, the Lucia books and the Dodo books, was evidently extraordinarily fond of using Arctic analogies for one person suddenly grown cold to another. To gather but a small nosegay of examples:

“It was as if an iceberg had spoken,”

“It was as if the North Pole had spoken,”

“icebergs passing in the North Sea” must speak to one another as two characters had, and

“Mapp turned to ice.”

See the problem? As a Benson enthusiast, I was able to come up with four of them without even pulling any of his books off the shelf These repetitions, deliberate or not, stick with the reader, just as surely as repeated phrases stick with the audience of a political speech.

That doesn’t mean it is a bad analogy, of course, if not a startlingly original one. Like any other literary device, however, time it’s used, it becomes less effective.

Yet again, we see an awfully good reason to read your entire book (or requested chapters, or contest submission) out loud before you submit it — and not just as a cursory mumble-through, either. Believe it or not, just as dialogue that seemed fine on the page can suddenly seem stilted when spoken aloud, phrases, sentences, and images that your eye might not catch as repetitious are often quite obvious to the ear.

Another good reason to read aloud: to make sure that each of your major characters speaks in a different cadence. It’s substantially easier for the reader to follow who is speaking when that way.

Don’t stand there and tell me that all of Aaron Sorkin’s and David Mamet’s characters speak in identical cadences, as though they all shared one vast collective mind. To my sensitive antennae, nothing is more potentially migraine-inducing than an evening of the percussive prose of Mamet. (Unless it’s a chamber concert of Stephen Sondheim’s greatest hits.)

As if the prospect of annoying your humble correspondent were not sufficient incentive to eschew identical dialogue patterns for every character, remember what I said back in Queryfest about the dangers of those new to the biz assuming that what the already-established have done, they may get away with as well?

Uh-huh. In a first manuscript, it would be considered poor craft to have every character in the book sound the same. Not to mention poor character development. While I’m on the subject, keep an ear out in your read-through for lines of dialogue that cannot be said aloud in a single breath without passing out — they tend to pull professional readers out of the story.

Why, you shout breathlessly? Well, in real life, listeners tend to interrupt speakers when the latter pause for — wait for it — breath. Cramming too many syllables into an uninterrupted speech usually doesn’t ring true on the page. Allow your characters to breathe occasionally, and your dialogue will seem more realistic.

I’d give you a concrete example, but I meant to post a short blog today, and here I have gone long again. Which begs the question: I’m so beautiful — why can’t I be happy?

There, now at least one real, live human female has said it; don’t say I never did anything for you, Uncle Scott. Keep up the good work!

Queryfest, part XXII: if it be the winter of Millicent’s discontent, can spring be far behind?

Before I fling all of us headlong into yet another examination of what strategies do and do not work well on the query page — that’s why you tuned in tonight, right? — I’d like to take a moment to reiterate some advice I gave all of you eager New Year’s resolution queriers a couple of weeks back. Or, at least that hefty chunk of the January querying community that either lives in the United States, is planning to approach literary agents based in the United States, or both: no matter how tempting it may be to send out a query via e-mail over this long Martin Luther King, Jr., Day weekend, please, I implore you, resist the temptation.

“And why should I even consider taking that advice?” those of you joining us mid-Queryfest demand. “At the risk of pointing out the obvious, I have more spare time in the course of a three-day weekend than during the normal two-day kind. Why shouldn’t I hit SEND while I have the leisure to do it?”

Already, a forest of hands sprouts out there in the ether. I love how closely my readers pay attention. Go ahead and help me fill ‘em in, Queryfest faithful: just as our old pal and nemesis, Millicent the agency screener, is predictably greeted by many, many more queries on any given day in January, as opposed to any other month of the year, she also finds her inbox stuffed with more e-queries than usual on Mondays than any other weekday, for precisely the reason the newcomers just cited — aspiring writers tend to have more time to send them over the weekend. As a direct result, not only does she typically have more work on Mondays. And as she, like so many people bent upon enjoying their weekends, is often a mite grumpier that day as well.

With what result? Chant it with me, Queryfesters: the rejection rate tends to be higher on Monday mornings than, say, Thursday afternoons. Our Millie simply has a taller stack of queries to work through, without any extra time in which to do it. Fortunately for her sanity, while it’s pretty difficult to compress the amount of time it takes her to process a paper query — about 30 seconds, on average, or less if the querier is helpful enough to insult her intelligence with a hard-selling statement like you’ll be sorry if you pass this one up! or this is the next DA VINCI CODE! — it is spectacularly easy to render the consideration and rejection of an e-mailed query a matter of just a few seconds. Especially now that so many agencies have adopted the to-a-writer’s-eye appallingly rude practice of simply not responding to a query if the answer is no.

Not sure how to speed up the consideration process? Okay, I ask you: how much time would it take you to twitch the finger nearest the DELETE key in its general direction? And how much more likely would you be to do it on a morning when your bleary eyes fell upon 722 queries in your inbox than the happy day when it contained only 314?

So, at the risk of repeating myself, I ask you: do you honestly want your query to land on her computer screen on a Monday morning?

Sad to say, though, it could arrive at a worse time: the Tuesday following a three-day weekend. Due to the aforementioned tension between aspiring writers’ free time and the rhythm of her work week, we may also confidently predict that she will be inundated with still more e-queries then than she would on an ordinary Monday, right? Just after Labor Day, for instance, or Memorial Day, it requires very little imagination to picture just how itchy her fingertips are going to be for that DELETE key.

It thus follows as night the day, then, that when a three-day weekend happens to fall in January, the dreaded month when a good half of the aspiring writers in North America who intend to query this year will be hitting the SEND key if they are going to take the plunge at all, Millicent’s e-mail coffers and mail bag will be as full as she is ever likely to see them. Need I devote more screen space to the predictable effect upon the rejection rate the following Tuesday?

I’m guessing not, with a group as savvy as this. Hint, hint, wink, wink, say no more, as the immortal Eric Idle used to say.

Speaking of Millicent’s a.m. stress levels, mine hit a peak this morning, triggered by the gentle snowfall pictured above. Not that I am anti-snow in general; indeed, I typically find the first — and sometimes only — snow of the year quite exciting. It snowed a grand total of thrice in the Napa Valley in the course of my childhood; it was something of an event. I didn’t actually see large quantities wafting down from a grumpy sky until my junior year of high school, in the course of an ill-fated let’s-show-the-kids-how-Congress-works field trip during which I got pushed sideways over a chair because I was the only student participant who believed Social Security was worth saving. (Hey, it was the 80s. And my sprained ankle is fine now, thanks.)

So I was darned excited to look up from my desk this morning to see great, big white flakes hurtling at my window. I can only plead the fact that I happened to be editing a manuscript at the time as an excuse for what happened next.

My SO came tripping into my studio, bearing a hot cup of tea. “Have you looked outside? It’s a winter wonderland!”

“I should think it would be obvious,” I said, gratefully accepting the mug, “from the fact that I am sitting right next to a window that I might have observed the snow. And couldn’t you manage to come up with a less hackneyed way to describe it than winter wonderland?”

And that, dear friends, is what reading even quite good manuscripts for a living will do to an otherwise charming person’s manners: I am certainly not the only professional reader who automatically revises everyday speech in an attempt to raise its literary value. Imagine how much touchier I would be if I had Millicent’s job on a Monday morning.

Had I mentioned that you might want to think twice about hitting that SEND button this weekend? Wouldn’t your time be better spent building a snowman?

To be fair to both Millicent and myself, stock phrases, clichés, and stereotypes do abound in your garden-variety query, synopsis, and manuscript submission. So common are they that one might well conclude that there’s an exceptionally industrious writing teacher out there, working day and night to inculcate the pernicious notion that the highest goal of literary endeavor consists in stuffing narrative prose to the gills with the most repetitive, prosaic elements of everyday speech.

In a sense, that is sometimes the case: as many, many writers can attest, the continental U.S. has not suffered in the past half-century from a shortage of English teachers bent upon convincing their students that good writing should flow as easily as natural speech. The most visible results of this endeavor have been, as we have discussed before, a superabundance of chatty first-person narrators given to telling, rather than showing, the stories through which they lead their readers, a general disregard of subject/object agreement (presumably because the proper everyone and his Uncle George contracted rabies strikes the ear less gracefully than the pervasive but incorrect everyone and their Uncle George contracted rabies), and, most irritating of all to the professional reader corps, texts peppered with the kind of catchphrases and polite phrases that show up in conversation.

Why is that last one problematic? Well, think about it: by definition, the stock responses to common stimuli (pleased to meet you, have a nice day, I’m so sorry for your loss), standard phrases exchanged in mundane interactions (sign right here, have a nice day, may I help you?), and mere polite murmurings (after you, excuse me, you’re welcome) are generic; their strength — and their social safety — lies in the very fact that people spout these statements all the time. As such, they do not have personal content: although Madge may genuinely mean it when she tells Bernice to have a nice day, chances are that when she said precisely the same thing to Herbert, Bruce, Ambrose, and Melchior over the course of the following two hours, she did not utter it with the same intent. It’s just something people say.

We’re all aware of that conversationally, right? So why does it frequently come as a surprise to aspiring writers that because such phrases are so very common, they lack the power either to convey characterization, illuminate relationships, or add complexity to an interaction?

Not sure why? Okay, let’s assume that Madge’s co-worker, the otherwise estimable Ima, decides to immortalize their workplace’s everyday speech on the novel or memoir page. Eager to depict darling Madge as the courteous, considerate lady that she is, conscientious Ima makes darned sure to include each and every stranger-charming statement. Unfortunately, the result is not particularly likely to charm a reader, much less one as page-weary as Millicent. Take a gander at a not-atypical opening scene:

“Excuse me.” The tall, handsome stranger handed her his paperwork almost apologetically. “I was told to fill out these forms and bring them to this window.”

“Hello.” Deliberately, Madge finished reorganizing the paper clips in their magnetic holder before glancing at the stack. “How are you this fine Monday morning?”

“Oh, fine. Is this the right window for these?”

“Yes, of course. Hectic day?”

He covered his watch with his sleeve. “Oh, yes. We’ve been swamped.”

“Well, it’s always like that after a holiday.” She stamped the top three forms. “We’ve been swamped, too. Did you have a nice long weekend?”

“Yes. You?”

“It was fine. Didn’t they give you a B/49-J form?”

“Oh, yes, it’s right here. I’m in a bit of a hurry.”

“I’m doing my best, sir. May I see some I.D., please?”

“Okay.” Clearly, the man was accustomed to his smile’s having greater effect on functionaries. He could have posed for a toothpaste ad. “Here it is.”

“Thanks. Just a moment.” She tapped on her computer, frowning. “We don’t seem to have any record of your existence, Mr. Swain.”

“What do you mean?”

She caught just a glimpse of the tentacle wiping the perspiration from his brow. “I’m sure there’s just been a mix-up in the database. You just hang on for a moment, and I’m sure we can get this cleared up in a jiffy.”

Pretty stultifying until that last bit, wasn’t it? Even less excusable from Millicent’s perspective, the narrative didn’t give the slightest indication until that last paragraph that this is the opening for a fantasy. While this sort of bait-and-switch between the ordinary and the unexpected is a classic short story plotting strategy — not to mention the dominant storytelling technique of the old Twilight Zone series, which continues to influence fantasy writers to this day — the speed with which the sheer volume of submissions forces Millicent to read renders the mundanity of this dialogue dangerous. She would have to read all the way to the end of this exchange to see that it’s not just the 274th exchange echoing everyday speech that she’s read this week.

Lest anyone be tempted to dismiss her tendency to lump this interaction with all the others (including issuing the same cry of, “Next!”), note, please, just how little those polite, ordinary speeches reveal about either of the characters shown or the situation. This dialogue could take place in any customer service environment: in a bank, at the DMV, at the teleport terminal between Earth and the planet Targ. Because these statements are generic, they can’t possibly tell the reader anything specific. And while the writer and his writing group might well find that keep-‘em-guessing ambiguity hilarious, Millicent’s simply seen it too often to play along for very many lines.

Does the chorus of martyred sighs out there indicate that some of you Queryfesters are tiring of playing along as well? “Okay, I get it, Anne,” those of you impatient to get queries out the door moan, “dialogue on the page needs to be something better than just a transcript of everyday speech. Lesson learned. But why in the name of the seven purple moons of Targ did you decide to stop dead in the middle of a series on querying to tell us about this Millicent-irritant now?”

An excellent question, impatient moaners, and one that richly deserves a direct answer. Try this one on for size: since Millicent, like most professional readers, has an extremely low cliché tolerance, it’s poor strategy to include even one stock phrase in a query letter.

And yes, in response to what half of you just thought very loudly indeed (the mind acoustics are phenomenal here on Targ), she sees cliché-filled queries all the time. See for yourself — and, as always, if you are having difficulties reading the individual words, try holding down the COMMAND key and pressing + several times to enlarge the image.

Oh, you thought I was going to use a real reader’s query to illustrate this particular faux pas? That would have been a bit on the cruel side, wouldn’t it? Besides, given a readership as savvy, fascinating, and creative-minded as this one, where could I possibly have found a query as cliché-ridden as this one?

Actually, although it pains me to say it, about a quarter of the volunteer queriers submitted letters containing one or more of Ima’s hackneyed phrases; although our fictional exemplar here is inordinately fond of them, you’d be astonished at how many real queries contain roughly this ratio of stock phrase to original writing. Odd, isn’t it, considering that as every syllable an aspiring writer sends an agency is a writing sample (you hadn’t been thinking of your query in those terms, had you?), that so many queriers would rush to make themselves sound exactly like everyone else?

Incidentally, about one in six of the queries I received from would-be volunteers also replicated a particular phrase in Ima’s letter — and that surprised me, because this all-too-common statement contains two elements that I frequently and vehemently urge Author! Author! readers not to include in their queries at all. Did you catch it?

No? Would it help if I mentioned that at most agencies, one of the deadly elements would render this query self-rejecting?

If your hand shot into the air at that last hint because you wanted to shout, “I know! I know! It’s because Ima said in the first paragraph that every reader currently walking the planet Earth — if not the planet Targ — would be interested in this book! From Millicent’s perspective, that’s a completely absurd claim, as no book appeals to every reader,” give yourself a pat on the back, but not a gold star. Yes, this particular (and mysteriously popular) assertion does tend to irritate most Millicents (especially on the Tuesday after a long weekend, when she will see many iterations of it), but it’s not always an instant-rejection offense.

No, were that boast the only faux pas here, Millicent probably would have kept reading until after the third or fourth unoriginal phrase. I seriously doubt, though, whether she would have made it past Ima’s first sentence. Any guesses why?

If your eye immediately pounced upon the phrase complete at 137,000 words, feel free to ransack the gold star cabinet. Why is this phrase — lifted directly from some maddeningly pervasive template floating around out there on the Internet, I gather — a rejection-trigger? It’s not, believe it or not, the fact that so many aspiring writers have been shoehorning it into their queries in recent years that it has effectively become a cliché, as far as Millicent is concerned. The real problem with it that it effectively bellows at Millicent, “Hey, lady — this querier does not know thing one about how books are sold in the U.S.”

An unfairly sweeping conclusion? Perhaps, but let’s don Millicent’s glasses and whip out her text-dissecting scalpel to figure out why she might leap at it. In the first place, this statement includes unnecessary information. If the book being queried is fiction, people in agencies will assume that the manuscript is complete, for the exceedingly simple reason that it would be impossible for a first-time, non-celebrity writer to sell an incomplete first novel. Fiction is sold on a completed manuscript, period.

Nonfiction is typically sold on a book proposal, not a full manuscript, so were Ima’s book a memoir, including the information mentioning that the manuscript is complete would not necessarily be a selling point, either. The only exception: the relatively rare nonfiction-representing agency that states point-blank in its submission requirements that it will consider a first memoir only if the writer has already completed a draft of it.

Why might they harbor that preference? Ask any memoirist: writing truthfully and insightfully about one’s own life is hard, doubly so if the life in question has been at all traumatic. The brain and the body often doesn’t make a huge distinction between living through something difficult and reliving it vividly enough to write about it explicitly and well. It’s not at all unusual for even an exceptionally talented writer to become heavily depressed, or even physically ill, in the course of fulfilling a contract for a memoir.

Since most of pulling together a proposal involves writing about the book’s subject matter, rather than writing the story from within — telling what happened, as opposed to showing it clearly enough that the reader feels as though she’s walking around in the narrator’s skin — many first-time memoirists worry, and rightly, that they might not have the emotional fortitude to finish the book. Others are stunned to discover that after months or years of effort aimed at landing an agent and selling the book concept to a publisher, they simply cannot bring themselves to complete it. Or, if they do, they balk at exposing their innermost secrets to the world.

There’s absolutely no shame in any of that — second thoughts are natural in this instance. However, an agent who has seen a pet project cancelled at the last minute because a client could not finish the book he was contracted to deliver might well become wary about running into the same problem in future. So while agencies that handle a lot of memoir tend to get inured to this sort of disappointment, it’s not at all unheard-of for a newly-burned agent or agency to establish a full manuscript-only policy.

Most of the time, though, that’s not the expectation; publishers buy memoirs all the time based solely upon a proposal packet and a single chapter. But they don’t, as a rule, buy incomplete fiction.

So when Ima makes a point of saying in her query — and right off the bat, too — that her manuscript is complete, probably merely because she saw an example online that used that phrase, she is effectively making a virtue of having lived up to the publishing industry’s minimum expectation of fiction writers. To Millicent’s mind, that’s just not something anyone familiar with how fiction is actually sold in this country would do.

But as much as most agents prefer to take on new clients who have done their homework about how publishing does and does not work, professional naïveté all by itself is seldom considered an instant-rejection offense. That unusually high word count, however, often is. In fact, many Millicents are explicitly trained to reject a query that mentions the manuscript it is promoting exceeds 100,000 words.

Why draw the line there? Cost, mostly. Although the average manuscript shrinks in length by about 2/3rds in the transition to print, it’s just far more expensive to print a long book than a shorter one. Since the publication costs rise astronomically at about 125,000 words — different binding is necessary, and trade paper binding is more problematic — and it’s so common for first-time authors to be asked to revise their books and add pages prior to publication, they like to leave themselves some wiggle room.

So pervasive is the prejudice against first books over 100,000 words (i.e., 400 pages in Times New Roman) that it’s not unheard-of for agents to tell clients with books pushing the upper limit simply to leave the word count off the title page. (If you were not aware that the word count is typically included on a professional title page, or that a title page is necessary for a manuscript, run, don’t walk to the HOW TO FORMAT A TITLE PAGE category on the archive list at right.)

Did some of you do a double-take at the 100,000 words = 400 pages equation? “But Anne,” Ima cries, justifiably upset, “my manuscript is nowhere near 400 pages. But it is about 137,000 words. What gives?”

I’m guessing that you have been using actual word count, Ima, not estimated. For short stories and articles, it’s appropriate to report what Word says your word count is, but for books, that’s not historically how it has been figured. And unfortunately for your query, Millicent will just assume that any word count that ends in a zero is an estimate.

Actually, she’s likely to leap to that conclusion, anyway, because that’s how word count for books has historically been figured: 250 x # of pages for Times New Roman, 200 x # of pages for Courier. Yes, yes, I know, Ima: the resultant figure will bear almost no resemblance to the actual word count. That’s fine — expected, even.

But that expectation does carry some pretty heavy implications for using the stock phrase complete at X words, necessarily. Specifically, when Millicent spots your query’s assertion that your manuscript is 137,000 words, she — and a potential acquiring editor — will just assume that your novel is 548 pages long. (137,000 divided by 250.) And that, as we discussed above, would place it well beyond what her boss, the agent of your dreams, could hope to sell as a first book in the current fiction market.

“But Anne,” Ima protests, tears in her eyes, “I see plenty of fantasy novels that long in the bookstore. Because, yes, I am one of those great-hearted and sensible aspiring writers who realizes that if I expect bookstores to help promote my novel when it comes out, I should be supporting them now by buying books from them.”

While I approve of your philosophy, Ima — and would even upgrade it by pointing out that an aspiring writer who does not regularly buy recently-released first books in her own book category is shooting her own long-term best interests in the metaphorical foot — what you probably have in mind are novels by established authors. What a writer with an already-identified readership demonstrably willing to buy his books can get away with often differs radically from what a first-time author can hope to sneak past Millicent. And because market conditions change, it’s certainly different from what a first-time author might have been able to sell five years ago.

It’s a truism, to be sure, but people in the industry repeat it for a reason: in order to get discovered, a new writer’s work doesn’t merely have to be as good as what is already on the shelves; typically, it needs to be better.

Now, an aspiring writer can find that truth discouraging — apparently I’ve depressed poor Ima into too deep a stupor to keep formulating questions — or she can choose to find it empowering. Yes, that stock phrase gleaned from an online query template led Ima down the path of certain rejection, but honestly, can you blame Millicent and her ilk for wanting to reject queries crammed with prefab, one-size-fits-all phrasing?

Be honest, now: if you were an agency screener, wouldn’t you prefer to reward queriers who made the effort to sound like themselves?

Of course, it’s quite a bit more work to come up with original phrasing for what most aspiring writers regard, let’s face it, as merely an annoying hoop through which they have to jump in order to get agents to read their manuscripts. It’s more than that, though — to Millicent, it’s your first opportunity to wow her with the originality of your voice, the startling uniqueness of your story or argument, and, yes, your professional grasp of the realities of publishing.

Listen: every piece of writing you send to an agency is yet another opportunity to demonstrate that you can write. Millicent wants to see your literary voice on the page, not other people’s phrasing, and certainly not a pale echo of what anybody random person on the street might say. (I’m looking at you, Madge.) Read your query carefully to make sure that you sound like you and nobody else — and that the story you are telling or the argument you are making doesn’t read like anybody else’s, either.

A tall order? Most assuredly. But isn’t this what a good writer wants, people in the publishing industry taking her writing seriously enough to pay close attention to how she chooses to arrange words on the page?

Ponder that, please, until next time, when I shall once again be analyzing a reader’s actual query. Have the confidence to eschew those templates, everybody, and keep up the good work!

Bringing those unbelievable stories to life on the page, or, well-mannered camel seeks wiser man

It’s Christmas Day, campers, but my tree has gone dark: the electricity has been out for the last two hours. The local authorities claim that gigantic boom we all heard around noon resulted from a frantic windstorm’s having taken out a transformer. A less literary-minded analyst might take this story at face value. You can’t fool me, though. This is obviously Phase I of the Grinch’s most recent plan to steal Christmas.

Either that, or the Great Celestial Plotmaster(s) have been reading a lot of classic mystery lately. The day has all the hallmarks of the genre: while stoplight at the top of the hill’s being on the blink (or, rather, uncharacteristically not being on the blink) is admittedly the kind of thoughtfully-selected, pragmatic detail that makes a fictional world spring to life on the page, my brunch guests’ finding themselves plunged into darkness — or as close to darkness as a deep gray Seattle afternoon will permit — must hardly have come as a surprise to those familiar with the genre. I’ll bet you saw it coming the proverbial mile away. What’s next, a cat leaping out of nowhere to startle us at a suspenseful moment?

I mean, really: all of the characters are gathered in one place, and the lights go out? Even the Agatha Christie-impaired around the table immediately began making nervous jokes about which one of us was about to meet a grisly fate.

That’s why, in case any of you have been wondering since last spring’s foray into editorial pet peeves and how to avoid them, I tend to urge savvy revisers not only to scan their manuscripts for places where summary statements (such as All the lights went out could be productively replaced with character- or situation-revealing details (In the middle of the soup course, the chandelier suddenly gave up on emitting light. Even the stoplight at the corner had ceased blinking annoyingly in Montel’s peripheral vision. The butler fumbled in the sideboard for matches.), but for opportunities to surprise and delight the reader with unexpected specifics (In the middle of the soup course — a clear, sherry-laced leek broth with a jaunty dollop of crème fraîche floating gaily on top — the dusty chandelier suddenly gave up on its losing battle to shed light on the table. Even the stoplight at the corner had ceased blinking annoyingly in Montel’s peripheral vision. Startled, he knocked his shrimp fork onto a passing cat.).

My, but that was a long sentence. Somewhere in the literary stratosphere, the late Henry James must be chortling over his holiday goose, muttering to Edith Wharton, “They just don’t make ‘em like that anymore.”

“Too few semicolons for my taste,” Edith replies. “And watch your elbow: if you knock the figgy pudding over, you are sure to set the tablecloth on fire.”

My point, should any of you by some remote chance have lost sight of it in the midst of all that frenetic activity, is that while every type of book — and certainly every genre of fiction — has its own conventions, tropes, and characterization expectations, word for word, a writer is going to get substantially more expressive mileage out of a creative telling deal than one that any inveterate reader of that book category could guess. Or even, if it’s a common enough element, add subconsciously to the scene if it does not appear on the page.

Oh, when you read that second description of the lights going out, you didn’t murmur, “I bet the butler did it,” before your eyes passed the parenthesis at the end of the example?

Yes, Millicent the agency screener is encouraged — indeed, is often explicitly trained — to be on the look-out for manuscripts that read like, well, books in their chosen categories, and yes, each book category, particularly each genre fiction category, has its own recognized and recognizable plot twists, plot lines, stock characters, and, yes, types of details. Because agents specialize in particular types of book, as well as certain types of voices — a fact well worth bearing in mind when selecting which agents to query — it does tend to be to a writer’s advantage at submission time if the manuscript fulfills category-specific expectations. (That’s as true in a query’s descriptive paragraph as in a submission’s first few pages, by the way: if the text doesn’t sound as though it would fit comfortably within the manuscript’s chosen book category, it will usually be rejected.)

Let’s face it, though, the line between making your text read like it belongs shelved with others like it and like a cliché fest can sometimes be pretty thin. Many an aspiring writer believes, mistakenly, that producing a pale replica of a famous author’s writing is a better way to win friends and influence people at an agency than to come up with something more original. Or, even more mistakenly, does not become familiar enough with what’s currently being published in that book category to be aware what conventions would now strike someone who deals with those manuscripts for a living as passé.

To put it another way: when was the last time you read a mystery in which the butler actually did it?

The result, unfortunately, is that our poor Millicent tends to see the same types of specific — as well as the same plot twists, character types, and even phrasing — over and over and over again. When you consider the sheer volume of stories within the same category any agent successful in selling such books receives in any given year, that’s hardly astonishing.

The trouble is, most submitters remain woefully in the dark (and not because the lights went out) about how such elements are likely to be received at an agency. Good writing in a particular book category is good writing, right?

Sheer repetition has made Millicent believe otherwise, alas — but honestly, it’s hard to blame her for feeling that way. What might strike Writer A as requisite for that genre is frequently precisely what Writer B considers an homage to a classic and what Writer C will decide to drop in as a humorous riff on a cliché. And that’s not even counting what Writers D-F will honestly believe is original, but is actually a subconscious lifting of material or phrasing from an admired book.

“Oh, come on,” Millicent mutters, scalding her lip on that too-hot latte she forgot in her annoyance she had set aside to cool. “Does this writer honestly think that someone who reads as much as I do can possibly read an opening line like Yesterday, I fantasized that I returned to Ottawa without Daphne du Maurier’s REBECCA springing to mind? Last night I dreamt I went to Manderlay again is arguably the most famous first line in the genre!”

Wondering why I am bringing all of this up in the midst of a series on querying? Well, several reasons. First, I wasn’t going to post today at all, but as my guests went home when the soup got cold, I had a bit of extra time on my hands. I also had a charged-up laptop, as it happens, so clearly, this is kismet.

Especially as I had a holiday-themed anecdote I had been itching to recycle, anyway. I could have worked it into a series of queries, but hey, it’s a holiday — I thought everyone might enjoy a little break from our two solid months of query consideration. And correct me if I’m wrong, but I’m guessing that those of you devoted enough to your writing to be checking in at Author! Author! today might be more seriously interested in a discussion of craft than your garden-variety casual Internet browser.

Either that, or you might be trying to avoid your nearest and dearest. I’m happy to help you do that, too.

So gather close to the Yule log, campers, and let me spin my tale. As you read, try to think like Millicent: does the narrative contain enough specifics to provide all of the characterization needed? Does it occasionally stumble into the realm of cliché? While you’re at it, why not embrace the chance to embrace the Author! Author! tradition of trying to figure out what editorial tweaks could improve the story?

Curly the camel, Moe the donkey, and, to mix Christmas traditions as thoroughly as possible, Donner the reindeer have been on tour together, strip mall manger scene after strip mall manger scene, since they were just small, furry refugees from the petting zoo where they were born. Despite their years of entertainment experience, my local nursery — plants, not animals — plasters the six-foot wire fence around their enclosure with warnings to wreath-buying patrons about keeping their fingers, gloves, hat pom-poms, scarf tassels, and bundled-up infants away from Curly’s long reach, Moe’s strong teeth, and Donner’s oddly-shaped antlers.

They also, somewhat less emphatically, erect a sign informing dog-owners that crèche livestock are not, to put it mildly, best friends with man’s best friend. Since dogs cannot, unfortunately, read and many leash-tugging owners apparently do not, poor Curly frequently thrusts himself between some yapping visitor and his hoofed friends. Nearby, nursery personnel visibly restrain themselves from shouting, “Hey, can’t you read?”

On the whole, though, human behavior seemed to leave the trio unfazed. Scores of children flung hay at them, bellowing, “Hey, Reindeer!” — or “Hey, Dog,” from those who had never seen a miniature donkey before or were confused by the ambient barking. The trio just stood there, blinking slowly, eyes glazed. Most of the time, the parents would intervene before the children grew too frustrated with their passivity and rushed the pens.

One small pink-clad screamer simply would not leave the animals alone, however. She kicked at the metal fencing, screaming words I was a surprised a kindergartener would be able to use correctly in a sentence, or, indeed, incorporate into her everyday vocabulary without getting expelled. When she picked up a rock, I wandered over to the fence to distract her with a hastily-constructed fairy tale about our barnyard friends. And camels.

Almost immediately, a bulbous man in shorts and a t-shirt materialized by my side. Despite ambient cold that left our breath visible, his exposed arms and legs were not even goose-bumped. “Come over here,” he barked at the little girl, dragging her along the fence until they were directly in front of Curly.

Was he going to make her apologize to the camel? Curly did not seem to be expecting it, but perhaps his furry friends would appreciate the gesture.

Releasing the quivering child, the man — whose clothing, I noticed, was emblazoned with advertisements for a local band and Nike, respectively, not the nursery — reached up and over the chain-link fence, snapping his fingers. Placidly, Curly dipped his head, extending his hyper-mobile lips toward the hand.

Curious to hear what happened next, aren’t you? That’s a good indicator that a scene is paced well. See how selecting those details carefully, as well as not over-burdening the text with explanations, can increase suspense while simultaneously moving the plot along?

So why, I ask you, would our old pal Millicent, have stopped reading part-way through paragraph #3? Because, I assure you, most would have: one of her most notorious pet peeves has reared its ugly head here.

If you pointed out that the narration switched tenses between the second and third paragraphs, congratulations! Paragraphs Nos. 1 and 2 are in the present tense; paragraph #3 is in the past.

Submissions and contest entries do that all the time; so do, believe it or not, descriptive paragraphs in query letters. Sometimes, they even switch back to the original tense later in the text, or vacillate from sentence to sentence.

Already, I can spot some raised hands out there. “But Anne,” adherents of variable tenses point out, and with some reason, “Paragraphs #1 and #2 describe ongoing conditions, while paragraph #3 on focuses upon one-time events. Doesn’t that mean that the tense choices here are appropriate, or at least defensible?”

Good question, lovers of the present tense. Professional readers — agents, editors, contest judges, writing teachers, etc. — are trained to spot redundancies in a manuscript. They’re also taught to leap upon inconsistencies.

In other words, Millicent is likely to assume that the change of tense is not the result of well thought-out authorial choice, but simply a mistake that did not get caught in the proofreading process — or, if this were a descriptive paragraph in a query, the after-effects of an incomplete merger of two different versions, one in the present tense and one in the past.

Why might that make her stop reading altogether? Like other commonly-made errors, the tense inconsistency may well jar her out of the flow of the story. Next!

You habitual tense-switchers are not particularly happy with that answer, are you? “Okay, so she’s detail-oriented, but this isn’t a writing mistake; this is a stylistic choice. So why would Millicent be annoyed by it?”

On its face, your logic is pretty sound, tense-switchers: it would indeed be possible, within the context of a civil conversation between author and reader, to justify the tense choices in the example above. A writer might ostensibly win an argument with, say, a writing teacher, critique group, or even an editor about keeping the switch in the text. But that doesn’t mean it would be a good idea to submit pages with tense inconsistencies to Millicent — or to her aunt Mehitabel the contest judge, for that matter.

Why, you ask? Long-time readers of this blog, chant it with me now: because the writer is seldom present when an agency screener, editorial assistant, or contest judge encounters his manuscript for the first time. Successful manuscripts, queries, synopses, and contest entries are thus those that do not require additional verbal explanation.

So even if the writer is technically correct, if a tense switch seems unjustified to Millicent — if it appears to be, say, an incomplete revision between a manuscript originally in the present tense and a subsequent draft in the past, or vice-versa — that’s usually the ball game. So why risk it? Especially when, as in this case, making the tense consistent does not detract at all from either the meaning or the voice of the section. Lookee:

Curly the camel, Moe the donkey, and, to mix Christmas traditions as thoroughly as possible, Donner the reindeer had been on tour together, strip mall manger scene after strip mall manger scene, since they were just small, furry refugees from the petting zoo where they were born. Despite their years of entertainment experience, my local nursery — plants, not animals — plastered the six-foot wire fence around their enclosure with warnings to wreath-buying patrons about keeping their fingers, gloves, hat pom-poms, scarf tassels, and bundled-up infants away from Curly’s long reach, Moe’s strong teeth, and Donner’s oddly-shaped antlers.

They also, somewhat less emphatically, erected a sign informing dog-owners that crèche livestock are not, to put it mildly, best friends with man’s best friend. Since dogs cannot, unfortunately, read and many leash-tugging owners apparently would not, poor Curly frequently thrust himself between some yapping visitor and his hoofed friends. Nearby, nursery personnel visibly restrained themselves from shouting, “Hey, can’t you read?”

On the whole, though, human behavior seemed to leave the trio unfazed. Scores of children flung hay at them, bellowing, “Hey, Reindeer!” — or “Hey, Dog,” from those who had never seen a miniature donkey before or were confused by the ambient barking. The trio just stood there, blinking slowly, eyes glazed. Most of the time, the parents would intervene before the children grew too frustrated with their passivity and rushed the pens.

That’s as painless a revision as you’re ever likely to encounter, folks, by see how big a difference it makes to the text? All it requires is a good proofreading eye and a willingness to view the story from Millicent’s perspective, not the writer’s. (The latter, after all, is already familiar with the storyline.) And need I even add that this variety of inconsistency is easiest to catch if one reads one’s submission or contest entry IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD?

I thought not. Let’s move on with the story, to see if we can catch any other Millicent-displeasers.

Delicately, politely, as if he were extracting an egg from beneath a mother hen, Curly took the man’s fingers into his gargantuan mouth. The hand did not budge. The camel paused meditatively for a few seconds, tasting, then sucked the hand into his mouth up to the elbow, dragging the man up to his tiptoes.

Instinctively, I took a step toward the child. If the object lesson about the dangers of violating animals’ personal space was about to go horribly awry, the least I could do was shield her from seeing the bloody denouement.

The man waved me back with his free hand. “See, Tanya?” he told the saucer-eyed girl. “They like people. If you treat them nicely, they’ll treat you nicely.”

“That’s right, sweetie,” a stringy-haired woman called from the nearby wreath display. “Be nice to the animals, and they’ll never hurt you.”

“You just have to learn what they like.” A helpful bystander kicked a tall crate toward the man’s feet, so he could follow his arm skyward. “Camels love sucking on things.”

Mentally, I began taking notes, in preparation for my inevitable testimony in a court of law. “I think she’s got the point. Maybe it’s time to back off now?”

Okay, what’s the problem this time? Hint: it’s even harder to catch than the last.

No? What about all of that redundancy in the dialogue?

That made some of you do a double-take, didn’t it? “But Anne,” several exclaim, “that’s how people talk in real life! You’re not gearing up to tell us that Millicent finds realistic dialogue annoying, are you?”

Um, sort of. At least the parts of real-life speech that are redundant. Or not germane to what’s going on. Or just plain boring.

Which is to say, as any close listener to everyday speech would happily tell you, most of it.

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

“But Anne,” I hear some of you protest, “isn’t that pretty self-evident? Just as absolutely faithful recreations of real-life events often don’t translate well into fiction, neither does most dialogue. Am I missing an additional nuance here?”

Perhaps one: aspiring writers are also apt to forget that real-life dialogue is seldom character-revealing — and thus reproducing it in a manuscript will often not convey as much about a character as we sometimes expect. Take, for instance, the oh-so-common writerly habit of placing the speeches of an annoying co-worker, relative, ex-lover, nasty dental receptionist, etc. into fictional mouth of a minor novel character as a passive-aggressive form of revenge.

Come on, every writer’s at least thought about it. To a professional reader, the very plausibility of this type dialogue often labels it as lifted from real life:

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

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

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

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

“I thought you had dropped it.”


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

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

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

Actually, that was a set of trick questions. The answer to each part is the same: because the narrative doesn’t provide enough motivation for the intensity of Dina’s response. Fairly clearly, the writer doesn’t think that any such explanation is necessary.

That’s usually an indication that the writer has a fully-formed mental image (negative, in this case) of the villain in question — something that Millicent, by definition, would not walk into the scene possessing. Nor would any other reader who was neither there when the incident occurred nor had heard the author complain vociferously about it.

In other words, what we have here is a rather subtle manifestation of the telling, rather than showing phenomenon. Because the writer experienced this exchange as nasty because Dina was nasty, she has assumed that the reader will perceive it that way as well. But without more character development for Dina — or indeed, some indication of whether this kind of insistence was typical for her — the reader isn’t really getting enough information to draw that conclusion.

Or any other, for that matter. It’s just an anecdote. Yet most self-editing writers, especially those who happen to be writing memoir, wouldn’t notice this narrative lack. Any guesses why?

If you immediately shouted that it was due to the fact that his memory of Dina the real person is so strong, help yourself to four peppermint cookies from the holiday table. In the writer’s mind, her character is so well established that he can just write about her, rather than helping the reader get to know her.

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

And yes, I WAS darned annoyed when Dina — in real life, a very nice woman named Ellen who happened to be having a spectacularly bad day — misinterpreted my act of good citizenship. If I crave well-deserved vindication from the total strangers who might conceivably read this story, however, it’s incumbent upon me to do quite a bit more character development. Not to mention integrating the incident into the storyline well enough that it’s actually interesting to read.

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

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

A: “Oh. You’re home.”

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

A: “Have a nice day?”

B: “Um-hm.”

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

B: “Yeah. “

A: “Ham sound good for dinner?”

B: “Yeah.”

A good third of the dialogue Millicent sees runs approximately like this, I tremble to report. Understand now why she might become just a tad touchy at the sight of dialogue that provides neither character development nor moves the plot along?

As a general rule of thumb — sore or otherwise — I like to flag any piece of dialogue that contains more than one use of yeah, really, yes, no, uh-huh, or, often, um. Almost invariably, these are an indication that the dialogue could either be tightened considerably or needs to be pepped up.

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

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

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

Hard to argue with that, eh? Yet, like most writers receiving critical feedback, I fought it at first. Since the dialogue in my advisor’s published works has seldom, if ever, strayed beyond three lines, regardless of situation or character, I was not particularly inclined to heed this advice — have you noticed how often it’s true that established writers with little or no teaching background spout aphorisms that all boil down to write as I do? — but I have to say, it has been useful in editing, both for others’ work and my own.

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

One more insight, then I’ll let you get back to your relatives: you’ve been having just a little trouble paying attention to my arguments, haven’t you? I’m betting that some substantial part of your mind has been distracted, wondering what happened to the arm in the camel’s mouth.

That, my friends, is how Millicent — and most other readers, professional and non-pro alike — feels when an interesting one- or two-paragraph teaser, the kind that aspiring writers so love placing within italics at the beginning of their manuscripts, gives way to an apparently or only tangentially unrelated second scene. Yes, we see it in published books all the time, but in a submission, it’s a risky strategy.

“Hey!” Millicent cries, spitting out her mouthful of scalding latte, “what happened to that darn interesting plot I’d gotten absorbed in? What’s this writer trying to do, hook me with something exciting, then drop me into a comparatively mundane storyline?”

Let’s be honest, folks: that’s precisely what most writers who use this trick are trying to do. Professional readers are wise to it by now.

Remember, part of being a good storyteller involves knowing when to relieve the suspense — and frankly, in the case of my camel story, Alfred Hitchcock himself would have chosen to do so by now. Ahem:

“Give me a boost,” the man asked calmly, but his eyes were beaming panic over his daughter’s head. Curly’s lips were exploring the first few inches of his t-shirt sleeve.

Since his arm appeared to be on the verge of being ripped off at the shoulder, the crate-kicker and I hastily complied. With his uneaten hand, he began tickling the camel’s lips, rubbing the gums as if he were a mammalian dentist. Curly face elongated, as though he were going to sneeze. A loud pop, a slurp, and the man’s arm returned to the land of the living.

He strutted his way down from the crate. “See?” he told the girl. “If you know what you’re doing, they won’t hurt you.”

“Yes, Daddy,” she whispered, staring aghast at his friction-reddened arm, manifestly resolving never to have anything whatsoever to do with an animal larger than herself again.

The moral, if I may venture one: just because something seems like a good idea at first blush doesn’t mean that it’s worth stubbornly adhering to it. One of the keys to successful self-editing is flexibility.

That, and keeping any parts of your body involved in typing out of animals’ mouths. Happy holidays, everybody, and keep up the good work!

Pet Peeves on Parade, part XXXIII, and Structural Repetition, part X: a parting glance before we move to pastures new

Are you still palpitating over that false suspense I managed to build up by the end of yesterday’s post, campers? Or is that heavy panting I hear all of you who are planning to give verbal pitches this summer tumbling onto my virtual doorstep, breathlessly eager to begin our long-anticipated Pitchingpalooza bright and early tomorrow?

Well, it probably won’t be bright and early, unless you are prone to measure such things by moonrise, rather than sunrise; tomorrow is going to be a rather full day. But I shall be launching our latest ‘Palooza, never fear.

“Um, Anne?” the more pacing-minded among you murmur, tapping your watches meaningfully. “Is it my imagination, or did you just extend the false suspense about today’s promised professional readers’ pet peeve by another two whole paragraphs by the simple expedient of digressing into another topic?”

Quite right, pace-minders — and you lengthened it by another paragraph through pointing it out. Now, I’m stretching it to four. Whee! We could keep this up for hours.

But we won’t, because we’ve all gotten the message by now, right? When our old pal, Millicent the agency screener, picks up a page 1, she expects the story (or argument, in the case of nonfiction) to get going right away. When the opening lines dither, evade, and generally avoid leaping right into the meat of the story, she has been known to become just a trifle impatient.

“What is this story about?” she fumes over her latte. “And why isn’t this writer getting on with it?”

Certainly an understandable reaction — and if it isn’t, I can only advise you to go back and read the first four paragraphs of this post again. Perhaps it’s the circles in which I move, but personally, I’ve never met a Millicent — or agent, editor, or contest judge, for that matter — who didn’t share this preference for a book’s opening to get on with it, already. Rarely, if ever, does one hear a professional reader say, “I liked that book, but do you know what would have made it better? A slower page 1. Heck, it would have benefitted from not beginning the central story at all until, oh, page 12 or so.”

I bring this up not only because a page 1 that drags is very frequently enough to trigger rejection — yes, even if the writing that lulls the reader along is beautifully constructed — and this will be my last post in our long-lingering Pet Peeves on Parade series. No, I’ve treated you to this last-minute admonition as a segue into one of the most important rules for a revising writer to remember: just as each authorial voice is individual — good authorial voice, anyway — so is each writer’s pattern of problems. Some very talented writers just can’t manage to get their stories started until page 34; others use and in every other sentence, and still others are purely incapable of remembering the difference between there, they’re, and their. Some rechristen their characters every thirty pages, then forget to go back and change earlier names; some meant to do background research on their protagonist’s mother’s job as a beekeeper, but never seemed to get around to it.

Yes, falling prey to any or all of these tendencies could result in Millicent’s shouting, “Next!” over your submission. You could waste endless energy worrying about that outcome. But rather than fearing her ire or resenting the professional reader’s notoriously sharp eye, may I make a suggestion for a better use of your time? Why not devote yourself to learning what your personal writing patterns are, and figuring out which ones you like enough to keep?

After all, there is no secret formula for writing success: what works for one story will be appallingly inappropriate in another, and vice versa. A thoughtful writer often experiments with a number of different voices, literary devices, and writing styles before settling on the best fit for her book. That’s healthy and a necessary part of a good writer’s learning process — hey, nobody is born knowing every craft trick in the book — but it’s vital to get into the habit of re-reading one’s own manuscripts (ideally, IN THEIR ENTIRETY, IN HARD COPY, and OUT LOUD, of course) with an eye to figuring out which of those experiments are worth incorporating into the book’s overall voice.

Why? Chant it with me now, those of you who have been intrepid enough to follow this series all the way through to the bitter end: because the hallmark of a really good authorial voice is consistency.

That’s not going to happen all by itself, you know — but you’d be surprised at how many submitters seem to act as though it would. As Millicent would be only too happy to tell you if you take her out for a latte (you think it’s easy to stay awake through all of those slow openings?), submissions and contest entries that begin in one voice and switch to another 2, 10, or 100 pages in are almost as common as manuscripts that have no distinctive voice at all.

It may seem self-evident, but in order to clarify your authorial voice or make it consistent across a manuscript, you’re going to need to recognize what it is. How are you going to know what’s good about your writing if you don’t read it? And reread it with each subsequent draft? Not only to catch your personal pattern of mistakes, but to learn what you sound like at your best.

“That’s a lovely sentiment, Anne,” the clock-watchers we met above chime in, “and I’m sure it’s practical advice, well worth heeding. But haven’t you also just distracted us from the fact that you STILL haven’t filled us in on the identity of the Millicent-baiter you teased us about on Monday? Jeez, Alfred Hitchcock himself would have revealed the culprit by now.”

Quite right, pacing-minders. The notorious species of structural repetition that causes professional readers to gnash their teeth and mutter under their breath is — wait, Millie, put down that ice pick! Help! Hel…

Just kidding. You watch-tappers didn’t think you were going to walk away unscathed after the Hitchcock crack, did you?

Actually, one eagle-eyed reader delved into her own manuscript and diagnosed this dreaded form of repetition for herself. Kudos to intrepid Anne A. for bringing it up in the comments a couple of months back:

I’d been looking back at my writing and trying to get rid of my characters’ excessive nodding, shrugging, and looking…especially looking. I’m having a lot of trouble with the looking.

I’ve found that I tend to use looking as a cue in the dialogue for whom a particular phrase is targeted; that is, there are four or five characters standing around and if one character says something directed specifically to another (e.g., “Can you fight?”), I have the speaker look at the target first. I’m finding these terribly difficult to get rid of, because without them the conversation makes little sense.

Any advice on how to handle this? It appears I cycle through, in decreasing frequency: “looked to”, “turned to”, “said to”, and direct address by name. I have a terrible feeling that all of these sound far too repetitive.

We have a winner: looked is one of the most frequently repeated words in manuscript submissions. If I had a nickel for every time I had spotted look, watch, saw, etc. on the manuscript page, well, I’d have a heck of a lot of nickels.

I’m not talking about enough to buy my own publishing house, mind you. Don’t be ridiculous. I’m talking about enough nickels to build a publishing house from sub-basement to rafters entirely out of the things.

Why is look so pervasive? Well, aspiring writers rely upon it, and upon vision-related verb phrases in general, quite heavily, and not always because most human beings glean most of their information about the world around them through their eyes. Often, characters — particularly protagonists — will look things as a means of introducing those things into the narrative. Essentially, the character’s eyes act like a laser pointer, directing the reader’s attention someplace specific. Lookee:

“Oh, I give up,” Albert said crossly. “I’m tired of trying to find that last Easter egg. It can rot, for all I care.”

Sharon cast her eyes around the room, taking in the disordered bookcase, the emptied-out desk drawers, and the overturned couch. She saw no trace of an eggshell of any sort.

Effectively, Sharon is acting as the reader’s eyes in this passage: she moves her eyes, and we are shown objects. Although she is acting, she is passive; she’s not commenting upon those objects — say, drawing the conclusion that Albert is not a particularly well-organized searcher or that the hotel’s maid is likely to find his pastime annoying — nor is she changing the situation through doing anything like knocking over a bookcase herself. She’s not so much advancing the scene as allowing herself to be used as a narrative device.

That’s good news for the self-editor, believe it or not. Instead of showing us the room via a seeing-eye Sharon, the reviser can radically reduce the number of looking references by simply showing what is in the room. That would free up Sharon to engage in activities of her own.

Albert sat in the midst of chaos of his own making. He had disordered the bookcase, emptied out several well-packed desk drawers, and upended the couch. “Oh, I give up. I’m tired of trying to find that last Easter egg. It can rot, for all I care.”

“And I’m tired of cleaning up after you.” Slowly, Sharon withdrew a brace of pistols from her fashionable purse. “We duel at dawn. The maid has offered to be my second.”

Another popular use for looking verbs is to remind the reader from whose perspective she’s approaching the story. This is particularly common in first-person or tight third-person narratives. As in:

I looked at the beautiful blue sky and the hopeful buds on the green trees; they made me sad.

That’s one way to alert the reader to the existence of the buds on the trees and the beauty of the sky — which is, we are told explicitly, blue, as opposed to all of those other colors beautiful skies are always sporting — but it’s not the only narrative possibility, and usually not the most imaginative one. It also slightly blurs the author’s intention: is the reader supposed to concentrate upon the fact that the trees are budding hopefully, or the fact that our narrator saw the buds and projected hope onto them?

Even if the image hitting the narrator’s cornea actually were the most important aspect of this particular sentence — in this example, it isn’t — often, the point of the protagonist’s looking at things is not the action itself, but to alert the reader that the objects being seen exist. Unless this device is used very sparingly, though, most readers will tire pretty quickly of being told over and over again that the protagonist is — stop the presses — seeing or noticing everything around her.

Hard to blame the reader for that, you must admit. From his point of view, it’s self-evident: the object is present in the environment, so naturally, the protagonist sees it. So?

Millicent’s reaction, predictably, is quite a bit less forgiving. “Stop telling me over and over that the protagonist is seeing things!” she will mutter, reaching for her third latte of the afternoon. “You don’t need to keep reminding me of the narrative perspective!”

So what’s a reviser to do with this type of Millicent-annoying look? Cut ‘em without mercy. With a little careful planning, it’s almost always possible simply to have stimuli external to the protagonist just show up, without reminding the reader that the players in the scene have seen them or having the protagonist acknowledge their existence.

Fringe benefit: because this approach encourages the things in question to be more active, the result is often a more vibrant narrative. Take a peek:

The sun shone in a cloudless sky, sending a caressing warmth to encourage the hopeful buds on the green trees. Their very exuberance made me sad.

Anne A’s concern sounds like combination of these two types of looking patterns, a mélange that used to be quite widespread in YA and many categories of genre fiction. In this combo, not only do the characters’ eyeballs serve as the narrator’s means of calling the reader’s attention to something in the physical environment as a sort of, “Hey, you — notice at that!” substitute — those busy, busy peepers also provide the transition between description (often presented as the result of observation) and the next set of actions.

What might that look like on the page, you ask? Let us turn to our next example. While I’m at it, I’ll toss in a little name repetition, since Anne A. mentioned that it was one of her personal bugbears.

Helene looked around the room. Not much there; the occupants must have moved out in a hurry. Suddenly, she saw a glint of silver on the mantelpiece.

She turned to Karen. “Look, Karen! Could that be Aunt Monica’s long-lost broach, the one we have been seeking for hours? If it is, maybe we will be able to figure out how to open its secret compartment and find the combination to the wall safe our beloved aunt told us three times a week throughout our collective girlhood was stored there.” She looked to her cousin for confirmation. “Well? Is it her broach?”

Karen picked up the round pin, examining it. “Possibly, Helene. Strange…”

Helene looked at her cousin expectantly. “What’s strange?”

Karen glanced nervously back toward the door. Did she hear movement out there? “Oh, that the search party, the militia, and the bloodhounds would have missed its being in such an obvious location.”

As you may see — looking verbs are addictive, aren’t they? — it’s not difficult for this type of looking to turn into Hollywood narration, dialogue in which the speaker tells the hearer things both parties already know, purely to convey the information to the reader. Like most dialogue plagued by this phenomenon, this passage benefits from trimming it. All of that visual activity could easily go, too, making room for some more revealing details or more action. (Why didn’t Helene pick up the darned broach herself, if she was so interested in it?) Also, if we really put our editorial minds to it, we could probably stop our heroines from squawking their names at each other constantly like hyacinth macaws.

The room’s dark wood paneling emphasized how quickly the former occupants had decamped. Dust outlines showed where a sinuously curved sofa, an ornate-footed chair, an old-fashioned two-sided partner desk had rested for decades. Only the mantelpiece seemed to have been cleaned within the last year. Silver glinted against the mahogany.

“Aunt Monica’s broach!” She dashed across the room, but Karen beat her to it.

Her cousin ran her fingertips across the polished surface. “How could it be this shiny, if it’s been lying here for a year?”

Helene completed the thought: “And why would everyone else who’s traipsed through here miss it? This was planted!”

Another tendency to keep an eye out for (oh, you think it’s easy to keep coming up with these?) is looking used as a stand-in for other, more interesting activity. It’s indigenous to recently revised manuscripts, as a means of identifying speakers without cluttering up the dialogue with all of those tag lines that graced the first draft. Unfortunately, not every alternative to he said makes for particularly scintillating reading.

Art looked askance at his adopted brother. “You’re not afraid, are you, Kay?”

Kay glanced at the dragon breathing fire nearby. Surely, any sane human being would be afraid. “Not if you will hand me that sword over there on your right. No, farther, next to the tumbledown shack in which that strange old man lives. That’s it, right next to the bronze chicken our grandmother smelted in her dotage. Oh, now you’ve gone too far. Don’t you see it there, beside that gently rippling stream?”

Art recoiled at the sight of it. “You mean the sword stuck in the stone?”

Here, the narrative falls into another Millicent-annoying trap: presentation of the physical environment not via explicit description, but by talking about it as though the narrator (or in this case, the character Kay) and the reader were watching a film of the scene together. Rather than giving us enough detail to be able to picture it as the writer imagines it, we’re left to guess what type of landscape could possibly contain all of those disparate elements.

And why might that narrative choice irritate Millicent? Sing it out loud and clear, campers: it’s the writer’s job to convey a sense of place, not the reader’s job to fill in descriptive details.

Another extremely common use of looked is as a substitute for showing emotional reactions. As any Millicent who has been at it for a while knows to her cost, aspiring writers just love having characters look at one another instead of evincing a more revealing response to something that has just happened.

All of a sudden, the wind chime over Violet’s left shoulder began ringing violently; Llewellyn’s chair seemed to be slipping sideways beneath him. They looked at each other.

“What’s happening?” Violet cried.

Doesn’t add all that much to the scene, does it? That’s because from the reader’s perspective, the mere fact that Violet and Llewellyn chose that moment to train their eyeballs on each other isn’t all that illuminating. Described this flatly, it’s such a generic act that mentioning it doesn’t either advance the plot or reveal character. It begs the question: how did they look at each other? Why did they look at each other?

Okay, so that was two questions. Here’s a third: is there something else that one or both of them could do or say here that would do a better job of advancing the plot and/or revealing what these people are thinking or feeling in this particular moment?

And, of course, there’s the ever-popular self-sufficient glare:

Not looking where he was going, Armand tripped over Patrice’s extended feet. She shot him a look.

Again, what kind of look? What did she intend it to convey, and was it in fact an accurate external representation of her internal mental processes? And while we readers are asking so many questions, why on earth didn’t the writer save us all this trouble by coughing up a substantive description of a meaningful response in the first place?

Be on the lookout, so to speak, for versions of she looked away, a sentence widely used as shorthand for a character’s conscious attempt to avoid conveying emotion to another character. While flesh-and-blood people do actually look away from one another from time to time, and for that very reason, this phrasing, too, can start to feel pretty redundant if characters do it very often.

At the risk of giving away a trade secret, looking away is also not usually the most interesting reaction a character can have to a stressful situation. Frequently, this action is a drama-killer, a means of allowing a character to avoid a direct confrontation. That may be desirable in real life, but since Millicent likes to see conflict on every single page of a novel or memoir — you knew that, right? — do you really want to squander a golden opportunity for injecting more of it into your story?

In short, you’re going to want to take a close look at all of those looks, evaluating on a case-by-case basis. Each time it appears, ask yourself: is this an effective way to convey the meaning I want to the reader, or is this just shorthand? Is it a stand-in for something else, a more revealing action, perhaps, or more interesting possibility? Would the plot or characterization would benefit from a different kind of sentence?

What you should most emphatically not do, however, is simply do a search for the word and cut every use indiscriminately. You’re going to want to exercise your judgment — always bearing in mind, of course, that the reader cannot read your mind, and thus may not interpret shorthand in quite the way you intended. You can’t blame her for that: since all she knows about the story you are telling is what the narrative shows and tells her, if you don’t fill in the details, she has to rely upon her imagination.

Don’t make me start the chanting again. You know the tune by now, right?

Remember, too, that what might work perfectly well in an individual sentence may well become a distracting pattern over the course of a paragraph, page, or even scene. Look is a sneaky one; it is used in so many context to mean so many things. To sharpen your eye to its many means of imbedding itself in text, let’s take a gander at few frolicking in their natural habitat.

He looked at me passionately. “But I want you to marry me, Mary!”

Quickly, I looked down at the fringe decorating my skirt. “I think you should go, Didier.

“Go?” He gave me a look of disbelief. “Didn’t you hear what I just said?”

I looked up. “Didn’t you hear what I just said?”

Taken individually, each of these uses of look is perfectly legitimate. But the problem here isn’t just the word repetition — it’s that looking is acting as a stand-in for a whole lot of potentially interesting human interaction. Over and over and over again.

Don’t look away — we already know what do in this situation, right? When confronted with characters merely looking in response to stimuli, we ask: could they have more character-revealing (or situation-revealing) responses?

The possibilities are endless, of course — which is precisely why I’m a big fan of this particular revision strategy; it can open a simple scene up in some fascinating ways. For instance:

He kissed my hand passionately. “But I want you to marry me, Mary!”

I abruptly became absorbed in studying the fringe decorating my skirt. “I think you should go, Didier.”

“Go?” His tone implied that I’d just asked him to leap off a fifty-foot cliff. “Didn’t you hear what I just said?”

So much for sparing his feelings. “Didn’t you hear what I just said?”

Is everyone comfortable with the prospect of tackling all of those looks in context, retaining some, and coming up with interesting and creative substitutes for others? Good. Now that you’ve started thinking about revising with your reader’s reaction in mind, let’s go back and apply the principles we’ve been discussing to the problem of proper noun repetition in a manuscript.

Oh, did you think that you were through with practical examples, because we were so close to the end of this series? Not a chance — over the past few weeks, we have established a method for dealing with word repetition. Now that we have added the last tool, placing ourselves behind the reader’s spectacles in order to figure out whether the over-used word in question is serving the narrative well, to our writer’s tool belt, aren’t you just dying to trot out the whole set of wrenches?

I’m going to take that look you’re all giving me as a yes. Perhaps if I’m really lucky, you’ll exchange glances. Maybe even meaningful ones.

Suppose for a moment that in mid-revision, you have suddenly become overwhelmed with doubt: have you been over-using proper names? Rather than panic in the face of such a dreadful possibility, you know precisely what to do: first, ascertain just how many of the darned things there are in your manuscript, so you may see just how serious the problem is — and where to begin to attack it.

So you, wise soul, print up a hard copy of your manuscript, pull out your trusty highlighter pens, and mark every time a character’s name appears, dedicating one color to each character. After highlighting up a storm for a chapter or two, you go back and flip through the pages. If a single color appears more than a couple of times on a page, you know that you might want to see where you could trim.

This test, which can be used to diagnose any suspected repetitive pattern in a manuscript, will reveal the most about Millicent’s probable reaction if you begin marking on page 1, of course, rather than at some random point in Chapter 12. If you can only find time to do a few pages, though, you might not want to start marking on page 1. A good, quick check on your name-usage habits is to highlight a two-person dialogue between major characters from the middle of the manuscript.

Why a two-character scene, you ask? See if this pattern seems at all familiar:

”I’ve never seen that giant centipede before,” Tyrone lied. “It just crawled into the house, Mom.”

Angela placed her fists upon her ample hips. “I suppose it opened the back door by itself?”

“It certainly has enough legs to do it,” Tyrone said, examining it. “Or it could have crawled through the keyhole.”

“Next you’ll be telling me that the cat is the one who has been opening the kitchen cabinets,” Angela retorted.

“I’ve seen her do it!” Tyrone insisted.

Angela placed her hand upon his head. “Tyrone, I hate to break it to you, but cats don’t have opposable thumbs. Neither do centipedes. So unless you’re harboring a chimpanzee I don’t know about, I’m going to assume that human hands did all these things.”

The boy cast a nervous glance at his closet door; did Mom know about Archie? “If you say so.”

Did you catch the patterns here? If you immediately said, “By gum, a skimming reader’s eye might mix up Angela and Archie, since they both start with the letter A,” give yourself a gold star for being able to remember that far back in this series. Take another star out of petty cash if you also murmured, “This writer is identifying speakers far, far more often than necessary. I wonder if the same pattern persists throughout the manuscript?”

In this excerpt, the pattern is clear, right? In case those baleful looks you’re giving me mean no, let me ask a follow-up question: how do we know that this scene doesn’t really require this many tag lines?

After the first set of exchanges, there really isn’t any doubt about who is speaking when, is there? So why does the reader need to be reminded so frequently who is who, when the speeches are alternating in a predictable rhythm?

The over-use of tag lines is quite pervasive in submissions, and for good reason: like over-abundant proper names, aspiring writers often believe that they reduce confusion. But to professional eyes, the author of the example above has apparently invented unnecessary opportunities for repeating her characters’ names.

Be on the lookout, too, for frequent use of relational terms as substitutes for names: her mother, my brother, her boss. Often, writers who lean heavily upon name usage will pepper their manuscripts with these, too — and again, physically marking them in the text is generally the best way to figure out if there’s too much pepper in your manuscript.

Okay, so that was a bad joke, but it was intended to soften a hard reality: until repetitions of these phrases are actually highlighted on the manuscript page, it’s well-nigh impossible for most aspiring writers to understand fully why this particular type of repetition drives the pros mad. Relationship repetition may seem merely descriptive or innocuous to a casual reader, but it reduces professional readers to apoplexy; they read it as the writer’s insecurity about the reader’s caring enough – or not being smart enough — to remember how these people are related.

Speaking of over-reactions: “Criminy,” Millicent has been known to mutter. “Is there a REASON you feel the need to tell me three times per page that Roger is Yvette’s son?” Do you think I have no memory at all?”

Sound at all familiar?

In this instance, I think Millicent has some justification for feeling that the writer is talking down to the reader. Unless you are writing a story that will be published in serial form, as so many of Dickens’ works were, it’s not necessary, and can be downright annoying, to keep referring to a character by her relationship to the protagonist.

Especially when, as often happens, the reader is presented with the relationship from several different perspectives. As in:

Brenda looked up at her mother. “Are you sure he’s dead? Couldn’t it be another false alarm?”

Mona cradled her husband’s blue-tinted face in her wrinkled but bejeweled hands. “You’re thinking of my last husband, Martin, the swimmer. Bert’s not capable of holding his breath this long.”

“I didn’t say he was faking it.” Brenda lifted her stepfather’s lifeless arm, dropped it. “I’m just saying that there’s a big difference between comatose and dead.”

“Fine.” Mona kicked her purse at her daughter. “Root through there until you find my compact, and hold the mirror under his nose. If he’s alive, it’ll fog up.”

“For heaven’s sake!” Millicent will be crying by this point in the manuscript, startling fellow screeners in adjacent cubicles. “If Mona is the mother, OF COURSE Brenda is the daughter! What do you think, I’m an idiot?”

Generally speaking, the formal relationship between two characters, particularly if one of those characters is the protagonist, needs to be mentioned to the reader only once in a chapter, at most. If it’s a significant relationship, it may well need to be brought up only once in the book, unless there honestly are issues of mistaken identity involved.

Otherwise, try giving the reminders a bit of a rest.

While you have your marking pens out, it’s not a bad idea to check your submission pages for other instances of phrase repetition as well. I’m not talking about pet phrases here — come on, admit it: every writer has a few phrases and words he likes enough to reuse with some frequency — but overworked nouns and descriptive phrases. Those have a nasty habit of offending the professional eye, too.

You’d be astonished at how much the repetition of even a single verb in two consecutive sentences, for instance, can make a manuscript seem less interesting. Especially — and this is almost impossible to catch when editing on screen, but genuinely irksome to see on a printed page — if the same word or phrase begins or ends two or more sentences in a row.

If you are clever and professional-minded enough to scan your manuscript IN ITS ENTIRETY, IN HARD COPY and OUT LOUD (gee, where have I heard that advice before?), it will immediately become apparent why: it reads as though the point of the paragraph is to get through the information within it as quickly as possible, rather than to write about it as beautifully as possible.

In a race run amongst the stylish, my friends, even a couple of lines that fall down on the job can cost you a head start. You’re in this to express yourself marvelously: try to be consistent about it, but use your best judgment on a case-by-case basis.

That’s such a pretty thought that I am going to sign off here for the day — and the series. Next time, it’s on to the rigors and joys of pitching. Keep up the good work!

Pet Peeves on Parade, part XXXII, and Structural Repetition, part IX: who is that handsome devil in the mirror, and why shouldn’t I consider him the sole arbiter of clarity?

Before I launch into what we all devoutly hope will be my next-to-last post on structural repetition (for the nonce, at least), a recommendation for all of you who write YA: because it’s always a good idea to familiarize oneself with the roots of one’s chosen book category, I would highly recommend that you take a gander at this quite interesting interview with YA grande dame Beverly Cleary. Actually, any writer planning to be a legend in her own time might want to take a peek at it. It’s both fascinating and falls into an interview trap that’s become surprisingly common of late — when asked what books she reads in her own category, Cleary, said that she doesn’t read any. Not too long ago, Philip Roth told a reporter essentially the same thing: readers should continue to pick up his novels, but he no longer reads fiction.

“I wised up,” he said.

I have to say, this strikes me as a trifle tone-deaf, given the difficulties the literary market has been facing of late. If writers don’t read (and buy) books in their own categories, who will? And how is a writer to know how his type of book — and his type of reader — is growing and changing unless he keeps an eye on what’s come out recently?

To be fair, it used to be considered rather chic for authors to pretend that they never thought about their readerships’ tastes while constructing what turned out to be bestsellers. No, art was art and commerce was commerce, and ne’er the twain shall meet: the only thing on the author’s mind, we were given to understand, was the inspiration descending from on high and his own fine sense of what would work on the page literary.

This, like the still-pervasive interview implication that what ends up on the page is first draft, is not a reflection of the realities of authorial life; it’s spin. And it’s unfortunate spin, because statements like these give aspiring writers everywhere the false impression that being a successful author has nothing to do with pleasing one’s readership, or even bothering to learn anything about their tastes. No, this argument goes, a truly gifted writer never seeks to please anyone on the page but himself.

It sounds tempting at first blush, doesn’t it? Art for art’s sake has always appealed to artists. But as a reader — as the overwhelming majority of good writers are, bless your hearts — doesn’t it strike you as a trifle insulting to be told what to like? Especially if the person telling you to like his work one moment is telling you the next moment that he doesn’t read anyone else’s work, and thus cannot provide a well-informed comparative assessment?

I leave the answers to those salient questions to further debate between you and your muse. For our purposes today, let’s take away three things. First, interview styles are as subject to change over time as writing styles; what sounded cool in 1963 may produce a significantly different impression now. It’s not a bad idea, then, for a first-time author to invest some time in reading and listening to recent author interviews, to see what works now and what seems like an idea whose time has passed.

Second, while established authors can sometimes afford to be cavalier about how their writing will strike their readers (although I suspect that you’d be hard-pressed to find a publishing house that would be thrilled about one of its authors doing so in public), those seeking to break into the biz cannot. It’s just not smart marketing to avoid thinking about who your target reader is, why your book will appeal to him or her, and how your book will satisfy an already-existing group of book-buyers’ literary tastes and/or interests in a manner that nothing else on the market currently does.

Obviously, in order to answer those questions, a writer is going to have to learn something about who is reading books like hers already and why. Sensing a pattern here?

Third, and most important for revision purposes, it’s vital to recognize that what the writer takes away from any given scene or paragraph might not be what a reader takes away – or what a reader who does not know the writer personally would glean from it. If the action on the page is confusing to a reader — especially if that reader happens to be an agent, editor, or contest judge — it’s the writer’s responsibility to clarify the writing, not the reader’s to figure out what is going on. Especially if that would mean going back and re-reading the sentences in question; Millicent simply doesn’t have time to do that.

I feel an editing axiom coming on: if a reader finds a passage unclear, it does not matter that the writer can explain glibly what’s going on; the reader can judge only what’s actually on the page.

This is especially important precept to bear in mind if you are editing for humor. All too often, aspiring humorists proceed upon the assumptions that

(a) anything that makes them laugh is inherently funny,

(b) anything that makes their kith and kin laugh is funny,

(c) any anecdote they have ever told out loud and elicited a chuckle is funny, and/or

(d) any reader will find writing based on assumptions (a)-(c) funny.

All of these are palpably untrue, as Millicent the agency screener would be only too happy to tell you, and she should know: humor that doesn’t quite work on the page shows up in submissions so often that it has become one of her pet peeves. It’s also untrue that

(e) having a character laugh at something either he or another character has just said will render it funny to a reader.

That’s likely to come as a surprise to all of those submitters who tried to convince Millicent that their protagonist was the next Hawkeye Pierce by depicting bystanders roaring with laughter at his antics and quips. This exceedingly pervasive professional readers’ pet peeve tends to run a little something like this:

Bored with the lesson, Chuck glanced out the window, searching for amusement. He leap to his feet. “Look, Miss McStraightlacedson! A tiger’s escaped from the zoo!”

Half the class ran to the window while he leaned back in his chair, grinning while his classmates searched for a beast that existed only in his imagination. His friends leaned forward on their desks, cracking up at how gullible the others were.

The teacher alone had not budged. “Back to your seats, everyone. I’m afraid Mr. Hilariouskid has been putting us on again.”

Several boys slapped him on the back as they regained their seats. “That was a good one, Chuckles!” Mopey Wanabefunny cried.

A professional reader’s response to this subtle giggle-prompting tactic is seldom laughter, I’m sorry to report, but eye-rolling. Most often, accompanied by, “Next!”

In other words, it might make Millicent laugh, but not for the right reasons.

While we’re talking about editing for humor, did you catch the other problem with this passage? Hint: the writer probably thought this made this scene’s hilarity clearer, but from the reader’s perspective, it watered down the joke.

If you immediately leapt out of your chair, yelling, “I know the answer, Miss McStraightlacedson! The narrative over-sold the joke,” allow me to hand you the Milton Berle Award; feel free to hang onto it for a while. While the old writing truism that brevity is the soul of wit is not always accurate (as anyone who has ever enjoyed a shaggy dog story can attest), explaining to the reader after the fact why something is humorous almost always renders it less amusing.

As we discussed earlier in this series, this kind of overkill also has another side effect: to a professional reader like Millicent, it indicates some doubt in the writer’s mind that the situation itself is funny enough to prompt laughter without the explanation, which in itself raises a question about its humor value. Basically, it’s a sign that the writer doesn’t trust the reader to get it.

In my experience, though, most of the writers who fall into this trap do so not because they are thinking poorly of their audience’s reading comprehension skills, but because they are not thinking of the reader at all. Something strikes the writer as amusing — so it must be so to the reader, right?

Frequently, no. If it isn’t, the text’s going on to tell the reader why something that hasn’t been shown to be funny should make her laugh is not going to help.

Don’t believe me? Okay, here is that scene again, with the laughter prompts excised, as well as the explanation; while I’m at it, I’m going to change the too-obvious character names as well. Judge for yourself whether the humor doesn’t stand up better.

Bored with the lesson, Charles glanced out the window. He leap to his feet. “Look, Miss Bates! A tiger’s escaped from the zoo!”

Half the class ran to the window. Only a pellucidly blue sky and well-kept lawns greeted them.

The teacher alone had not budged. “Back to your seats, everyone. And you, Mr. Spencer, will report for detention after…Mr. Spencer? Where are you?”

Even the kids who hadn’t rushed to see the tiger screamed. All that remained of Charles was a red-stained tennis shoe occupying his chair.

While his classmates wept and Miss Bates dashed to the principal’s office, Charles walked whistling down the path to the river. Fishing was a much better use of a sunny day than learning about how Hannibal crossed the Alps.

Come on, admit it — you weren’t expecting one new plot twist, were you, much less two? The unexpected is often funny on the page. So much so that if I were editing this piece, I might recommend that the last paragraph be beefed up with another surprise.

While his classmates wept and Miss Bates dashed to the principal’s office, Charles walked whistling down the path to the river. Fishing was a much better use of a sunny day than learning about how Hannibal crossed the Alps. As he slipped through the hedge and off school grounds, he heard a low growl behind him, the faint sound of padded feet.

Whether the pursuer turns out to be a tiger or Miss Bates teaching him a lesson, you must admit, the revised version is quite a bit more amusing than the original. In the second, the writer trusts the reader to be able to follow what’s going on AND to have a sense of the absurd.

Should the writer have explained that Charles reddened his shoe with the ketchup packets he always kept concealed in his desk? Possibly, but not necessarily. If the reader already knew from an earlier scene that the boy believed in being prepared in case any stray hot dogs might find their way to his desk, smuggled from the lunchroom (oh, that rapscallion!), the joke would fly just fine without it. Ditto if we’d already seen him brandishing a red Magic Marker or dabbing a cut with iodine.

There is, in short, no single, hard-and-fast editing rule dictating the right amount of set-up for humor. It all depends on the situation — and the target audience.

Why bring any of this up while either author interviews or revision are on our collective mind? Simple: not taking your reader’s likely response into account renders pulling off either well quite a bit more difficult. A writer who thinks only of his own reaction to what’s on the page tends to overlook clarity problems, logical leaps, redundancy, and anything else that didn’t strike him as important when he composed the passage.

He also is inclined not to consider the reader’s enjoyment — and that’s a real drawback, as far as Millicent is concerned. As we’ve seen in this series on structural repetition, it’s not nearly as much fun to read prose that’s repetitive in sentence structure or vocabulary as writing that’s more varied.

Because writing is a solitary art — yes, even after one lands an agent and sells one’s book to an editor — it’s astonishingly easy to lose sight of the end reader, particularly in the revision stage. When we writers are up on our high horses, we tend to talk about our artistic visions and the importance of being true to our voices, but while we’re being down-to-earth about it, we have to admit that if we can’t (or won’t) take the time to make those visions and voices accessible to the reader AND at least somewhat pleasant to read, we aren’t completing our mission successfully.

Does that mean dumbing down complex concepts or compromising original voices? No, not if revision is performed intelligently. It does mean, however, that the writer of a Frankenstein manuscript owes it to any complex concept that might be lingering with in it, as well as to her own narrative voice, to try to read the text as a reader might.

An author reading I attended last year provided a glorious pragmatic illustration of the necessity for a good reviser (or good writer, for that matter) to consider not only his own point of view when deciding whether a passage of text was clear, but also a reader’s. As is lamentably often the case at such readings, the author read excerpts from her book in a monotone, without once lifting her eyes from the page to connect with her audience.

The result, unsurprisingly, was that her gorgeous prose fell flat. The characters blurred together; the dramatic arc of the scene was lost; the quite amusing punch line failed to invoke even a single smile in an audience member. A great and preventable pity, because the scene she chose to read was well-written, beautifully paced, and contained some genuinely astonishing plot twists.

As if the muses had gone out of their way to demonstrate to this author just how much she was underselling her own excellent prose stylings, the venue had booked a second author to read at the same event, one whose obviously well-rehearsed, excitingly voiced reading, punctuated by frequent merry glances up at her fans, kept the crowd enthralled. Guess which author sold more books?

Now, I have nothing but sympathy for the shy; I happen to enjoy public speaking, but I know that it positively terrifies many. Reading one’s own work in public is hard, so I would STRENUOUSLY recommend that any and all of you who intend to see your work in print some day start practicing reading it in front of others as soon as humanly possible. Reading well out loud is something that few of us manage the very first time we try, after all.

Like so many other skills required of a professional writer, giving good public readings is a learned skill, one that requires practice to perfect. It also requires — you saw this coming, didn’t you? — the writer to take the time to consider what that passage of perfect prose might sound like to someone who, unlike herself, might not have read it before.

I’ve said it before, and I shall no doubt say it again: a writer’s ability to step outside his own head and consider what’s actually on the page, rather than what he thinks is on the page, is crucial to good revision.

Case in point: the question we have been discussing over the last couple of posts, the delicate balance between referring to characters by name often enough for clarity, but not so much that all of those capital letters distract the reader’s eye and prompt Millicent to grope for the form-letter rejection stack. This is a problem that’s not likely to trouble the sleep of a writer who doesn’t think much about what her readers might be taking away from any particular page of his story, right?

In fact, the very question might strike him as just a little bit stupid. “Why, I should have thought that was obvious,” he would huff.

If the writing on that page is clear, his intended meaning may well be obvious. If not, his submission could well end up confusing Millicent — or, still worse, expecting her to fill in gaps in logic, background scenery, character motivation…

You know, all of those thrilling, character- and plot-revealing details that we talk about so much here at Author! Author! as the hallmark of expressive prose. Millicent’s on the lookout for style, recall, not just a gripping story. If she — or any reader, for that matter — has to devote even a few seconds of her scant time with your submission to sorting out confusing logistics, unclear character motivations, or just plain trying to figure out what’s going on, that’s a few less seconds she is spending noticing how likable your protagonist is and how gracefully you describe cloud patterns.

I couldn’t help but notice that not all of you immediately shouted, “Right, by Jove!” Does it strike you as a trifle hostile to literature that our Millie tends to concentrate far more on a submission’s faults than its beauties? Okay, let’s step into in her practical two-inch heels for a moment, and consider the strengths and weaknesses of the kinds of manuscripts we’ve been discussing.

Got your Millicent cap firmly pulled down around your ears? Excellent. Picture four manuscripts before you, each written by a talented writer eager for a break. Which one will you decide to show to your boss, the bigwig agent, and which three will you reject?

Your choices are (1) a narrative that assumes you will put in extra effort to sort out what is going on in certain confusing passages, like so:

He woke up with her hair in his mouth. She rolled sideways. Trees swayed outside the unfamiliar window, giving him no clue of his whereabouts. Ow — his knee! He pulled on his boots.

(2) A submission that just summarizes the story, leaving you to fill in most of the details, rather than providing interesting and surprising specifics from which you might derive your own impression of what’s going on, thus:

Bart woke up dazed, disoriented, under what seemed to be a pouf of somebody else’s hair. There was a girl next to him; for the life of him, he could not remember her name, nor did the trees swaying outside the window give him any clue about where he was. His knee hurt, as if something had smashed against it recently. He had to get out of there. He crept out of bed, pulled on his boots, and left.

(3) the most extreme form of Frankenstein manuscript, one so rife with spelling, grammar, perspective, and consistency problems that even its author appears not to have taken the time to read it all the way through:

But, I wake up with her hair in his mouth. She rolled sideways, pearing at the unshaven face near to her foot. No help there so quite as a mouse, I syruptitiously looked at the trees outside the window, but they didn’t tell me where I had managed to get myself to. Something had cracked against his knee. Where had those darned boots gotten to, and who was this girl anyway?

(That one was genuinely hard for me to write, by the way; I kept having to undo my instinctive corrections.)

(4) A manuscript where the writer has taken the reader’s perspective into account sufficiently to clarify all of the relevant issues of the page, skillfully using a plethora of vivid details to convey to the reader a complex reality and consistent enough in tone that you can discern, however faintly, an individual authorial voice:

Bart woke up gasping for breath. Was he being smothered under a fuzzy scarlet blanket, or had his bangs grown down to his mouth, choking him with a lamb-like pouf of curly hair? Wait — his hair hadn’t been curly since he had been the spelling champion of Mrs. Chellini’s third-grade class. His dim memories of her classroom seemed like Technicolor spectaculars, compared to his recollection of last night.

He yanked a particularly wavy red lock from the corner of his mouth, following it gingerly — better not move too much, head — across the rough Navaho blanket to its source. The mascara-streaked face wasn’t familiar, but the Hooters t-shirt was. Tammy, maybe? Tina? And was that blood on his bare knee? No wonder it hurt: that gash would need stitches.

Tell me, Millicent-for-a-day: which would you choose to pass on to your boss, and which would you reject?

There’s nothing wrong with expecting your reader to draw conclusions from what you say on the page, but as some well-meaning English teacher may have pointed out to you once or twice in the past, style often lies in the essential difference between showing and telling. If the writer chooses to beguile the reader with enough details about a situation that he walks away from the scene with the mental image the author intended, that’s showing. If, on the other hand, the writer elects to tell her tale in generalities, or to spell all of the necessary conclusions for the reader instead of allowing the reader to draw them for himself, that’s telling.

Of course, to write a complex tale, you’re probably going to have to do both. Let’s face it, telling can be quite useful from time to time, particularly in a fast-paced action scene or a chunk of narrative that needs to cover a hefty chunk of passing time. More often than not, however, writers use summary statements as a kind of shorthand writers to get past activities that are necessary to the plot, but just don’t interest them that much.

Which brings me, conveniently enough, to one of the most commonly over-used verbs in manuscript submissions — and, not entirely coincidentally, to one of Millicent’s lesser-known pet peeves. Contest judges complain vociferously about it, too, so I could not in good conscience polish off our discussion of textual redundancy without talking about it. Not that I mind: this particular phenomenon is a favorite bugbear of mine as well, because its astonishingly pervasive use tends, in my experience, to flatten description and characterization.

Have I piqued your curiosity sufficiently yet? Too bad — you’re going to have to wait until tomorrow’s post to find out what this classic Millicent-annoyer is. I know what I’m talking about here, and that’s enough for now.

See how frustrating it is when the writer considers only what she needs to get out of the words on the page, rather than her readers’ desire to know what’s going on? And have I given you strong enough evidence of the point I made yesterday, that false suspense — withholding information from the reader purely for the sake of building suspense — is darned annoying?

My work is done here for the day, clearly. Tune in next time for a few last concrete examples of Millicent-irritants before Pitchingpalooza begins on Wednesday. In the meantime, remember your readers, and keep up the good work!

Pet Peeves on Parade, part XXIX, and Structural Repetition, part VI, and bears, oh my! And other run-on sentences of note. And anything else that might occur to me to include.

Sick of structural repetition yet, campers? Excellent: you’re starting to gain a sense of how Millicent the agency screener and the rest of us who read for a living feel about it.

Oh, you think I’m kidding? Those of use who have been at the manuscript game for a while tend to have negative reaction to it that borders on the visceral. At the end of a long, hard day — or week, or month, or lifetime — of watching manuscripts get caught up in the insidious allure of and to make even the simplest run of short sentences sound interconnected and chatty, just like the run-ons that plague everyday speech, most of us would be perfectly happy never to see a conjunction again.

Okay, so we tend to get over it by the next day. Then what do you think happens? We’re greeted by another manuscript penned by some well-meaning and probably talented soul laboring under the misconception that a narrative voice must sound like somebody who’s had eight cups of coffee by 9 a.m.

Make that someone rude who’s had eight cups of coffee by 9 a.m. There’s just no getting that pushy narrator to pause for breath — or a period. Perhaps unsurprisingly, this run-on dominated style is especially common in first-person narratives:

I was walking down the street, and I saw a car drive by. Not just any car, mind you, but a red, white, and blue car with magenta trim and violet and gold rims. And then, just when I thought my eyeballs could take no more searing, a truck drove up and I looked at it: a two-ton mauve beauty with chartreuse bucket seats, a scarlet grill, and neon yellow racing stripes.

I stopped and stared. Who wouldn’t?

Makes some sense, right? The character narrating the piece is a non-stop talker; the constant forward impulse of all of those ands conveys that. Clearly, what we see on the page is what the narrator would sound like in real life.

A rather literal interpretation of narrative voice — and, perhaps because so many people are hyper-literal, a radically overused device — but justifiable. You’d be astonished, though, at how often third-person narratives — which, although they may follow a single character closely, are seldom attempts to echo an individual’s speech pattern — fall into a similar cadence.

Why is that a problem? Let’s allow those cars to take another pass by our hero.

George was walking down the street, and he saw a car drive by. Not just any car, but a red, white, and blue car with magenta trim and violet and gold rims. And then, just when he thought his eyeballs could take no more searing, a truck drove up and he looked at it: a two-ton mauve beauty with chartreuse bucket seats, a scarlet grill, and neon yellow racing stripes.

George stopped and stared. Who wouldn’t?

Doesn’t work as well, does it? In this version, those run-ons come across as precisely what they are: not a reflection of an individual’s speech patterns, but rather repetitively-structured writing. And, unfortunately for the writer responsible for these immortal words, repetitive in a manner that our old pal, Millicent the agency screener, is likely not only to find repetitive on this page, but across half of the manuscripts she screens today.

Given the unfortunate ubiquity of this structure, a reasonable submitter might conclude that Millicent’s sensibilities would get blunted after a while, but in practice, quite the opposite is true. If anything, most professional readers become more sensitive to word, phrase, and structural repetition over time. So if the ands in question have rampaged all over page 1 of a submission — or even, heaven help us, a query letter — we shouldn’t be tremendously surprised if Millicent reverts to the most over-used word in her vocabulary?

That’s right, campers: “Next!”

Honestly, it’s hard to blame her. Seeing the same phenomenon rampage across submission after submission, one does start to wonder if every sentence structure other than this happened and that happened and then we did this, that, and the other thing was wiped off the face of the earth by an evil wizard. And (see, even I’m doing it now) those of us prone to sympathizing with good writers everywhere can easily become depressed about that, because the ubiquitous use of run-ons can make otherwise quite polished writing seem in a submission like, well, the rest of what we see.

“Oh, talented writer who appears not to read his or her own work very often in hard copy,” we moan, startling onlookers and fellow coffee shop habitués, “why are you handicapping your voice so? It would be understandable — if a bit predictable — if you were writing a first-person narrative, especially if it is YA, but in this close third-person narrative, why cram so many disparate elements into a single sentence? If only you would give the ands a rest and vary your sentence structures more, your voice would be much more enjoyable to read.”

I’m telling you: it’s a tragedy — all the more so because so many aspiring writers are not even aware that this plague afflicts their manuscripts. For every voice-constructor makes a conscious authorial choice to incorporate conversational run-ons to ramp up the narrative’s chatty verisimilitude, there seem to be ten who just don’t notice the ands piling up .

Purposeful or not, the results still aren’t pretty, as far as Millicent is concerned. Any reasonably busy professional reader sees and in print so often that she might as well have that WANTED poster above plastered on her cubicle wall.

And‘s crime? Accessory to structurally repetitive prose. As we have seen close up and personal in my last few posts, too great an affection for this multi-purpose word can lead to run-on sentences, dull action sequences, and contracting nasty warts all over one’s kneecaps.

Well, perhaps not the last, but let’s face it: no other individual word is as single-handedly responsible for text that distracts the eye, enervates the mind, and wearies the soul by saying different things in more or less the same way over and over and over again on the page. Yet on the individual sentence level, the problem may not be at all apparent.

Don’t believe me? Okay, let’s take a look at the issue both in isolation and at the paragraph level.

Bernadette had her cake and ate it, too.

Standing alone, there’s nothing inherently wrong with this sentence, right? Most self-editors would not even consider excising it. Solitude, however, tends not to be this structure’s writer-preferred state. A perennial favorite in both submissions and contest entries, the X happened and Y happened sentence structure all too often travels in packs.

Yes, like wolves. Here’s what the mob tends to look like in its natural habitat:

Bernadette had her cake and ate it, too. Jorge ate what was left of her cake and then went out and baked his own. He believed it to be good, tasty, and yummy. After having tried his cake and found it untoothsome, unpalatable, and generally inedible, Frankenstein’s monster broke into his apartment and destroyed his oven.

“I’m stopping him,” the monster told reporters, “before he bakes again.”

See the problem? No? Okay, let’s look at that first paragraph again as Millicent might:

Bernadette had her cake AND ate it, too. Jorge ate what was left of her cake AND then went out AND baked his own. He believed it to be good, tasty, AND yummy. After having tried his cake AND found it untoothsome, unpalatable, AND generally inedible, Frankenstein’s monster broke into his apartment AND destroyed his oven.

Like any sentence structure that appears too often within a short run of text, this type of sentence to bore the reader after a while, even if the subject matter is inherently interesting — and yes, Virginia, even if every sentence in the passage isn’t put together in precisely the same way. That’s and‘s fault, you know; when too many of them appear on a page, even the untrained eye starts unconsciously counting them up.

Seven, by the way. And two in the last paragraph of explanation — which also boasted two evens, in case you’re interested.

That’s not to say, naturally, that the X happened and Y happened sentence structure doesn’t have some legitimate uses. Let’s face it, it’s darned useful, providing a quick way to inform the reader of quite a bit of action in a short amount of text. Instead of having to write a brand-new sentence for each verb with the same subject, all of the action can be presented as a list, essentially. That can be especially handy if the individual activities mentioned are necessary to plot, characterization, or clarity, but not especially interesting in and of themselves.

Weary from a long day at work, Ambrose sat down and removed his heavy steel-toed boots.

Nothing wrong with that, right? The reader doesn’t need to spend two sentences mulling over Ambrose’s rather predictable post-workday actions. Now, while we’ve got our revision spectacles on, we could debate from now until next Tuesday whether the reader actually needs to be told that Ambrose sat down — not exactly a character-revealing move, is it? — but that’s a matter of style, not proper presentation. Technically, this is a perfectly legitimate way to convey what’s going on.

You’d be astonished, though, how often aspiring writers will treat even quite a thrilling string of events in this manner, purely in the interest of telling a tale rapidly. This tactic is particularly popular amongst synopsis-writers trying to compress a complex plot into just a page or two. Like so:

AMBROSE MERCUROCROME, JR. (27) comes home from work one day, removes his steel-toed boots, and discovers that the third toe on his left foot has transformed into a gecko. He cuts it off in a panic and takes it to a veterinarian, DR. LAO (193). Dr. Lao examines the gecko-toe and determines it has the capacity to knit exquisite sweaters. He and the gecko kill AMBROSE, go into business together, and soon take the skiwear market by storm.

Not the most scintillating way of describing the plot, is it? The repetitive structure gives the impression that none of these potentially quite exciting plot developments is important enough to the story to rate its own sentence. Obviously, that’s a problem in a synopsis, where the goal is to present the story you’re telling as interesting and exciting.

Perhaps less obviously — brace yourself, and-lovers; you’re not going to like this — this structure can create a similarly dismissive impression on a manuscript page. Not to be telling stories out of school, but skimming eye like You-Know-Who’s will has been known note only the first verb in a sentence and skip the rest.

Before any and-hugger out there takes umbrage at the idea of every sentence in his submission or contest entry’s not getting read in full, let’s take a moment to think about verb-listing sentences from Millicent’s perspective — or, indeed, any reader’s. If an action is not crucial enough to what’s going on for the writer to devote an entire sentence to it, why should we assume that it’s important to the scene?

I sense some squirming out there. “But Anne,” some of you and partisans hasten to point out, “while I admit that sometimes I lump a bunch of activity together in a few short, list-like sentences in order to speed things up a bit, that’s not the primary way I use and in my prose. As you yourself have mentioned, and not all that long ago, stringing together sentences beginning with but or yet, it creates the impression conversation-like flow. Isn’t that essential for a convincing first-person narrative?”

At the risk of repeating myself, partisans, echoing recognizable speech patterns is only one technique for constructing a plausibly realistic first-person narrative voice. There are others; this is simply the easiest. It would be hard to deny that

I woke up the next morning and poisoned my husband’s cornflakes.

is chatty, casual, echoing the way your local spouse-poisoner is likely to describe her activities to her next-door neighbor. True, it doesn’t quite match the arid eloquence of Ambrose Bierce’s

Early one June morning in 1872, I murdered my father — an act which made a deep impression on me at the time.

But then, what does?

You would not be alone, then, if you feel that the heavy use of and is downright indispensable in constructing dialogue or a first-person narrative. (Just ask Millicent how often she sees it on any given day of submission-screening.) Many a living, breathing, conversation-producing person does incorporate the X happened and Y happened structure into her speech with great regularity.

In many cases, with monotonous regularity. Certainly, it can feel awfully darned monotonous to the reader, if it appears on the printed page with anywhere near the frequency that it tumbles out of the average person’s mouth.

Don’t believe me? Okay, try walking into any public place with an abacus and moving a bead every time you hear somebody use and. Better get some training on how to use that abacus quickly, though; your total is going to be up in the thousands before you know it.

Yes? Do those of you who have been following this series have anything you’d like to add here? Perhaps the observation that no matter why a word, phrase, sentence structure, and/or narrative device appears over and over again within a short span of text, it’s likely to strike a professional reader as repetitive?

No? Were you perhaps thinking of my oft-repeated axiom that just because something happens in the real world doesn’t necessarily mean that a transcript of it will make compelling reading?

Despite the sad fact that both of these observations are undoubtedly true, few real-world patterns are as consistently reproduced with fidelity in writing as everyday, mundane verbal patterns. Sociological movements come and go unsung, jargon passes through the language literarily unnoted, entire financial systems melt down without generating so much as a mention in a novel — but heaven forfend that everyday redundant or pause-riddled speech should not be reproduced mercilessly down to the last spouted cliché.

And don’t even get me started on the practically court-reporter levels of realism writers tend to lavish on characters who stutter or — how to put this gracefully? — do not cling tenaciously to the rules of grammar when they speak. In some manuscripts, it seems that if there’s an ain’t uttered within a five-mile radius, the writer is going to risk life and limb to track it down, stun it, and pin it to the page with quotation marks.

Again, I’m not saying that there aren’t some pretty good reasons underlying this impulse. Many aspiring writers consciously strive for prose that echoes the kind of conversational rhythms and structures one hears every day, particularly when they are penning first-person or present-tense narratives.

“I want it to sound real,” they say with engaging earnestness. “My goal is to hold, as ’twere, the mirror up to nature.”

Unfortunately, from Millicent’s perspective, most of these writers don’t realize just how widespread this particular goal is — or that much real-life conversation would be either deadly dull, logically incoherent, or at minimum not literarily interesting transferred directly to the printed page. Real-life speakers repeat both words and sentence structures to an extent that would make even the most patient reader rip her hair out at the roots in frustration.

And I’m talking arm hair here, people. If you doubt the intensity of this reaction, here’s a little experiment:

(1) Sit in a crowded café for two hours, jotting down the conversations around you verbatim.

No fair picking and choosing only the interesting ones; you’re striving for realistic dialogue, right?

(2) Go home and type up those conversations as scenes, using only the dialogue that you actually overheard.

No cheating: reproduce ALL of it.

(3) Wait a week.

(4) Seat yourself in a comfy chair and read the result in its entirety.

If you can peruse the result without falling into a profound slumber, congratulations! You have an unusually high threshold for boredom; perhaps you have a future as an agency screener. Or maybe you have cultivated an affection for the mundane that far outstrips that of the average reader.

How can you tell if you have roughly the same redundancy tolerance as most reader? Did you find yourself reaching for the nearest ice pick with the intention of self-destruction within five pages?

And if your fingers start itching not for that ice pick, but for a pen to write some acidic commentary on the subject of the inadvisability of boring one’s audience with gratuitous word repetition, have you considered a career in publishing? Millicent was reaching for that pen before she graduated from middle school.

I was reaching for it before I could walk. One of the most beloved Mini family anecdotes concerns my correcting a dinner guest’s grammar from my high chair. His spoken grammar.

But enough about me. Let’s get back to that test.

(5) Ask yourself honestly: does the dialogue you overheard have any entertainment value at all when reproduced in its entirety? Or are only selected lines worth preserving — if, indeed, any lines deserve to be passed down to posterity at all?

Even if you are lucky enough to stumble upon an unusually witty group of café denizens, it’s highly unlikely that you would be able to get the result past Millicent, either as dialogue or as narrative. In professional writing, merely sounding real is not enough; a manuscript must also be entertaining enough to hold a reader’s interest.

Yes, Virginia, even if the manuscript in question happens to be literary fiction, if it’s book-length. Most of what goes on in the real world, and nearly everything that’s said, doesn’t rise to the standards of literature.

Not of good literature, anyway. And that’s as it should be, as far as I’m concerned.

There’s more to being a writer than having adequate transcription skills, after all; merely reproducing the real isn’t particularly ambitious, artistically speaking. Think about it: wouldn’t you rather apply your unique worldview and scintillating ability with words to create something better than reality?

In that spirit, let’s revisit that sentence structure beloved of the real-life speaker, X happened and Y happened and see if we can’t improve upon it. Why, here’s an example of it wandering by now.

Ghislaine blanched and placed her lily-white hand upon her swiftly-beating heart. Roland nodded with satisfaction and strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously and continued to move closer.

Did it bug you that time? Each of these sentences is in fact grammatically correct, and this structure reads as though it is merely echoing common spoken English. It’s also pretty much the least interesting way to present the two acts in each sentence: the and is, after all, simply replacing the period that could logically separate each of these actions.

By contrast, take a look at how varying the sentence structure and adding the odd gerund livens things up:

Ghislaine blanched, her lily-white hand clutching her swiftly-beating heart. Roland strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously, moving closer every second.

Easier to read, isn’t it? Admittedly, the prose is still pretty purple — or at least a blushing lilac — but the paragraph is no longer jumping up and down, crying, “My author knows only one way to structure a sentence! Run, Millicent, run, or you’ll be driven mad by page 42!”

Good advice, bellowing paragraph, but your assessment is rather generous: most pros would be driven mad within a page, particularly if that page happens to be page 1. We tend to have a very low tolerance for over-use of this particular sentence structure. Seriously, I’ve seen pens poked through manuscripts at the third instance of this kind of sentence within half a page. Screaming has been known to ensue after the sixteenth use within the same space.

If that seems like an over-reaction, consider this: most professional readers go into the job because they like to read. Adore it. Can’t get enough of lovely prose. Lest we forget, people who work at agencies are individuals with personal preferences, rather than the set of automatons sharing a single brain that many aspiring writers presume them to be. I can guarantee, however, that they all share one characteristic: they love the language and the many ways in which it can be used.

What does that mean in practice, you ask? Millicent screens manuscripts all day at work, pulls a battered paperback out of her bag on the subway home, and reads herself to sleep at night; her boss totes submissions back and forth on that same subway because he’s so devoted to his job that he does half of his new client consideration at home. And no matter how many manuscripts they reject in a given week, both wake up each and every day hoping that today, at last, will bring an amazing manuscript into the agency, one to believe in and shepherd toward other lovers of good literature.

With such an orientation, it’s genuinely frustrating to see a great story poorly presented, or an exciting new voice dimly discernible through a Frankenstein manuscript. Or — and this happens more often than any of us might care to think — when a talented writer was apparently in such a hurry to get a scene down on paper that a series of potentially fascinating actions degenerated into a mere list that barely hints at the marvelous passage that might have been.

“But Anne,” and-huggers everywhere cry, “I just love the charge-ahead rhythm all of those ands impart to a passage! If the writing is strong enough, the story gripping enough, surely a literature-lover like Millicent would be able to put her repetition reservations aside?”

I see that it’s time to get ruthless: I’m going to have to show you just how much damage an injudicious application of ands can inflict upon even the best writing. To make the lesson sting as much as possible, let’s resurrect an example I used a week or two ago, the exceptionally beautiful and oft-cited ending of F. Scott Fitzgerald’s THE GREAT GATSBY. To refresh your memory:

And as I sat there brooding on the old, unknown world, I thought of Gatsby’s wonder when he first picked out the green light at the end of Daisy’s dock. He had come a long way to this blue lawn, and his dream must have seemed so close that he could hardly fail to grasp it. He did not know that it was already behind him, somewhere back in that vast obscurity beyond the city, where the dark fields of the republic rolled on under the night.

Gatsby believed in the green light, the orgiastic future that year by year recedes before us. It eluded us then, but that’s no matter — tomorrow we will run faster, stretch out our arms farther… And one fine morning–

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

Even before I finished typing this, I could sense hands shooting up all over the ether. “Aha, Anne! He began two sentences with and! And he used the very X happened and Y happened structure you’ve been complaining about. So I may use both with impunity, right?”

No, actually — I selected this passage precisely because he does incorporate them; he also, you will notice, uses the passive voice in one sentence. He does both sparingly, selectively.

Look at the horror that might have resulted had he been less variable in his structural choices. (I apologize in advance for this, Uncle Scott, but I’m making a vital point here.)

And I sat there brooding on the old, unknown world, and I thought of Gatsby’s wonder when he first picked out the green light at the end of Daisy’s dock. He had come a long way to this blue lawn, and his dream must have seemed so close that he could hardly fail to grasp it. He did not know that it was already behind him, and that it was somewhere back in that vast obscurity beyond the city, and it was where the dark fields of the republic rolled on under the night.

Gatsby believed in the green light, and in the orgiastic future that year by year recedes before us. And it eluded us then, but that’s no matter — tomorrow we will run faster and we will stretch out our arms farther… And one fine morning–

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

The moral: even when the writing is very good indeed, structural repetition can be distracting. (Take that, writers who believe that they’re too talented for their work ever to require revision.)

Where might one start to weed out the ands, you ask? Glance over your pages for sentences in which and appears more than once. Chances are high that such a sentence will be a run-on — or a too heavily burdened list.

Not sure that you’ll be able to spot them in the wild? Here is a classic run-on — too much information crammed into a single sentence, facilitated by those pesky conjunctions.

In avoiding the police, Babette ran down the Metro stairs and out onto the platform and into the nearest train.

And here is a description crammed into list form:

Zorro scanned the house, admiring its inventive decorative scheme. Its attractive red lintels, inviting purple door, and Robin Hood green roof demanded the attention of passers-by, while its white-and-orange checked kitchen curtains seemed to promise that pies would be cooling beneath them soon and sultry sheers wafted from the bedrooms on the second floor, offering (in the chaste realm of thought, at least) the imaginative onlooker a suggestion for what to do until the pies cooled. Not that the view from the street gave an impression of relaxation: the lawn was manicured and the hedges were clipped and shorn; even the small and compact doghouse was shipshape and freshly painted.

Interesting use of detail, but why on earth stuff so much description into so few sentences? What’s the narrator’s hurry? And is it really a good idea to preface such a hastily thrown-together image with an announcement to Millicent that what is about to be described is inventive?

She’s like to make up her own mind about that, thank you very much. But trust me, by the middle of the second sentence, she will already be asking herself, “Wasn’t there another, more interesting way the writer could have conveyed this information? If not, is are all of these details even necessary?”

Some writers, of course, elect to include run-on sentences deliberately in their work, for specific effect: to make the narrator sound less literate, for instance, or more childlike, or to emphasize the length of a list of actions the protagonist has to take to achieve a goal. Or sometimes, the point is to increase the comic value of a scene by the speed with which it is described, as in this excerpt from Stella Gibbons’ immortal comedy, COLD COMFORT FARM:

He had told Flora all about his slim, expensive mistress, Lily, who made boring scenes and took up the time and energy which he would much sooner have spent with his wife, but he had to have Lily, because in Beverly Hills, if you did not have a mistress, people thought you were rather queer, and if, on the other hand, you spent all your time with your wife, and were quite firm about it, and said that you liked your wife, and, anyway, why the hell shouldn’t you, the papers came out with repulsive articles headed “Hollywood Czar’s Domestic Bliss,” and you had to supply them with pictures of your wife pouring your morning chocolate and watering the ferns.

So there was no way out of it, Mr. Neck said.

Quite the sentence, eh? (Not the second, silly — the first.) I’m going to part company with pretty much every other editor in the world for a moment and say that I think that a writer can get away with this sort of run-on every once in a while, under three very strict conditions:

(1) if — and only if — it serves a very specific narrative purpose that could not be achieved in any other manner (in this example, to convey the impression that Mr. Neck is in the habit of launching into such diatribes on intimate topics with relative strangers at the drop of the proverbial hat),

(2) if — and only if — it achieves that purpose entirely successfully (not a foregone conclusion, by any means), and

(3) if — and only if — the writer chooses to do this at a crucial point in the manuscript, s/he doesn’t use it elsewhere, or at least reserves the repetition of this choice for those few instances where it will have the greatest effect.

Why minimize it elsewhere? As we saw in that last example, this device tends to create run-on sentences with and…and…and constructions, technical no-nos. You may be doing it deliberately, but as with any grammatical rule, many writers who do not share your acumen with language include them accidentally.

Why might that prove problematic at submission time? Well, Let me ask you this: how is a speed-reading Millicent to tell the difference between a literate submitter pushing a grammatical boundary on purpose and some under-read yahoo who simply doesn’t know that run-ons are incorrect?

Usually, by noticing whether the device appears only infrequently, which implies deliberate use, or every few lines, which implies an ingrained writing habit. Drawing either conclusion would require our Millie to read a significant chunk of the text.

Obviously, that would take quite a bit more time than shouting, “Next!”

I’ve been sensing disgruntled rumblings out there since point #3. “But Anne, I read a great deal, and I see published literary fiction authors break this rule all the time. Doesn’t that mean that the language has changed, and people like you who go on and on about the rules of grammar are just fuddy-duddies who will be first up against the wall come the literary revolution?”

Whoa there, rumblers — as I believe I may have pointed out before, I invented neither the rules of grammar nor the norms of submission evaluation. If I had, every agency and publishing house would post a clear, well-explained list of standard format expectations on its website, along with explanations of any personal reading preferences and pet peeves its staff might happen to be cherishing. Millicent would be a well-paid, under-worked reader who could spend all the time she wanted with any given submission in order to give it a full and thoughtful perusal; the agent for whom she works would be able to afford to take on a difficult-to-market book project every month or so, just because he happens to like the writing, and the government would issue delightful little checks to compensate writers for all of the time they must now spend marketing their own work.

As simple observation will tell you that these matters are not under my personal control, kindly take me off your literary hit lists. Thank you.

No, but seriously, folks, even in literary fiction, it’s dangerous to include grammatically incorrect sentences in a submission — to someone who hasn’t read more of your work than the first few pages of your manuscript, it’s impossible to tell whether you are breaking the normal rules of grammar in order to create a specific effect, or because you just don’t know the rule. If an agency screener concludes that it’s the latter, she’s going to reject the manuscript, almost invariably.

Then, too, the X happened and Y happened structure is just not considered very literary in the business. So the automatic assumption if it shows up too much is that the material covered by it is to be read for content, rather than beauty of prose.

To quote Millicent’s real-life dialogue: “Next!”

Unless you are getting an extremely valuable effect out of a foray into the ungrammatical — and an effect that would impress Millicent with its efficacy at first glance — it’s best to save them for when it serves you best. At the very least, make sure that two such sentences NEVER appear back-to-back.

Why? To avoid that passage appearing to Millicent as the work of — horrors! — a habitual runner-on or — sacre bleu! — someone who does not know the rules of grammar. Or even — avert your eyes, children — as the rushed first draft of a writer who has become bored by what’s going on in the scene and just wants to get that darned set of actions or description onto the page as quickly as humanly possible.

Oh, that diagnosis didn’t occur to you in the midst of that description of the house? Millicent would have thought of it by the second and.

None of these may be a fair assessment of any given sentence in your manuscript, of course. But when you do find patches of ands in your text, step back and ask yourself honestly: “Do I really NEED to tell the reader this so tersely — or all within a single sentence? Or, indeed, at all?”

“Perhaps,” (you’re still speaking to yourself here, in case you were wondering) “I could find a way that I could make the telling more intriguing or unusual by adding more detail? I notice by reading back over the relevant paragraphs that my X happened and Y happened sentences tend to be light on specifics.”

My, you’re starting to think like an editor, reader. A Frankenstein manuscript just isn’t safe anymore when you’re in the room. But would you mind not wielding that ice pick so close to the computer screen?

Since your eye is becoming so sophisticated, take another look at paragraphs where ands abound and consider the opposite possibility: do all of those ands indicate that the narrative is rushing through the action of the scene too quickly for the reader to enjoy it? Are some of those overloaded sentences cramming four or five genuinely exciting actions together — and don’t some of these actions deserve their own sentences?

Or, to put it a bit more bluntly, is the repeated use of and in fact your manuscript’s way of saying COME BACK AND FLESH THIS OUT LATER?

You thought you were the only one who did this, didn’t you? Almost every writer has resorted to this device at the end of a long writing day. Or when we have a necessary-but-dull piece of business that we want to gloss over in a hurry. When the point is just to get lines down on a page — or to get a storyline down before the inspiration fades — X happened and Y happened and Z happened is arguably the speediest way to do it. It’s a perfectly acceptable time-saving strategy for a first draft — as long as you remember to go back later and vary the sentence structure.

Oh, and to make sure that you’re showing in that passage, not telling. Millicent has an ice pick, too.

When time-strapped writers forget to rework these flash-written paragraphs, the results may be a bit grim. Relying heavily on the and construction tends to flatten the highs and lows of a story. When actions come across as parts of a list, rather than as a sequence in which all the parts are important, the reader tends to gloss over them quickly, under the mistaken impression that these events are being presented in list form because they are necessary to the plot, but none is interesting enough to sustain an entire sentence.

Which, I’m guessing, is not precisely the response you want your sentences to evoke from Millicent, right?

Does revising for this tendency require an impeccable attention to detail? You bet it does. But honestly, isn’t there more to your literary voice than a sense of consecutive speech? Doesn’t that inventively-decorated house in your mind deserve a full description? And isn’t there more to constructing a powerful scene than simply getting it on the page before you have to run out the door to work?

Doesn’t, in short, your writing deserve this level of scrutiny? 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!