May 21, 2010

Background Noise

A multi-purpose title, as will hopefully become clear.

Submitted for your approval is one Theresa Cano. Theresa was a character in the early drafts of The Suffering Map, my first solid attempt at a novel. She’s a young woman who works as a cleaning lady in San Diego to pay for her night courses in computer engineering. Theresa’s going to build the first thinking computer, you see. As it turns out, one of Theresa’s regular employers is an antique store owner named Lois Antanello. Lois is kind of an old bitch, to be honest (she is one of the lesser villians of the book), but she pays well so Theresa bites her tongue when Lois snidely refers to her “immigrant accent.” Theresa has no accent, you see, because her family’s been living (legally) in southern California for about fifty years longer than the Antanellos, who showed up just after World War II. As it happens in the story, Theresa is working there in the antique shop one day when Lois gets a disturbing phone call from her namesake, her Uncle Louis, who is, as some folks might say, a very bad man.

Keep all that in mind. We’ll be getting back to Theresa in a bit.

Names and descriptions are a kind of shorthand for readers. They let the readers know this person is important. They could be the protagonist’s best friend, an old lover, or an old rival. Maybe we’re supposed to note the color of their eyes or just remember them when their dead body shows up fifty pages from now. We don’t know yet why they’re important because the story’s just beginning. But when the writer takes the time to give us someone’s name and what they look like, that’s a sign to us we need to remember this person. They’re an actual character.

As such, a horrible mistake beginning writers tend to make is when they name and describe everyone. Every single person on the page gets a name, age, body type, ethnicity, and a quick (or not so quick) personal history. This is great for your main character, but it really sucks for the waitress who’s just saying “your drink, sir,” and putting a glass on the table.

The problem is that naming everyone clutters the story with characters. Yes, characters are great and they really make your writing. You can’t have good writing without good characters. However, pointless characters just drag on a story. As the reader, I’m trying to keep track of the important people and getting bombarded with the unimportant ones. An excess of characters is like that lady on the sinking ship who keeps insisting she needs to bring all fifty items of luggage into the lifeboat. All we really need to get moving is to get her in the lifeboat, but as long as she’s taking her time with hatboxes, makeup cases, and steamer trunks we’re not going anywhere.

Did you catch that? The sentence where I listed out all the types of luggage was kind of clumsy, wasn’t it? Because we don’t need to know all that. Your mind trips over it because, as an experienced reader, you instinctively know it’s not that relevant.

In his book Creating Short Fiction (check out the carousel at the bottom of the page) Damon Knight explains that a fact we don’t know is information, but a fact we already know is just noise. I’d add to that by saying a fact we don’t need to know is also noise, it just takes a bit longer to recognize it.

This mistake is lethal in scripts. Would you spend a full paragraph describing that waitress in so much detail in a novel? Then why would you do it in a screenplay, where the object is to make your writing as lean and tight as possible? Think about it. One hundred and fifty words spent on the hopes and dreams and legs of the cute waitress is 150 words you don’t get to spend on your main character. Or on that climactic action scene. So why waste those words on someone who doesn’t matter? There’s a reason people in film production refer to those folks as “background” or “extras,” and not as cast members. If we know she’s a cute waitress, that’s all we need to know.

Can you imagine reading the lobby scene in The Matrix if every person was named and described? The four cops at the metal detector when Neo and Trinity walk in. The two dozen guards who come filing out into the lobby. The whole scene would drag like nobody’s business. It’d be four pages of description before Neo even pulled out his second set of guns. Sure, maybe those guys have wives, kids, rich lives, and a lot of that, but for the purposes of this story they’re just there to catch a lot of bullets and a few kicks from Trinity. The screenwriters of The Matrix knew that none of those guys mattered, which is why that scene is barely half a page long.

And, yes, I used to do this myself. Remember Theresa? She existed for no other purpose but to overhear the start of a phone conversation. We never saw her before. We never saw her again. When I removed her from The Suffering Map it didn’t even cause a ripple. She was nothing more than a clever way to get into the scene and fill an extra two pages. Once I realized that, I knew she had to go.

It’s not just excess characters, though. Any decription can be rich and lush and vivid, but what it will be, no question, is a pause in the story. A big description means a big pause and a big pause gives me time to wonder if I should be doing the laundry rather than reading. Do we need to know exactly what this apartment looks like? Every detail of how Yakko is dressed? Each line and panel and rivet of that armored exo-skeleton? The readers are going to fill in a lot of that for themselves, so if you’re spending time doing it–especially on elements that have no real bearing on the story–you’re just shooting your writing in the foot.

Now some folks might argue that such elaborate descriptions of every character, major and minor, is what makes writing great. To a small extent, they are right. To a far larger extent, they’re wanking off. Leonardo wasn’t scared of painting empty space when it was needed. Shakespeare knew sometimes a soldier was just a soldier and a crowd didn’t need to be anything more than a crowd. If you think you’ve got a better sense of art than them, knock yourself out.

When you write, make sure you’re focused on the foreground, and not spending your time and energy and pages on those distracting background elements.

Next week, something a bit more definitive. I’m going to prattle on something the reader should never, ever see in your writing.

Until then, go write.

March 11, 2010 / 6 Comments

…And I’ll Use Small Words!

So, one last time. Because some of you are having problems with it.

Take the bowl out of the cupboard and put it on the counter. Take the cereal out of the cupboard. Open the cereal box, open the wax-paper bag inside the box, and pour the cereal into the bowl. Do not overfill the bowl. When you’ve finished, close the box back up and return it to the cabinet. Now, take the milk out of the refrigerator. Unscrew the cap (counter-clockwise) and remove it. Pour the milk over the cereal in the bowl. Watch the edges and make sure the bowl does not overflow. If you plan on moving the bowl to another location to eat, do not let the milk fill the top half inch of the bowl. Once the appropriate amount of milk has been poured, replace the cap (screwing it on clockwise) and return the milk to the refrigerator. Open the drawer and get a spoon. Using the spoon, transfer an amount of the cereal and milk from the bowl to your mouth. Close your mouth around the spoon but do not bite down with your teeth. Slide the spoon out between your lips, keeping them sealed. Chew the cereal in your mouth. Swallow. Return the spoon to the bowl and repeat this process until all the cereal has been chewed and swallowed.

Now, let’s be honest with each other for a moment.

How many of you started skimming halfway through that?

It’s okay. I was writing it and I started skimming. It was boring as hell to write, I can’t imagine reading it was any better.

This is why so much exposition sucks. It’s all summed up right there in that fascinating paragraph. Allow me to explain.

Again.

First, that paragraph is something we know. Exposition is boring and pointless if the audience (either watching or reading) knows all the information being put forth. It’s just wasting time while we wait for something to happen. Damon Knight has pointed out that a fact we don’t know is information, but a fact we do know is just noise. No one wants to read a story full of noise. So, as writers, we need to know what our audience knows and work around that. If I’m writing a story set in the late 1930s or ’40s, I don’t need to explain to anyone that Nazis are the bad guys.

Second is the skimming that happened when you read that paragraph. People (or characters) don’t want to sit through something they already know. Can you imagine my doctor sitting patiently while I explain the circulatory system to him? Hell, a first year med student knows more about the circulatory system than I do. There’d be absolutely no point to me explaining it and no point to him sitting through the explanation. In Raiders of the Lost Ark, the two federal agents (and the audience) pay attention to Indy’s lesson about Ark of the Covenant because it’s something they don’t know. After all, that’s not their field of expertise. Notice that in the same scene, Marcus isn’t listening with rapt fascination. He almost comes across as mildly bored, and he probably is because he already knows this.

Third, and last, is that a lengthy explanation about how to prepare and eat cereal serves no purpose here. None. This is a blog about writing tips, so a paragraph like that is a waste of space. Nobody came here looking for information like that and the people who are looking for stuff like that won’t be looking here. As I’ve mentioned once or thrice before, there’s a reason Indy’s lecture to the feds doesn’t involve Masada, even thought the story of Masada is very cool and the odds are they don’t know it–it just isn’t relevant. He also doesn’t tell them about that cool time when he was a kid and those guys chased him on a circus train. The feds don’t know about that, either, but it’s probably less relevant than the Masada story.

A few times here on the ranty blog I’ve mentioned something I call the ignorant stranger which I came up with while writing a DVD review of Shogun four or five years ago. It’s a simple, sure-fire way to use as much exposition as you want in a short story, screenplay, or novel–you just have a source of information explain something to someone who does not know these facts.

Easy, right? Just remember these two things…

One, your ignorant stranger has to be on the same level as your readers or viewers. The audience is learning alongside them, and they don’t want to wait while the stranger’s educated on what policemen do for a living, where England is on a map, and why you shouldn’t play in traffic. There’s a big difference between ignorance and stupidity, and the ignorant stranger can’t actually be stupid. It’s only this particular situation that has put him or her at a disadvantage.

Two, the source explaining things has to be smarter than the stranger, and thus, smarter than your audience. If what’s being explained is something we can figure out on our own (or something that we’ll never need to know) then the Source is wasting everyone’s time by explaining it. Remember, you want information, not noise. Yeah, maybe for whatever reason this particular Source doesn’t know much about football, noir detective movies, or the eternal mystery that is woman, but on the topic they’re explaining this character needs to be an authority. It needs to be clear the Source’s knowledge dwarfs the ignorant stranger’s on this topic.

So there it is. If anyone tries to tell you only bad writers use exposition in a story, tell them it’s only the bad writers who don’t know how to use exposition. And then look smug while you eat your Captain Crunch.

Next time, by request, I want to talk about balloons.

Until then, go write.

January 9, 2010 / 2 Comments

The First Rule of Fight Club

Starting the year off late, which doesn’t set a good precedent, but also with a surprisingly clever pop-culture reference (as you’ll come to see), which does. If you don’t know the reference… go. Just go. I’m not joking, please leave now.

All those wanna-bes and posers gone?
Good. So, I figured I’d start by ranting about something I see crop up more and more in fiction. Would-be screenwriters, this week might be a bit thin for you, but if you follow along, who knows, I may say something clever.
Anyway, there’s a fiction writer (and sometimes writing coach) named Damon Knight who points out that first person is really a bit of a trap. A lot of people use it because they think it makes their story more personal, more realistic, and easier to get into. It also creates an instant character in the story—the narrator.
Truth is, though, first person is one of the most difficult tenses to write well. It isn’t personal, it isn’t realistic, and it makes it extremely difficult to create a character. I mean if it’s so easy, why aren’t the so-called hacks like Stephen King or Dean Koontz using it more often? Oh, sure, King’s written a few first person short stories, a novella or two, but the vast majority of his work is plain old third person perspective.
The reasons first person is so tough are kind of invisible, which is why it’s a trap. They’re things that make perfect sense when they get pointed out, but until then… well, it’s easy to wander in, set off a dozen tripwires, step into the beam of light, and suddenly you’re at the bottom of a deep hole. Hopefully not one filled with stakes.
To be clear, I’m not saying first person is a bad tense to write a story in. Far from it. Some of my favorite stories are written from this perspective, and it is some gorgeous, genius writing. It’s definitely not an easy viewpoint, though. Even experienced writers will run into a lot of problems with it, and inexperienced writers will often hit them at terminal velocity.
Here are a couple of those hidden problems. If you’ve got a first person story, you may want to take a glance through and make sure it doesn’t suffer from any of them.

The first problem is suspense and tension. You’ve probably heard this one before, because it’s one of the first issues that needs to be addressed in a story with this perspective. Any story has to have a degree of conflict and tension, but in a first person story a thick layer of that tension is scraped off the top because of the format. If we’re only halfway through the book, we know there has to be more than the narrator’s tale than just getting the girl. We also know the main character isn’t going to be killed in a first person tale because… well, they’re telling us the story.
Yeah, there’ve been a couple clever stories that have gotten around this roadblock, but they usually do it with a bit of a cop out. At this point, enough stories have revealed their first-person character is a ghost, angel, vampire, or some such thing that this reveal is probably just going to frustrate or bore readers more than anything else.
From this angle, writing in first person just drives us into a corner.

Next, first person is a very limited viewpoint. The reader can only see, hear, and experience things the main character does. We never get to see the other side of the door and we have no idea what happens to Wakko when he leaves the room. We don’t get the suspense of us knowing something’s happening that the character doesn’t know about. This also means we can’t be privy to extra detail, nor can we have any doubt if something did or didn’t register with the main character.
By its very nature, this also requires most first person stories to be told from a very “average-man” level. If the character is too smart and figures things out too fast, it kills the story. If said character is rock-stupid and can’t solve a single problem, it kills the story and frustrates the reader. Consider that Sir Arthur Conan Doyle’s detective stories are told in first person, but not by Holmes. They’re told by Watson, a very smart and able doctor–but nowhere near the range of his best friend.
So, from this angle, writing in first person drives us into another corner. A different corner, yes, but a corner nonetheless.

Another problem that relates back to viewpoint is that you can’t have forward motion in your story without action, and the common way action grinds to a halt is when the writer stops for description. I mentioned a while back that the problem with pausing to describe details about the main character‘s height, weight, eye and hair color, shoe size, skin tone, education, and preferred underwear color (sorry Facebook folks) is that everything comes to a halt while we do.
This kind of gear-grinding stop is bad enough in a regular story, but in a first person story what’s the only way we can get this description? That’s right– if the main character starts talking about themselves. And what would you think of me if I spent the next ten or fifteen minutes talking about my chiseled abs, broad shoulders, or rock hard glutes (all of which, I can assure you, are a complete fabrication).
So in a first person story, this kind of description brings the story to a halt and it makes your main character look more than a bit egotistical. What kind of woman writes two pages in her diary about how hot she is? How much of a ninja are you if you pause to admire your posture and build in a convenient mirror?
Heck, imagine how awkward this would seem in a horror or adventure story? I open the door to reveal the armed terrorist/ hungry zombie/ angry ninja and I pause to describe them as they’re leaping at me. The thing is, we see a lot faster than we can write or read. My first person character may register a lot of details, but it’s a very tricky balance leaving those details in or out during moments of action. I can notice the ninja is a woman with green eyes and a wisp of red hair peeking out of her hood, but if I pause to say that it seems that she’s just standing there in a very un-ninja-ish way. If I describe her afterwards, I now have to pause and refer back to something the character actually saw two or three pages back.
And so, here we are, written into a corner again.
For the record, I’ve just decided the word for a female ninja will be ninjette. At least for our purposes here. Just thought I’d get that in writing.
Now, Knight has a nice exercise in his book Creating Short Fiction. What he suggests is to rewrite a few chapters into third person with as few changes as possible. Don’t restructure, don’t add anything– just turn me into him or her. He really suggests rewriting the whole thing, but he’s usually talking about short stories. Twenty or thirty pages will do for most of us here.
Once you’ve done this, re-read your story. If the character you had in first person has vanished, it’s because there wasn’t a character there to start with. Just the illusion of one. If your story vanishes… well, there’s some work to be done. That’s the trick of first person, and why you have to be careful with it. It gives the impression of creating a personality and defining a person, but it rarely does.
This ranty blog (any blog, really) is a great example of a first person trick. I may seem personable, funny, and clever–but do any of you reading this actually know me? Okay, granted, a handful actually do, but I know there’s another, much larger handful that wouldn’t know me if they bumped into me on the street. It feels like you know me, my likes, my dislikes–you may even have an image of me in your head. Once you stop and think about it, though… you really don’t. Try writing down a rough character sketch of me based off the two or twenty times you’ve read something here and you’ll be surprised how little there really is. If I rewrote this post as a third-person column I would vanish altogether.
Which is a great time to wrap this up.
Next week I’d like to take a moment to re-introduce the blog for those who came in late. It’s still early in 2010 and I’ve been at this for almost a year and a half, so it might be good for all of us to recap.
Until then, go write.
September 10, 2008 / 1 Comment

The Ignorant Stranger

Exposition gets a bad rap.

People like to shriek that exposition kills a story, brings things to a grinding halt, and you’ll never make a sale if you use a lot of exposition. It’s an easy target, which is why lots of gurus warn against it and so many people latch onto it as an ironclad rule to be obeyed until the end of time. They can’t figure out how to do it, therefore no one should do it.

Of course, exposition isn’t a problem in and of itself, only when it’s part of bad writing. Honestly, you need to have exposition at some point or your story’s probably going to leave a lot of unanswered questions (and not in the good way). If you want proof, just look at a handful of the mildly successful movies or novels that use tons of exposition.

Star Wars – Ignoring the fact every movie in this series begins with a two minute text scroll, let’s look at the classic first film. Obi Wan spends a good four or five minutes explaining to Luke what the Force is and how it works. Darth Vader has to explain his relationship with Obi-Wan. The rebels have to explain the plans to the Death Star and how they’ll exploit its weakness.

Shogun—James Clavell’s best selling novel involves constant explanation as Captain Blackthorne, called Anji-san (Sir Pilot) by his captors, is forced to learn the Japanese language and culture in order to survive. He has to learn from scratch and drags the audience along with him.

Raiders of the Lost Ark – Right in the beginning of the film, Indiana Jones and Marcus Brody have to tell the two visiting federal agents about the legend of the Ark, its mythic powers, and where it may be hidden, a lecture that comes complete with pictures and chalkboard diagrams. Note that the two Feds don’t need to explain who the Nazis are and why they’re bad—everyone knows this.

The DaVinci Code – In Dan Brown’s bestselling novel, which pauses to explain historical details every ten or fifteen pages or so, Langdon and Sophie pause for two whole chapters in Leigh Teabing’s library while he relates a dozen or so different hypotheses about the blood line of Jesus, his relationship with Mary Magdalene, and how the Catholic Church has corrupted the Bible over the centuries to serve their own needs.

The Matrix—This movie has a staggering amount of exposition considering it’s known as a dynamic action film. It begins with characters discussing Neo (in voice-over no less), moves through Trinity and Morpheus each describing the mystery of the Matrix, and then Morpheus explaining the truth of it once Neo wakes up in the real world. The crew is explaining things constantly as Neo’s training begins. Cypher gets a little speech, so does Agent Smith… the exposition just goes on and on and on in this film.

Now, Damon Knight makes an interesting point in his book Creating Short Fiction (go buy it—most of his lessons are universal for fiction writing). A fact you don’t know that’s presented to you is information. It holds your attention for the sheer reason it’s something new. A fact you already know that’s presented to you is noise. It’s something you want to ignore and block out so you can get past it and back to the good stuff. This is why a lot of exposition fails—it’s information the audience either already knows or would be able to figure out on their own with minimal effort.

I’ll add one other tenet to that little point. Relevance. Information the reader needs for this story is vital. Information that has nothing to do with the story is wasting time and space. The catch here is the audience won’t know if something’s relevant or not until the final scene or the last page (although sometimes it’s painfully obvious). Notice in the above-mentioned scene from Raiders of the Lost Ark, the good Doctor Jones doesn’t progress into a lecture on Masada, the fortress-city where almost a thousand Jews were besieged by the Romans in 70 AD before committing mass suicide rather than be captured. The first time we all sat down, we wouldn’t’ve know any better and I have no doubt screenwriter Lawrence Kasdan could give us a completely gripping lecture on Masada. But then we’d reach the end of the film and say “What the hell was all that stuff about a fortress in there for?” Masada has nothing to do with the story of Raiders, which is why no one talks about it.

All those stories mentioned up above manage to pull off their reams of dialogue because they all do it essentially the same way. People in the know are giving information to people not in the know who need it. Years ago while writing one of my very first DVD reviews (for the miniseries adaptation of Shogun, actually) I came up with a term for this which I call the ignorant stranger. It’s when a character who is a source of information gets to do an infodump on a less-educated character. The name comes from John Blackthorne, the main character of Shogun, a man who is ignorant of Japan’s culture and language for the simple reason that it’s all completely new to him—an ignorant stranger. This is a surefire, never-fail, completely acceptable way to have exposition in your writing.

So, keeping that in mind, here’s the only two things you must remember so you can pull off the ignorant stranger in your writing.

First, the ignorant stranger can’t actually be stupid—there’s a big difference between ignorance and stupidity. It’s this particular situation that has put him, her, or them at a disadvantage. Your stranger has to be on the same level as your readers or viewers. We, the audience, are learning alongside them, so we don’t want to wait while the stranger’s educated on where hamburgers come from, what firemen do for a living, where Oklahoma is on a map, and who his friends and family members are.

Second, the Source explaining things has to be smarter than the stranger, and thus, smarter than your audience. If what’s being explained is something we can figure out on our own, or something that we’ll never need to know (within the scope of this story), then the Source is wasting their time, the ignorant stranger’s, and ours by explaining it. Remember, you want information, not noise. Yeah, maybe for whatever reason the Source doesn’t know much about U.S. currency, cooking on a grill, or this thing called love, but on the topic they’re explaining this character needs to be an authority. They don’t need a degree of some kind, the audience just needs to be clear the Source’s knowledge and understanding dwarf the ignorant stranger’s.

That’s it. Follow those two simple rules and you’ll be amazed how well exposition can work in your novels, screenplays, and short stories.

Speaking of which… aren’t you supposed to be writing?

Categories