What Are You Working On?

Paper cutter with toolsTell us about your current writing projects!

Note: Please don’t post more than a few sentences of any given piece (or paragraphs if it’s book-length) because that could cause your piece to be considered “published.” (Many publishers only want new content and will not consider something that has already been made available to the public. Since this site can be viewed by anyone, it counts. For a more detailed discussion, see this Writer’s Relief article. For bunches of links to even more articles about this topic, see this Write It Sideways post.)

Also, please remember that this site is not meant as a place to get or give critique.

Script Frenzy: Coming Your Way in April

If you like to set big writing goals and then dive in, you might want to check out the Script Frenzy event that runs April 1-30. Script Frenzy is an annual event sponsored by the nonprofit organization the Office of Letters and Light to encourage creative writing.

The goal is to write 100 pages of a screenplay, stage play, graphic novel, or TV script, all within that 30-day time period. If you reach your goal, you get a certificate. You can write a screenplay yourself, or team up with a partner and work on it together. Anyone can participate. There’s even a Script Frenzy Young Writers Program for kids who are 12 or younger, with classroom resources for teachers.

The Script Frenzy website has forums and resources for writers, like links that you can use to see sample scripts. There are also some regional events where you can meet with other writers if you want some company or encouragement. Note that this is a writing event, and the focus is writing, not on how to publish your work.

Thousands of people participate in Script Frenzy each year. There’s no charge, but since it is run by a nonprofit organization, they happily accept donations.

The Rules Disease

Writing Rules

Anyone who seriously tackles the craft of writing is likely to have encountered a writing­ rule, like “Show, Don’t Tell,” or “Never Begin a Sentence with a Conjunction.” “Don’t Split Infinitives” and “Never Head Hop” are also popular. The granddaddy of all of them, “Omit Needless Words,” is deliciously self-explanatory … but the ever baffling “Murder Your Darlings” is a rule so confusing it deserves its own essay.

Writing rules can do a lot of good. For example, “Show, Don’t Tell”—meaning, draw word pictures that create the effects you want, rather than explicitly telling the reader what they should feel—can make your writing more direct, more immediate, and more effective. For example, compare:

The boring professor put Mary to sleep.

with

Professor Smith droned on until Mary’s head thunked onto her desk.

The first version tells you exactly what to think about the professor—he’s boring—and precisely what he did—he put Mary to sleep. The second version has the same information, but it’s no longer explicit: we have to infer that he’s boring from the sound of his voice, and infer that Mary fell asleep from what happened to her head. As that information is delivered, we’re also treated to sounds, images and a physical action, which together create a brief but vivid scene.

The second version has more words … but more interest.

Rules and Judgment

But wait! More words? Doesn’t that fly in the face of “Omit Needless Words”—the command to remove from your sentences every word which doesn’t carry its weight in meaning? Well, yes, it does. Writing rules can conflict with each other, and you have to use your best judgment when applying them.

In the case of “Omit Needless Words” at war with “Show Don’t Tell”, no matter how good you are, you’re unlikely to come up with a way of showing “the boring professor” in fewer than the three words it takes to say “the boring professor.” So you as a writer have to exercise your best judgment on whether your story or essay is better served by getting to the point … or illustrating it concretely.

The Danger of Writing Rules

The real danger of writing rules is not that they can conflict; conflicting rules can obviously be resolved by exercising judgment (though what that resolution should be is often far from obvious). No, the real danger of writing rules is when they do not conflict. When they clearly apply. And can be overapplied.

Unlike the laws of physics, the rules of writing don’t apply everywhere. They’re heuristic: rules of thumb that don’t hold in every situation. The reasons behind this are very deep. Some of the reasons are buried in what makes writing effective. Some are a product of how writing rules are created. But mostly, they’re a product of how writing rules are applied. Only by understanding the seductive power of rules—and the limits of what rules can do, even in the best of all possible worlds—can we understand the Rules Disease and how to fight it.

What Makes Writing Good

Writing is good if it is effective at evoking in the reader what the writer wanted. But writing is not effective because of how it conforms to a set of rules; writing is effective because of how it is processed by the human brain.

The human brain doesn’t process stimuli using strict rules. It’s a robust, error-correcting, creative understanding engine resistant to all kinds of noise. It can tolerate misspoken sentences, broken grammar, misspelled words, and even corrupted lettering. Take a look at the following phrase (taken, with apologies, from Doctors Selfridge and Seuss):

T/-\E C/-\T IN T/-\E H/-\T

Most of us have no trouble reading “The Cat in the Hat,” but how? The “H” and the “A” in “the cat” are actually the same shape—the ambiguous figure /-\. Fortunately, your brain naturally fills in the gaps, or doesn’t, depending on the context that shape appears in. The letters around that shape actually change your interpretation of the shape. This works for more than just mistakes: think of a lowercase ‘l’ and uppercase ‘I’, or an uppercase ‘O’ and the number ‘0’. In handwriting, these can be almost identical, but we rarely have problems telling them apart, based on our experience.

Scientists who study reading have different names for this phenomenon. I don’t want to overstate the level of consensus that scientists have reached, or  understate the enormous amount of work ahead of us to truly understand human language. But the purpose of the picture of the huge stack of books at the head of this article was not to show how many rules there are—but as a brute act of credentialing, to show the briefest slice of the immense amount of work scientists have done to show that language is understood through the interplay of multiple sources of knowledge.

When we hear sounds, we use the movement of the speaker’s lips to help us figure out what they’re saying, something that cognitive psychologists Harry McGurk and John MacDonald found when dubbing tapes in their laboratory. When we perceive letters, we use the word that they appear in to help us decipher them, something that psychologists James Rumelhart and David McClelland modeled with parallel distributed processing. When we understand sentences, we use the whole history of speech we’ve heard to make sense of it, something computer scientist Eugene Charniak modeled with statistical language learning. Even understanding the simplest stories can involve reinterpreting our most basic concepts, something artificial intelligence researchers Kenneth Moorman and Ashwin Ram modeled as creative understanding.

There are limits to this, of course: as linguists like Ray Jackendoff and Jerry Fodor are fond of pointing out, you can’t not read words you see, and your ability to perceive letters is not affected by what you ate for breakfast. But even they argue that at the level of meaning, when readers try to put together what a story is about, they draw on every resource of information available to them.

The point is that at almost every level that scientists have studied, readers don’t use strict rules, but instead use their past experience as a guideline to try to piece together some consistent interpretation of the squiggles they’re reading.

A complete story is the same way: any rule can be broken, as long as there’s some interpretation consistent with our experience. You can write a complete story without breaking a single rule, but if there’s a powerful effect you want to achieve, you can break any rule to make the story have the impact that you want.

Literature is littered with examples. Faulkner writes sentences three pages long, but Hemingway writes ones three words long. E. E. Cummings plays with punctuation, line breaks, and spaces; but Shakespeare writes entire plays in iambic pentameter. Each of these striking stylistic choices makes sense given the way each author put their story together. Each choice makes sense … in context.

Where Writing Rules Come From

But writing rules don’t have this contextual knowledge embedded in them. They’re free floating. No matter how pithily worded, writing rules amount to IF-THEN triggers, specifying a condition that can match a story and suggesting a course of action—or, more often, just suggesting “don’t do that.” But if good writing is contextual, why do we use tools that are context free?

I don’t know the history of all writing rules, but I do know how writing rules are created, used and applied in the writing communities I’m a part of. In my experience, writing rules are created when readers, writers and editors reflect on a story that worked for them—or, more likely, one that didn’t. They find a place in a story which didn’t work, identify a flaw, and create a rule that helps them fix it.

I say a story because, while ideally rules should apply to many stories, in my experience the process of creating rules begins when a reader encounters a story which unexpectedly didn’t satisfy them—and reflecting on it awakens in them the idea that writing could be systematically improved.

For example, I and my writing colleagues use “The Sharply Dressed Man” rule:

In dialogue with an embedded tag, such as “Stop,” he said, “or I’ll shoot!”, if the name of the character speaking is a long noun phrase, as in “the sharply dressed man said,” consider putting the verb first, as in “said the sharply dressed man”—or rewriting the sentence to make the long embedded tag unnecessary.

This rule was created when I was unexpectedly disappointed by a turn of phrase in the published version of one of my own stories, “Steampunk Fairy Chick.” To avoid complicating the story I had several unnamed characters, but to keep them straight the awkward phrase “the sharply dressed man said” got itself embedded in a chunk of dialogue that really needed to be split in the middle for rhythm. Swapping the verb fixed the rhythm so that the sentence was clearer, but I could also have given the character a name, rewritten the dialogue to rework the rhythm, or rewritten the scene so the speaker was clear with a simple “he said.”

As writing rules go, it’s not the greatest one. I did spend some time reading over the story to try to analyze whether this was a pattern, but ultimately I only looked at that one story. And the reason the sentence didn’t work may have been more a product of its context and less a product of constructions like “the sharply dressed man said.”

This problem isn’t one we can easily think our way out of by analyzing the sentence and the story more carefully, because reading isn’t just an error correcting process: it’s an unconscious process. More precisely, it’s an unconscious process that produces our conscious experience. We don’t have access to all the details of our mental processing; we only have access to the output. Scientists like Jackendoff and Fodor argue our minds are built of modules—separate regions of the brain and thought whose innards are at least partially hidden from the rest of the mind.

When something goes wrong, we construct explanations based on what we perceive—but scientists have found these conscious explanations are often fictions masking real problems that are much deeper. This happens most dramatically with patients who have brain damage or surgery splitting one side from the other; the cognitive scientists Michael Gazzaninga and Roger Sperry found that the left side in particular would make up bizarre explanations for the behavior of the right, and attributed it to a module they call the left brain interpreter.

But even healthy people have this problem, most spectacularly when we do something that conflicts with our intentions and later alter our perception of our own intentions to fit our actions, a process that cognitive scientists Leon Festinger and Merrill Carlsmith called resolving cognitive dissonance.

The point being, the rules we accept as being “right” about a story are fodder for our left brain interpreters, and when we encounter something that makes us queasy, the interpreter uses the rules it knows to help explain that.

But the rules can only apply to the text that we see, and our understanding of the story is informed not just by that line but by everything we’ve read up to that point. So we may be tempted to blame the line we just read when our experience of reading a story is disrupted—but that’s like blaming the tip of the iceberg for our woes, when the real problems may lurk beneath the surface.

Experienced readers, writers and editors handle this problem by paying close attention to context: by looking at supposed offenses in the context of the overall story and making a judgment call about whether to correct them. But a writing rule by definition is divorced from that context: to be a rule it must be generalized enough to be applied to many stories and many contexts, an IF-THEN, a free floating bomb ready to drop its payload whenever its precondition is satisfied.

Where Writing Rules Go Wrong

Well, what’s wrong with that? Shouldn’t you, as an author, exercise your own judgment about whether to apply a rule? Certainly. But the problem is that other people can apply this to your story … whether or not there’s a real problem.

Think back on “The Sharply Dressed Man” rule. It was created by a confusing sentence in a particular story, but it’s no longer about confusing stories: it’s about sentences with longer dialogue tags. In reality, a sentence with a two-word “he said” can be confusing, and one with a fifty-word Faulknerian mini-epic can be clear—based on context, and content. But once you’ve learned “The Sharply Dressed Man” rule, you start to see it everywhere—and can flag every instance, whether they’re confusing or not—and whether fixing them will help the story or not.

“Master” writers and editors may complain this doesn’t apply to them—may complain that you simply have to learn when to apply rules—but in the trenches, out in the workshops and comic shops, in the writing groups and critique circles, where novice and journeyman writers are working with novice and journeyman editors and exposing their stories to beta readers and critics of all sorts, there are a thousand free floating writing rules and a thousand policies on how to apply them.

One policy I’ve often encountered—even from very experienced editors and beta readers, mind you—is to mark every instance of a rule whether it affects the story or not, leaving it up to the author to decide what to do with them. For me, this undermines the value of criticism: because you can’t, by definition, see your story how others see it, you depend on others to recognize problems in your story that you can’t see, whether that person is a writing partner, beta reader, editor, fact checker or copyeditor. But if rules are always being applied, regardless of whether the story is effective, then the signal coming back is not whether or not the story is effective—but whether it satisfies a checklist. And you can ALWAYS flag a story that violates the rule, regardless of how effective the story actually is—and some critics do.

This is the Rules Disease.

The Rules Disease

Every writer needs to learn their craft. Every writer needs to learn the rules. But some rules are in conflict (“Omit Needless Words” and “Show Don’t Tell”) some are contextual (like “The Sharply Dressed Man”) and some are just plain wrongheaded (see the history of the “Don’t Split Infinitives” rule on Wikipedia).

Even if the rules were perfect, following them would still be no guarantee of success. It’s a mathematical law that no set of rules, no matter how extensive, can simultaneously capture every possible truth and avoid every possible error. The formal name for this law is Gödel’s Incompleteness Theorem, but in this context the consequence of this limit is that if a story is a configuration of words, its effectiveness is a property of that configuration, and there is no set of rules you can create that’s guaranteed to capture that property completely. In other words, there is no substitute for reading a story and asking the question: is it effective?

And so every writer must learn to use judgment when applying the rules to their own works or when critiquing the works of others. But when rules become free floating, divorced from composition and judgment, they become a temptation. Writing rules are often pithy and easily repeated, spreading through writing communities like a plague. Writing rules are often clear and easily applied, giving us ready tools when trying to critique a story. Learning writing rules gives us a sensation of power—and when divorced from judgment, a false impression of wisdom.

The Rules Disease is endemic in the writing world. It crops up everywhere groups of writers gather in close proximity, exchanging ideas about their craft. Individual writers find rules that they consider their secret weapons; writing groups collect rules that become their common knowledge; editors find rules that become their sacred law. Everywhere groups of writers pick up their own strains: their own genome of rules that they pay attention to, possibly to a fault.

Curing the Disease

The cure, of course, is not to give up on writing rules: using them correctly can help a writer perfect their craft, or help an editor hone a story. The cure is instead to recognize that blindly following rules does not produce good writing.

Put more strongly: there is no writing rule that must be followed in order for a story to be effective. So it does not help anyone—not a writer, not an editor, not a beta reader, not a critic—to go through a document looking for violations of a rule for its own sake. That will produce a list of warnings without meaning, and following those warnings will produce stories that only satisfy checklists.

Instead, to use the rules, you should upend them. Rather than reading stories looking for violations of the rules, read your stories with an ear to whether they are effective—and if not, then use the rules to help you figure out how. Used this way, writing rules can make much easier the difficult process of parsing the unconscious sources of our discontent into a conscious explanation.

But even if you do find a violation of the rule, think carefully about whether the violation is really causing the problem, or whether the problem has another source. Because no matter how much you want to convince yourself you understand your own subconscious processes, you don’t. Your subconscious is faster than you, and just because it gets indigestion, that doesn’t mean you can always figure out why. A rule can help you understand why, but the seductive power of the IF in its IF-THEN can also trick you into thinking you understand the problem when you really don’t.

While it isn’t always possible, we should critique our stories with the same care that we compose them. We should strive to improve our critique with the same effort that we put into our writing. Our critiques should have real value that can genuinely help us improve our stories. And we should no more mechanically apply rules in critique than we would apply them mechanically in writing.

In the end no rule can substitute for the exercise of good judgment.

A Case Study

Just as I was finishing this essay, I encountered a writing rule in the wild and had a chance to test my theories. I was polishing this essay during writing sessions at a recent writer’s group, but since editing involves jumping around in a document and continuity is easier on listeners, during reading sessions I was reading from my novel JEREMIAH WILLSTONE AND THE CLOCKWORK TIME MACHINE. Then one of my trusted beta readers pointed out that there was a sentence in passive voice, which I’ve highlighted in bold below:

Then she clocked him hard on the jaw, and he went out again.

The sounds of approaching sirens began to be heard in the distance.

“We gotta go,” Marcus said. “Airship girl! We gotta go!”

Aha, the perfect test, I thought, so I asked: “Why did the sentence bother you?” My beta reader had a great response: “The sentence threw me for a loop. It didn’t sound like the style of the rest of the passage. Passive voice was the first thing that jumped out at me as a possible problem.”

So, consciously or unconsciously, my beta reader was already following the strategy I’ve recommended, but simply hadn’t told me why: she invoked the rule without first telling me that the sentence had bothered her.

But if you look at the sentence, passive voice is only one of the sentence’s problems. Think about “Omit Needless Words”: sirens, the sound of sirens, and hearing sirens are redundant. The word ‘siren’ can refer to a physical object, a horn, or a sound, the wail those horns make. But once you’ve said you’ve heard a siren, saying you’re hearing the sound of a siren is redundant. Furthermore, taken out of context, “began to be heard” also seems unnecessary, because when you hear a siren by definition you started to hear it at some point. In this case, “began to be heard” is not unnecessary, because our heroes had just disabled a police car’s siren in the next lot, so saying that a siren “began to be heard” provides new information. And identifying that new information is the key to fixing the problem.

I don’t think this is that bad a sentence. It’s National Novel Writing Month churn, quickly banged out, but I know why I wrote “Jeremiah heard sirens” that way: because the sound of the sirens is slowly growing in the distance, and I wanted to stretch out the description to stretch out the perception in the reader’s mind.

But there are better ways to do that, and better ways still to convey the information that they’ve started to hear sirens again, that the police must be sending reinforcements, and that it’s urgent that they go. So the solution is not to tweak the sentence: it’s to annihilate it entirely and deliver the needed information in a completely new way.

Then she clocked him hard on the jaw, and he went out again.

“We gotta go,” Marcus said, glancing over his shoulder. Jeremiah heard sirens in the distance, approaching fast: the police were sending reinforcements. “Airship girl! We gotta go!”

Now, I’m not convinced this is the perfect replacement: two of my editors disapprove of placing multiple character names between dialogue tags, because they think it can confuse readers. But this version is stronger than the last.

(Full disclosure: since the above paragraph was written, I’ve further refined the sentence to read “Sirens wailed in the distance,” removing the confusing name on the prompting of the mental ghosts of that prior editorial feedback—but I’m still not happy with the revised version. Yet. SO the above version stands. For now.)

SO ANYWAY, based on this editing experience, this is what I recommend: if something bothers you about a story, say what bothers you, then point out possible violations of the rules. That should be a starting point for thinking about the purpose of the segment of the story, what it should be achieving—and where it fails.

If you understand why something is failing, then you can fix it—with a deeper and better fix than just correcting a violation of a rule.

Further Reading

The writing rules I mention are ones I’ve heard from many sources, but the granddaddy of them, “Omit Needless Words,” is from Strunk and White’s The Elements of Style, which every writer in the English language should read.

The “T/-\E C/-\T” example, which illustrates how surrounding evidence can change how we perceive the same stimuli, originated in Oliver Selfridge’s paper “Pattern Recognition and Modern Computers“, but it and parallel distributed processing models like it were discussed more thoroughly in James McLelland, David Rumelhart and Geoffrey Hinton’s paper “The Appeal of Parallel Distributed Processing” in the PDP books, from which the illustration is thieved. The Cat in the Hat, of course, is by Theodor Geisel, known to the world as Dr. Seuss.

The McGurk Effect is discussed in Harry McGurk and John MacDonald’s paper “Hearing Lips and Seeing Voices,” but a more engaging illustration was done by the BBC on Youtube and is discussed in depth on Wikipedia.

Eugene Charniak discusses “old school” methods of understanding written text with grammar and spoken texts with statistical rules—and how scientists now build statistics directly into grammar based on large corpora of text—in his book Statistical Language Learning, a topic also briefly discussed on Wikipedia.

Kenneth Moorman, who started out his work using an “old school” grammar parser but now thinks Charniak is on the money, was my cubemate in graduate school. He wrote a program called ISAAC that read very short science fiction stories, and demonstrated that some of the simplest possible stories required creatively reinterpreting concepts. Kenny and my thesis advisor Ashwin Ram edited a book called Understanding Language Understanding with a couple of chapters on this approach.

While a careful read of their models supports my thesis that understanding a text draws on all available information, neither Ray Jackendoff nor Jerry Fodor (nor even I) would argue that language understanding is infinitely plastic, and the fixed nature of our low-level language models no doubt informs many grammar and stylistic rules. However, both of them agree with my point that we don’t have full conscious access to the modules with which we are understanding language, so our ideas of why we don’t like something are often a guess.

“Steampunk Fairy Chick” appears in the UnCONventional anthology, but the article where I discuss how I was unpleasantly surprised by a few turns of phrase once I saw them in print, and thereby came up with “The Sharply Dressed Man” rule, appeared in last month’s column on this blog.

Michael Gazzaniga and Roger Sperry’s work on split-brain patients and the left brain interpreter is discussed thoroughly in the chapter on consciousness in Gazzaniga, Richard Ivry and George Mangun’s textbook Cognitive Neuroscience. The problem of cognitive dissonance and how we resolve it by editing our own beliefs was tackled by Leon Festinger and Merrill Carlsmith and is discussed in depth in Daniel Wegner’s The Illusion of Conscious Will.

The limits of prescriptive grammar rules (and of purely descriptive ones as well) are discussed at length in David Crystal’s The Cambridge Encyclopedia of Language. The “Don’t Split Infinitives” rule is described in depth on Wikipedia. The upshot of all this is that languages do not ‘decay’; they simply change, something discussed in the Encyclopedia of Language and in Jean Aitchison’s Language Change: Progress or Decay, also available online.

Finally, my opinions are my own. I may have been trained as a cognitive scientist, but I am not a practicing cognitive scientist: I’m a writer. I haven’t done experiments to verify my hypotheses about rules; I’ve used existing experimental evidence and the theories built upon it to synthesize, engineering-style, an approach to dealing with texts and applying writing rules. But I could be wrong.

As always, your mileage may vary.

-the Centaur

A Writing Group Poem

Hi everyone,
Here’s a little poem I wrote during Tuesday night’s writing group:

There’s a writing group I’ve come to know,
That meets on Tuesday night.
They get together and form a group,
They sit down and they write.

Fables, fiction, memories,
And stories all are told.
Such a range of story characters,
Tall, short, young, and old.

They say that writing is good for you,
It releases an inner thought.
It unleashes the imagination,
And allows dreams to be sought.

Transferring what’s in your mind,
To put it down in words.
Bringing thoughts to life,
It’s not far-fetched or absurd.
So, if it’s Tuesday night,
And you need something to do.
Just come on down to Mission City cafe,
We’ll save a seat for you.

-Janina

Doing Medical Research as an Author

I’m a technical writer, but I also write books for families who are coping with children’s medical issues (The Parents’ Guide to Clubfoot  and The Parents’ Guide to Hip Dysplasia).

If you’re a writer who is researching a medical topic, it’s important to find accurate, reliable sources of information. I often start with the National Institute of Health (NIH) website, which has very good health information for consumers. If I want more depth, I go to Pubmed.  Pubmed is the online U.S. Library of Medicine, which is geared toward medical professionals. Medline  is another good online resource associated with the NIH.

Anyone can visit websites like Pubmed and Medline to search the medical databases and read abstracts of medical journal articles. When I’m doing research, I cut and paste each abstract for the articles that I want to read into a Word document so that I have a list.

The problem that arises is that unless you subscribe to the medical journals, in many cases there’s a fee to get each complete article. This can get expensive pretty fast. When I was working on my first book, a friend in the medical field told me about community health libraries, and a whole new world opened up to me.

Community health libraries are wonderful resources. They have health and medical books and brochures about many health topics. The staff can help you find information that you might not discover on your own, and show you how to use medical databases. Even if the library is small, the staff typically has access to health resources at other locations

On top of all that, researching at community health libraries can save you money. Typically, they can get you full medical articles without charging you for access. If you want a printout to take home with you, there’s usually a small fee to cover the cost of making copies.

I recently visited the PlaneTree Health Information Center located inside the Cupertino Library, which is new to this location. I was doing research for a nonfiction book I’m going to be working on this summer. The staff was friendly and helpful. If you don’t live near the Cupertino Library and want to visit a community health library at a different location, ask your doctor’s office to recommend one.

What Are Your Top 5 Favorite Noises?

a cat walkingBesides being fun, making this list could help your writing wake up to sound.

Don’t take too long on it. I’d say post your list within 24 hours. And don’t worry about trying to get your absolute top 5 favorite sounds ever. When you’ve collected 5 sounds you love, just post the list. We know this is just for fun, and we won’t hold you to any of your stated favorites. (And if you think of 5 more, you can post those, too!)

-Keiko

Learning from Publication

Recently I wrote a short story called “Steampunk Fairy Chick” for the UnCONventional anthology. Even though the story went through many revisions, lots of beta readers, two editors and a copyeditor, when I read through my author’s copy I found there were still things I wanted to change. Nothing major—just line edit stuff, a selection of different choices of sentence structure that I think would have made the story more readable.

I can’t react to this the way I would with a draft; the story’s in print. And I don’t want to just throw these insights on the floor. Instead, I want to analyze the story and find general ideas I could have applied that would have improved the story before it hit the stands—ideas I could use in the future on new stories.

Don’t Overload Your Sentences

I am verbose by nature, and my stories are ornate by design. Because I was trying to pack a lot into 10,000 words, I tried to pack a lot into each sentence of “Steampunk Fairy Chick.” Sometimes, the sentences simply couldn’t carry the load. For example, on the first page of the story this sentence appears:

Jeremiah prepared to dart out into the food court before one of them could cry “Foreigner”—or was the word on this world “alien”—and bring the whole restaurant down upon her.

Here I’m trying to do a whole raft of things all at the same time:

  • Set the scene: Jeremiah is in a packed restaurant near a “food court,” which helps set the story in the present day.
  • Show character: Jeremiah is active, quick thinking, prepared to bolt at a moment’s notice—and she’s hiding something.
  • Provide backstory: Jeremiah is hiding the fact that she’s part alien, and she’s concerned that admitting it can get her in trouble.

That’s a lot for one sentence to do, but I didn’t choke on any of that: I choked on the phrase “or was the word on this world ‘alien?’” which made me lose my place. Why is that aside even in there? It’s because in this sentence I’m also trying to:

  • Raise a question: Jeremiah is not clear that the rules or language are the same in “this world”—implying she’s from another.

That’s great, but it’s a separate idea. So perhaps, even though it costs more words, it would have been better to separate these ideas into two sentences:

Jeremiah prepared to dart out into the food court before one of them could cry “Foreigner” and bring the whole restaurant down upon her. Or wait—wasn’t the word for “Foreigner” on this world “alien?”

This rewrite is clearer … and by removing the interjection, it serves another hidden purpose of this sentence:

  • Clarifying ambiguity: “Jeremiah” is a male name for a female character … so “Jeremiah” needs to appear with a female pronoun.

Even though that creates yet another job for this sentence, it’s important. This is a very early sentence, so it’s critical real estate for establishing her gender clearly. Removing the aside brings “Jeremiah” and “her” eight words closer together.

As a side remark, Jeremiah’s male name illustrates the gender-neutral world of Victoriana from which she came, but otherwise isn’t material to this story—and some authors question whether a story should contain anything in it that doesn’t serve that specific story. For standalone stories, this might be the case, but for series fiction I respectfully disagree. In series fiction you must respect the rules of your series even if they aren’t convenient for a specific story. A series creates its own reality, and one could no more change Jeremiah’s name to Jeri for convenience than one could change Sherlock to Sherman—or move Atlanta to Albania.

“Spoilers!” she said with a smirk.

WARNING: the next two sections contain very mild spoilers for the story. If you’re a savvy scifi reader you probably can read the following section without being spoiled because what IS being spoiled is only a minor surprise. However, if you are one of the people who HATE spoilers, skip to “Make Learning Explicit” … or run out and buy a copy of the UnCONventional anthology and read the last story in it. (Yes, that was a subtle—but entirely shameless—plug).

Pay Attention to Rhythm

Back with us? OK. Another sentence that leapt out at me was:

“You really think,” the sharply dressed man said, “a handful of steampunks armed with coffee and vodka are going to stop the zombie apocalypse?”

There’s nothing too bad with this sentence, but it still jarred me—because “the sharply dressed man” is a complex noun. I’m referring to this character with this mouthful of a name for several reasons:

  • Limited third person point of view: Jeremiah, our point-of-view character, doesn’t know his name—and therefore, the narrator, who doesn’t know any more than the POV character in limited 3rd person POV, doesn’t either.
  • Limited oxygen for limited screen time: The sharply dressed steampunk is a key but minor character, appearing in two and a half brief scenes with only a few lines. Naming him in this already complex story could distract the reader.

Major surgery could fix the problem: make the character more prominent and introduce him formally; cut the character out; give the line to someone else; come up with a shorter epithet. But there’s an easier trick to solve the problem:

“You really think,” said the sharply dressed man, “a handful of steampunks armed with coffee and vodka are going to stop the zombie apocalypse?”

The point of the dialogue tag in this sentence isn’t just to identify who’s speaking. It’s to break up the rhythm of the sentence so it reads the way it ought to be heard. The sentence is a secret in-joke, a riff off this line in Mortal Kombat:

“A handful of people on a leaky boat are going to save the world?”

Interjecting the dialogue tag into the sentence breaks up the reading, makes the reader pause in hearing at the right moment to make the quotable quote stand out. But the action that’s happening is speaking, and throwing a four word noun into the sentence completely derails the rhythm.  Why? A clue can be found from an earlier sentence with a very similar structure which did NOT disrupt my reading:

“This is a trick,” the sharply dressed man said. “Some kind of neon—”

The initial scrap of dialogue here—“This is a trick”—is a complete sentence. A reader knows it is speech from the quote marks, and expects to find a noun describing a speaker. But in the offending sentence, the initial scrap of dialogue—“You really think”—is NOT complete, forcing the reader to keep what the character said AND the character’s name in their mental buffer until the dialogue tag appears.

A better solution is to make the ‘said’ come first, easing the reader down off “You really think” by confirming that the reader has just read speech. Putting the verb first in this case reinforces the already existing expectation that the reader will encounter the name of a character, followed by a resumption of the dialogue which will complete the spoken sentence started with “You really think.”

Grammatically, switching the verb and the noun in a dialogue tag is almost always allowed, but it is not always recommended aesthetically. Consider:

“Give me a break,” he said.

versus

“Give me a break,” said he.

Ouch! If you don’t have a rhythmic (or other) reason to change the order of the dialogue tags … just stick to “he said.”

Stick to your guns

In several places in the story, the editors suggested I could get rid of dialogue tags to make the text shorter, smoother, and punchier. Here’s an example:

“She brought this down on us.” Jeremiah stared into the wires feeding in to Jackson. “That big vacuum-tube enhanced brain of hers holds secrets of time travel not even the Scarab managed to discover in over a billion years.”

That paragraph works well, delivers its punch … but doesn’t sound like me. I want sentences to draw pictures with words. And for a sequence of actions, a sequence of short sentences without connectors can do that well:

Jeremiah darted forward. The nearest zombies stirred. Jeremiah shoved them aside. The remainder started to turn. Wayfarer sprayed them. Zombie eyes began to glow. Jeremiah reached Jackson and fumbled at her corset. The zombies raised their hands, crackling with power.

But when someone is speaking, action and speech are happening at the same time. The montage effect above works less well, perhaps because the dialogue lives in quotation space and the action lives in normal narrative space. That’s why I’d strongly consider changing the first paragraph above back to:

“She brought this down on us,” Jeremiah said, staring into the wires feeding in to Jackson. “That big vacuum-tube enhanced brain of hers holds secrets of time travel not even the Scarab managed to discover in over a billion years.”

This weaves the action and the speech together so it’s clear they’re taking place at the same time. Your mileage may vary; there is nothing wrong with the version the editors recommended, and you could delete dialogue tags more extensively through the entire story without a fault. (Anthony waves to his editors, who did a great job!) But when I reread my own story, these dropped dialogue tags didn’t sound like ‘me.’

I find the very best edits are the ones that seem perfectly natural: the editor suggests it, and it goes so well with the story the words feel like your own. Sometimes this happens because the editor has nailed your voice; sometimes it happens because you have internalized the editor’s lesson. BUT, if a change doesn’t work for you, I think the right thing to do is say “stet” (Latin for “let it stand” and writer-editor jargon for “revert to original”). Trust me, editors are big boys and girls. They WANT authors to push back as much as they push authors, because the end result is a story that benefits from both the editor and the author’s best ideas.

Make Learning Explicit

You may agree or disagree with the recommendations I’ve made above. “Switching ‘said’ and ‘he’ for effect?” you might say. “Adding extra dialogue tags where none are needed? Adding extraneous material to a story at all? Heresy!” In fact, a few years from now, when I’ve grown more as a writer, I might say the same thing. But there’s a more general principle here which you can take advantage of even if our aesthetics don’t agree: use publication as an opportunity to make learning explicit.

People learn when they get feedback on their actions and try to improve based on it. If the feedback is timely and you don’t actively try to reject it, learning can be almost automatic. But you can’t always guarantee getting timely feedback—so sometimes you need to deliberately create a strategy that helps you improve.

So what I recommend is: when your work hits print, get a copy of it. Read it, marking anything you want to change. And then try to generalize what you’ve learned, so you can apply it to new stories in the future.

-the Centaur

Catching the Horse, or How I Wrote a NaNo Thing

“If you fall off the horse, get back on.”

It’s an old saying, tried and true, that failure does not mean to stop trying.  Fall off the horse, jump back on quickly.  The longer you wait, the harder it is to work up the courage to try again.

But what if you wait so long that the horse wanders off?

This last year, my writing life has mainly been devoted to revising my novel manuscript.  Writing and rewriting, incorporating comments from beta readers, changing the order of scenes, ripping out characters, you name it.  At this point, the “horse” of my manuscript isn’t ready for show-jumping for an agent, but it’s getting close.

While I threw all my efforts into polishing this manuscript, something else was happening so slowly, so quietly, that it took me a long time to notice.  The “horses” of all my other stories were wandering off into the sunset, reins trailing behind them.  I was so focused on what I’d already written that I wasn’t producing anything new.

Then November arrived, and with it, National Novel Writing Month.  For the last six years, NaNoWriMo has provided a springboard for my creativity.  Something about knowing thousands of other people are also crazy enough to write 50,000 words of a novel in thirty days alongside me is remarkably freeing.  At midnight on October 31, metaphorical trumpets blare, and I’m once again spurring a novel down the track hurtling toward the finish line of “THE END.”  In all of my attempts, I’ve hit the 50,000 word NaNo goal, though “THE END” has eluded me.  That’s all right.  Each of those novels gained enough momentum during the NaNo race that hitting an ending is inevitable.

NaNo 2011 rolled around after I had spent most of the year polishing the hooves of my thoroughbred.  I looked around to find another story to ride for NaNo and discovered all of my horses had wandered off, and what was worse, I was not certain I could entice any to come back to me.  When I first started writing, I never imagined I could come up with any story ideas that could hold my attention for long enough to produce even one novel, much less several set in the same story universe.  This year I had the opposite problem.  I wasn’t sure I could do it again.

In the weeks before NaNo, I fretted about what to write.  Should I play it safe and write the next adventure in my usual characters’ lives?  Should I use the time to finish one of my other drafts?  Or should I, could I, use the momentum and joy of NaNo to try something new?

My “stable” of stories has room for many novels.  So far, the stalls are filled with a thoroughbred of an almost submission-ready manuscript, another thoroughbred waiting its turn for grooming, and a few work horses that need a lot of training before they’ll be ready for the submissions race.  I knew I could easily use NaNo to entice another work horse into the stable.  That’d be the safe course.  Write another adventure for my characters, give them another mystery to solve.  Plod forward.

Something within me rebelled at the thought.  I’d played it safe by spending all year in revision and never poking my head outside the stable door.  Something within me wanted to soar.

So how does one entice one’s creativity to return from the green pastures where it’s wandered off?  Soft words and treats?  Threats of spur and whip?  That’s a good way to scare creativity off into the hills never to be seen again.

Getting creative about being creative works.  So does sneaking up on the problem.  Novels can be skittish.  Too much pressure, too many expectations, and the enthusiasm to work on so large a project can wither.

This year, I snuck up on NaNo.  I decided not to write a novel.  I wrote a Thing.  Every time I put hands to keyboard or opened my notebook, I fed words to the Thing.  It sat in a corner of the stable yards gobbling down word after word while the horses looked at it askance and stayed out of the way of its voracious appetite.

And a funny thing happened to the Thing.  The more I worked on it, the more coherent it became.  The style is different than anything I’ve attempted before, the ideas are new, and its place in my story universe opened up so many ideas that I’m still reeling from all the tantalizing possibilities.  By allowing my Thing its thingness, by not forcing myself to conform to my own expectations, something wonderful was born.

Now after NaNo is over, I have a 50,000 word Thing still hungry for more words.  It’s looking more like a novel than when it started, but I’m not sure whether the Thing is going to hatch into a horse like my other novels.

Right now, it’s looking a lot more like a pegasus.

Keiko Called Time

So there I was at the Write to the End group scribbling away in my notebook. Just before this round of writing, Anthony had announced his Doorways to Time Anthology call for entries. I was working on story idea I got from that. The way it was turning out, this story wouldn’t work for the anthology, but I’d write another one for him later. Even the sound of the words Antony’s Anthology made it seem like they belonged together.

“Two minutes left,” said Keiko. “Finish up, or look for a good place to stop.”

There wasn’t a good place, but that was okay. Enough was on paper that I would be able to figure out what I meant later if I wanted to go back to this story.

Keiko called time, and just that one night, Time decided to stop by, you know, to chat and see what she needed. It was Pacific Time specifically who came over to our table. She had long, flowing tropical hair and looked very relaxed as if she had all the time in the world, which I suppose was not far from the truth.

I was sitting near Keiko, so I heard Pacific Time introduce herself in a low voice, but I think most people in the group figured she was one of the many people who stop in once in awhile, and then don’t come back for a long time.

“I don’t get out to Silicon Valley that often,” said Pacific Time. “For the most part, Internet Time resides here, and he zips all over the place so we don’t connect that well. I was coasting on a weather front when you called, and thought, hey, why not?”

“Oooh,” said Keiko with a smile. “I’m so glad you came. Pull up a chair and sit down. We’ve just finished one of our 20 minute writing sessions and we’re going to read. Did you bring anything?”

Pacific Time shook her head.

“That’s okay, said Keiko. “You can listen in for this round, and then we can talk during the break.”

Nothing fazes Keiko.

How to Run Beta Reading Cycles

So you’ve written your piece, read through it and revised it, worked on it some more, and now it’s reached the point where you’re thinking of submitting it for publication. Before you do that, consider rounding up some beta readers and having a beta reading cycle.

Beta Readers
What are beta readers? They are people who read your work pre-publication and give you feedback. The term came from pre-releases of software that go through beta testing. Where do you find beta readers? Try your writing group, and if you know people who love to read the genre you write in, ask for volunteers. If you’re writing mysteries, and your potential beta reader doesn’t like the genre, then he or she is probably not a good fit for your project.

Sometimes it’s helpful to give the beta readers guidelines, especially if this is the first time you’re working with them. This can be as simple as asking them to tell you what they like, what they don’t like, and to flag any areas that confuse them. If there’s something in particular that is giving you trouble you can mention it or not. For instance, you might say, “There’s something wrong with the ending, but I can’t figure out what.” Or you might decide not to say anything and see if your beta readers come to the same conclusion.

Planning and Managing the Review Cycle
You want your beta reading cycle to be effective. So it’s a good idea to give some thought about the kind of help you’re looking for, and to schedule your beta cycle with a specific beginning and end date. Talk to your potential beta readers to make sure they are available and that they want to participate. Only use beta readers who like the idea of participating, and plan on enlisting a few more than you think you need. That way if some get too busy and don’t have time, you can still get comments from the others.

Preparing a Document for Review
I find it helpful to save the file for the piece that is going out for review with the date in the file name. It could be something like this: title_date_mylastname_beta. That way I know exactly which version of the piece went out for review. Beta reviews can be done in common file formats like PDF or Word that you send to the reviewers (soft copy), or you can provide printouts (hard copy). For shorter pieces, many readers don’t mind reading a file, or printing it out themselves to mark it up. If you have a long piece, find out if your beta readers prefer printouts.

Note: One way for reviewers to mark up a Word document is to turn on tracking. That identifies every change but preserves the original text. If you receive this type of mark up from a reviewer, you can choose to accept or delete each change. Or you can print it and work from the hard copy if that’s easier for you.

If you’ve written a novel and your beta readers prefer hard copy, the cost of reproduction can add up quickly. So far, the least expensive option that I have found is to go through Lulu (www.lulu.com) and set up a book as a private project. A private project isn’t visible to others, and that is the default setting at Lulu when you upload a project. You can use their wizard to format your beta review draft, and then order the number of copies that you need, using whatever coupon code is active when you place your order. Lulu has online chat support during business hours and I’ve found them to be very helpful.

It pays to shop around, and you might find a better deal somewhere else, so you should comparison shop before you make your final decision about where to get your printouts produced. If you really can’t afford to have copies made, tell your beta readers and ask if they can work from soft copy for your project.

Review Comments
In a perfect world, everyone you approach for a beta read would give you insightful, useful comments that allow you to polish and perfect your work. In real life you’ll discover that some beta readers are more able to give useful comments than others. You’ll also find that they have different strengths. Some will spot issues with language mechanics, others can give good advice about plot. You’ll also encounter readers who either like or dislike a piece, or a part of it, but don’t know why. All of this can be useful, but sometimes it can be frustrating and confusing if the readers’ comments contradict each other, or if you feel the comments are not relevant to your aims as a writer. Remember too, that some reviewers will forget to tell you what they like about your work because they are focusing so much on trying to help you find any mistakes before you submit it for publication.

If you’re not sure which comments you want to follow up on, you can always make a test file. Try the revision and see what you think. Do you like the story better—or does making that change introduce a problem? If you like it better and it introduces a problem, can you fix this new problem? Sometimes revisions do “break things” that you have to go back and fix. With practice it gets easier to evaluate review comments and figure out which are most helpful to you. You’ll also learn which beta readers are the best fit for you.

Beta reviews can be a bit nerve wracking, especially when you’re first starting out, but they can also be very valuable. Being on the receiving end of comments can give you some insight about how to be a beta reader yourself. Once you start using beta readers, you will most likely hear from some of them about pieces they’d like you to review.