Showing posts with label Show don't tell. Show all posts
Showing posts with label Show don't tell. Show all posts

Wednesday, April 1, 2015

The Inactive Beginning

If you’ve read my post on the purpose of the Story Polisher, then you know that I like to divide writing into three categories: Prose, Plotting, and Creativity. My posts here generally focus on Prose; this is in part because your prose will be the first thing an editor notices about your work (poor prose is the number one reason most stories get rejected, in my experience) and in part because it is difficult to teach people to write clear prose in any setting other than a classroom or one-on-one instruction. There are an abundance of resources out there to help new writers improve their Plotting and Creativity, but not many focused on Prose.

However, today I’m going to set Prose aside for a moment to focus on an element of Plotting. I do this in the interest of highlighting a common error that gets stories rejected by editors on a frequent basis. And that error is the inactive story beginning.

This error is easy to describe: a story begins, and nothing happens. More specifically, the protagonist and other characters aren’t doing anything, or the amount of activity on their part is miniscule compared to the number of pages it takes to describe it all.

This is almost always the consequence of heavy worldbuilding, backstory-telling, and other forms of info-dumping. Most stories have a fair amount of background information that the audience will need to know in order for the story to make sense, and it is tempting to try to get all of that pesky background information out of the way right at the start.

But here’s the thing: background information tends to be boring if your audience isn’t already emotionally or intellectually invested in your world and your characters. The most effective way to engage readers at the beginning of the story is to have something interesting happening at an efficient pace.

Here’s an example of how I’ve seen this done poorly (or rather, a summation of an example, since an actual example lifted from an actual manuscript would be far too long):

     The book begins with the protagonist in the back seat of an SUV, sandwiched between a pair of burly guards. He is being escorted into the dangerous jungles of Juduun, home of the dangerous and violent ape-snakes that guard the ancient ruins of a lost civilization. The various horrors that the ape-snakes have perpetrated upon humans are described. The ruins are described, along with the few little facts that are known about the ancient civilization and what happened to cause its downfall.

     Our protagonist is nervous and tries not to tremble, not wanting to show weakness in front of his captors. He reflects upon the unfortunate series of events that brought him here, how he was orphaned at a young age and stole to help feed his sister. He managed to find her good work and a place to live, but then everything went wrong when she caught the eye of a lecherous nobleman. Various things happened, our protagonist was charged with a crime that he either didn’t commit or was forced to commit even though he’s really a good guy.

     The jungles come into sight up ahead, covered in early-morning mist. The protagonist is being sent into the jungles to retrieve an artifact of the lost civilization as punishment for his crime. He will have no supplies or help; even worse, no one is even sure whether or not the artifact that he’s supposed to find is even real. He believes it’s just a myth and that he’s simply being sent to his death.

     They arrive at the jungles, and the guards throw him to the ground beside the trees. He pleads with them to give him some equipment, anything that might help him. The dangers of the jungle are described. He’s afraid of them.

Now, my summation of this example was four paragraphs long. The actual examples that the summation is based on, however, tend to be anywhere from ten to fifteen or even twenty pages long. That’s ten to twenty pages where our protagonist:

     1. Sits in a car
     2. Sits in a car and tries not to tremble
     3. Sits in a car and sees the jungle up ahead
     4. Is tossed from the car and pleads for help

See the problem? That’s nothing. Nothing happened in over a dozen pages of story. It was all just backstory and worldbuilding—one long infodump. It doesn’t matter how you frame all the backstory; if your protagonist is reminiscing about it, describing it to someone, or having it described to him or her, it’s all the same. Which is to say, it’s boring. It doesn’t matter how action-packed or interesting the backstory is—it will still be boring if it’s a flashback given while your protagonist does nothing. If all of that backstory is so interesting and eventful, then just go back and start the story there!

The pure-backstory prologue gets criticized often (with good reason), but even that would be better than watering down the action of the beginning of your story with infodumps.
Picture what the introduction to a movie would be like if it were done in this manner. Try the original Star Wars movie: after the opening crawl (which is itself a backstory infodump, but it’s traditional and deliberately evoking old pulp action films and comics—not to mention short—and is therefore somewhat justified), we see a star destroyer capturing Leia’s ship. C-3PO and R2 discuss how serious this is and the things the empire is likely to do to all of them. The imperials board the ship, and C-3PO reflects on how brutal the empire has gotten over the years and how hopeless the situation of the rebels seems. Vader comes on board, all menacing, and we’re shown a long introductory flashback depicting some of his history of brutality and his position relative to the Emperor. Jump back to the present, where Princess Leia records a long message explaining her position in the rebellion, what her goals were for her present mission, how she obtained the stolen plans for the Death Star, and then paused to reflect upon what type of droid R2 was and what his normal functions were.

"Ah, we've captured you, senator. Now I will explain the lengthy process by which we uncovered the fact that you are part of the Rebel Alliance and a traitor!"
Slow, ponderous, and boring, right? And that’s with actual action going on in the background—the imperials capturing and boarding Leia’s ship, fighting in the corridors, ominous villains arriving, and our heroine hurrying to get the plans off the ship. If that’s not enough to counter the effect of excessive infodumping, then nothing will be.


Don’t let this problem happen to your story! The inactive story beginning is the most common reason—after poor prose—that I’ve seen stories rejected. So remember: reflecting, reminiscing, explaining, and flashbacking are not action. There’s nothing wrong with introspection in reasonable doses, but introspection does not an interesting story introduction make. Get your characters out there and get them doing things right from the start.

Friday, February 20, 2015

Saying Things Twice

A common signifier of not-yet-professional writing is an author who consistently says things twice. This doesn’t mean that they repeat themselves verbatim; it means that they say something, and then they re-state it in a different manner. For example:

     Walking fast, she hurried to the door.

That’s rather redundant, isn’t it? We’re told that she’s “walking fast,” and then we’re told that she “hurried.” Those are basically the same thing. This sentence should just be shortened to “She hurried to the door.”

If you’ve been reading this blog for a while, you know why redundancy isn’t a good trait for your writing to have. If you don’t know, here’s a link to the many posts that touch on redundancy and its negative effect on writing. To put it shortly: redundancy wastes your readers’ time and insults their intelligence.

This is a real line from an actual manuscript.

Here’s some more examples:

     “Turn in your badge and gun now,” I ordered, holding out my hand.
     Detective Mullens cursed under his breath. Reluctantly, he complied, handing me his badge and his gun.

See the repetition? First, we’re told that Mullens “complied.” Since we just read the order he was complying with, we know that this means that he handed over his badge and his gun. But then the writer goes ahead and tells us that’s what he did, anyway.

     “Okay, I’ll see you at noon tomorrow,” Julia said. She made a note of the meeting, writing it down in her planner.

Same situation—“made a note” and “wrote it down” mean the same thing. One of those phrases should be cut.

Now, you may remember the common writing advice “Show, don’t tell.” This novice writer’s habit of saying things twice often comes about because the author chooses to show and tell. Here’s an example that one of my teachers once pointed out in my own writing:

     For most people, the view from the lighthouse would have been very impressive. But Hero had seen far more than most people. He simply yawned and leaned against the railing.

First I told my readers that Hero had seen more than most people, and then I showed that through his actions. You are all smart enough to read between the lines if I simply show you:

     For most people, the view from the lighthouse would have been very impressive. Hero simply yawned and leaned against the railing.

Bam. Gone is the redundancy, leaving behind tighter, more efficient prose. All I needed to do was trust my readers to be smart enough to understand what I was showing them.

Another example:

     “Thank you for your help,” Jane said. She smiled, her expression happy.

Boooo. We all know that a smile is a happy expression, right? No need to re-state it.

Pictured: A Happy Expression


You all get the picture. Next time you’re editing, keep an eye out for any spots where you might have said something twice. When you find them, ruthlessly eliminate the redundancy.

Monday, January 26, 2015

Dialog to Avoid: "As a ____, I . . ."

Here’s an irritating little phrase that we’ve all heard or read some variety of in a story: “As a _____, I . . .”

     “As a mortician, I can tell you that her description of the embalming process is accurate.”

     “As a psychologist, it is my expert opinion that this man is completely off his nutter.”

     “As your mother, I cannot allow you to meet with that girl anymore.”

     “As lord of these lands, it is my duty to care for the needs of the lesser beings under my rule.”

     “As someone who blogs about prose and grammar, I am constantly showered with praise and entirely deserved adoration.”
 
"And money. Don't forget all the money."

Nine times out of ten, this phrase and its variations are unrealistic, unnecessary, or unintentionally arrogant. Unrealistic, because they tend to be a form of maid-and-butler dialog, where a character tells people information they should already know. Take that third example above—whoever the woman’s child is, they already know that she was their mother. She didn’t need to say it. It feels like breaking the fourth wall; the woman isn’t identifying herself as the other character’s mother for the purpose of speaking to her child, she’s doing it because the author needed to let the audience know that she was the other character’s mother (and even then, it was probably already obvious to the readers).

That brings us to the second problem—such phrases are generally unnecessary. You’ll almost never encounter a situation where a character needs to explain who they are or what qualifications they possess before they speak. Usually, if you’ve done your job right, you’ll have explained all that far more smoothly in some other situation.

So often, when this phrase pops up, it is because the author wanted to remind the readers who this character is or what their qualifications are. Maybe the character hasn’t been around for a while, or you simply haven’t mentioned their profession in some time. In those situations, find a smoother way to work a reminder in. Or, better yet, trust your readers to remember what you told them before. If they don’t, maybe you need to make the character’s profession or position a stronger part of their character so that your audience won’t forget who they are.

But what about situations where the people around a character genuinely don’t know who a character is? That would justify them beginning a sentence in this way, right? Well, yes . . . but . . . that brings us to the final problem with this phrase: unintentionally arrogant.

Writers tend to be a loquacious bunch—we usually have respectably large vocabularies and a great fondness for words. We tend to read a lot, sometimes far more than we actually speak to other people. Being insulated into a group that so loves wordplay and a well-spoken turn of phrase can skew our perspective on how people actually speak. It can also blind us to how we ourselves sometimes sound when we speak.

So, that said, here is a variety of ways to express the thought “As a ____, I . . .”:

     “Oh, I can answer that—I’m a nursing student at the U. I think she actually got the details of the procedure pretty close to perfect.”

     “Hon, I know you don’t like it, but it’s a father’s job to look out for his daughter. I don’t think you should go out with that boy again.”

     “Well, if you want an engineer’s opinion, I’m happy to give mine. That whole design is completely infeasible.”

     “As an artist, I am frequently misunderstood by those around me.”

Which of those sounds the most arrogant? Now, this could just be me, but I generally feel like “As a ____, I . . .” is pretty much the most puffed-up way of expressing one’s qualifications.

Of course it’s possible to use this phrase in a way that doesn’t sound arrogant. But in those cases, the lack of arrogance is generally conveyed through tone and body language. When you’re writing, you can’t rely on those tools. So you have the distinct possibility that people will supply their own emphasis and tone to words which make them think of these sorts of people:

     “Well, as a vegan, I don’t believe in hurting any creatures in any way, especially for my own mere comforts.”

     “As a Christian, I would never let my daughter behave in that manner. It’s just not right.”


Now, sometimes you’ll have a character who is rather puffed-up with their own importance, or who is very loquacious and maybe a little oblivious to how they sound. If that’s the case, then it might be worth busting out the “As a ____, I . . .” phrase. Most of the time, however, people just don’t speak that way—it’s redundant, odd, and often viewed as an indication of self-importance.

Monday, January 12, 2015

Phrases to Avoid: "Alarmed By"

If you’ve been writing stories for more than twenty-four hours, odds are good that you’ve come across the phrase “show, don’t tell.” What this advice essentially means is that action is more interesting than description.

For example, we could write that “Jane was angry.” This is simple and direct, but it is also the sort of thing that is more engaging to see than to be told. Instead of just telling our audience that Jane is angry, we could write this: “Jane punched the wall, red-faced and growling through her teeth.” This conveys Jane’s emotions more powerfully than a simple statement of anger.

Another advantage to showing is that it is more subtle than telling. You have to trust your audience to pick up on the things that you are not directly stating. This makes it more difficult to write, but also makes it more engaging to read.

“Show, don’t tell,” is the reason that alarmed by is a phrase that should usually be avoided. Here’s an example of how I generally see this phrase used:

     Gizem felt her way along the corridor. She kept one hand on her dagger while the other traced the rough stone of the wall. There was a dim light coming from up ahead.
     When she came around the corner, she found a narrow window. Moonlight poured through the opening, illuminating the still form of Hunsu. Blood covered his face and clothing and pooled on the gray wooden floorboards beneath him.
     Alarmed by the sight, Gizem scrambled to Hunsu’s side.

Do you see the problem? You don’t need to be told that Gizem was “alarmed by the sight” of Hunsu lying in a pool of blood, do you? It’s obvious. You don’t even need to know who the characters are for this to be clear.  In fact, when you think about it, it’s almost insulting that the writer thought you wouldn’t already know that was clear.

The entire phrase “alarmed by the sight” could easily be removed without harming the passage. If you feel it is necessary, you can leave the word alarmed:

     Alarmed, Gizem scrambled to Hunsu’s side.

But even that could probably be shown instead of told:

     With a nearly silent gasp, Gizen scrambled to Hunsu’s side, almost tripping on a loose floorboard in her haste.


Now, you don’t have to show all of that. Simply stating that Gizen is alarmed is much more economical, and sometimes that will be more important than the emotional effect of showing instead of telling. The problem with the phrase alarmed by, however, is that it forces you to re-state something that you’ve already shown. In our example above, we’d just barely seen Hunsu lying in a pool of blood. We can infer why Gizen is alarmed without being directly told. 

Imagine writing this iconic scene: "Alarmed by the sight of the pursuing T-Rex in the mirror, Muldoon floored it." Do you really think your audience wouldn't figure out why Muldoon was alarmed on their own?
There is almost no scenario where you would use alarmed by without already having shown the alarming scene or event. So trust your audience to put two and two together, and leave the phrase out.