Perverts. Your minds always go there, don’t they?

By the way, I’d like to take this moment to note that this marks my 100th post on this here ranty blog. Who would’ve ever guessed I’d have this much to say about writing. Well, without it devolving into incoherent jabbering and a lot of gestures.

Anyway…

There’s a comic book writer/ novelist/ screenwriter by the name of Peter David. If you’re reading this and haven’t heard of him, I highly recommend hitting Borders or Amazon and grabbing one or three samples of his work. The man knows how to write characters like no one else.

In one of the early issues of his run on the comic X-Factor, David had someone make the keen observation that every super-hero group has a strong guy. The immediate joke was to explain the huge muscle-bound guy on the team (who was then inspired to adopt the codename “Strong Guy”), but there’s a larger point to be made with this.

Every superhero group has a strong guy because at some point they need a strong guy. As a writer, the reason you have a character who can bench press 90 tons is because at some point in the story there will be a Sherman Tank that needs throwing, a house-sized boulder that needs to be shifted, or a giant ninja-robot between your team and their ultimate goal. You put the strong guy on the team because you’re going to give him a chance to show off his strength.

This has been an enduring theme in literature for centuries. The mismatched team where every member eventually becomes necessary. You’ve probably heard some variation on the classic fairy tale about the six friends. A young man sets out to perform some tasks so he can win the hand of a princess. During his journeys he becomes friends with the fastest man in the world, the strongest man in the world, the hungriest man in the world, the man with the sharpest vision in the world, and so on. Oddly enough, to complete his tasks the young man needs someone who is incredibly fast, strong, hungry, etc. Charles McKeown and Terry Gilliam adapted this tale, by the way, and called it The Adventures of Baron Munchausen.

Now, there’s a simple corollary to this I’m sure most of you have already figured out. If there isn’t something for the strong guy to do, you shouldn’t have a strong guy on your team. You’ll notice few superhero groups include someone who can blink at amazing speed. None of the variations of the Grimm’s fairy tale feature someone who can shoe oxen better than anyone else in the world. In no version of the Ocean’s 11 films do they make a point of getting a great pastry chef on their team (although I freely admit I never saw the last one so… maybe they did). These people all may be fascinating in their own way, but they don’t really contribute anything to the particular story being told. High-speed blinking may be superhuman and somewhat interesting, but it’s also kind of useless when you’re saving the world from Galactus.

Thing is, this little observation holds for every character, not just ones in genre stories. If the character isn’t doing anything and doesn’t contribute, why are they there? As the name implies, a supporting character should be helping to hold things up. Not big things–that’s what your main characters are for–but they’re bearing the load around the perimeter and on the edges. They keep the tone balanced, give the main characters a sounding board for ideas and exposition, and help sustain the suspension of disbelief. If you’ll pardon my saying it, they’re the ones keeping it real.

A good chunk of the time, though, a supporting character get stuck into a story for the wrong reasons. Often it’s because the writer has seen a similar character in a similar story, so said writer just wedges a rough copy of that character into their own story. It doesn’t matter if this character does anything or not, there’s just this unspoken assumption they have to be there. A lot of comic-relief characters come about this way. Fledgling comedy writers stick in the goofy sidekick or wild neighbor because comedies always have a goofy sidekick or wild neighbor. Zorro, the Green Hornet, and Batman all have helpful manservants, so I should stick one into my adaptations of Doctor Fate, right?

Y’see, Timmy, much like the golden rule, just because something works in your story doesn’t mean it’s going to work in my story. This is especially true of the characters. I can’t just cram a random person into my novel or screenplay because there’s a good chance they don’t mesh with the story or the existing characters. Forcing them in means they’re unnatural, which usually means they’ve just become unbelievable characters within the scope of this story. Why would Phoebe and Dot possibly be friends when they’re complete opposites in every way? How could a bumbler like Yakko have possibly made it onto this elite squad of high-tech thieves? Why would dark ninja overlord Wakko allow someone like me (or worse, me as played by Rob Schneider) to stumble along behind him on his mission of vengeance? There has to be a reason for a supporting character to be in your story, otherwise they’re just eating up words and pages that should be spent on your main characters.

Speaking of which, a follow up problem is when main characters take a backseat to the supporting characters. We’re following Wakko for the whole manuscript, but suddenly at the end Chicken Boo dashes in and defuses the bomb, gets the girl, or lands the plane. To be terribly honest, I did this myself in the first two drafts of Ex-Heroes. It wasn’t St. George that beat the monster in the end, but a guy on the walls of the Mount named Ilya. It was still a fun, cool scene, but what I’d effectively done with it was made my hero useless. He didn’t save the day–some regular guy with a rifle did. Not impossible, but also not what this story was about.

Main characters do the main things. Supporting characters do lesser things. In the movie Aliens, Corporal Hicks survives and helps Ripley and Newt escape the hiveworld because he’s a main character. Vice versa, he’s a main character because he survives and helps Ripley and Newt escape the hiveworld. Aliens doesn’t focus on Frost or Apone or even Vasquez because they’re the lesser characters. One of the reason we can tell this is because they die early on in the story.

It sounds a bit like circular logic, I admit. However, don’t look at it from the story point of view (where it’s confusing) but from the storytelling point of view. If Hicks wasn’t the main character, why would he survive over someone else? Why would he succeed where others fail? I’m not a good storyteller if the focus of my tale isn’t about the people who survive and succeed (assuming anyone does survive this particular story).

Dan Abnett has a habit of introducing characters in his Gaunt’s Ghosts series, giving us a name and a thumbnail description, showing them in a few action scenes, and then killing them. Why? Because the Ghosts are fighting a war. They’re almost constantly wrapped up in one battle or another, and, awful as it is to say, it’s not a believable war when only the bad guys die. Abnett introduces these secondary characters–and then often shoots them in the head– to remind the reader how brutal life is on the battlefield. Even the sci-fi battlefield of the future.

Next time around, on a somewhat similar note, I’d like to prattle on about your story. The one you want to tell.

Until then, go write.

There’s a phrase that gets tossed around a lot in Hollywood, usually by directors, actors, and producers. It’s kind of insulting and condescending the way it gets used, but there is a degree of truth to it. That phrase is…

The script is just a blueprint.

Now, the reason I say that’s condescending is because this gets used by directors who want to justify rewriting scenes and actors who want to justify changing (or just making up) lines. We’d never say the director’s just there to block out the scene or the actor’s just supposed to read the dialogue, but for some reason it’s acceptable to say the writer is just a stepping stone for everyone else’s brilliance.

Here’s my take on this. There are numerous stories in Hollywood of brilliant scripts that became average-to-sub-par movies when the director and actors were done with them. Pay It Forward. Excess Baggage. Wanted. Little Monsters. Heck, even Suburban Commando. Yeah, you’re cringing, but have you ever read the original screenplays for any of these films? The ones that sold and got the project greenlit? Most of them were damned entertaining, and one or two of them were just phenomenal. Who do you think’s responsible for the movies that came out of these scripts? The key grip? The wardrobe supervisor? Heck, the writer of one recently released film confided to me that the whole reason the movie went through numerous expensive reshoots was because the director had made “a few changes” during the original shoot which destroyed the character arcs for both protagonists (much to the frustration of both the screenwriter and the producers).

Now, to be fair, how often have you heard of a brilliant director and great actors being saddled with a sub-par script which sank their film? A few times for that, too, right?

Riddle me this, though, Timmy– if the script was sub-par, why did they decide to go into production with it?

Doesn’t make sense, does it? No one’s going to build a house if the blueprints don’t include a foundation, a front door, or a staircase to the second floor. Considering how much more a motion picture costs than a house, does anyone here really believe a studio would march into production with a crap script? That a director would agree to work on it? That actors would rush to be in it?

Unless, of course, those people don’t know what they’re doing, either…

But I digress…

As I said up above, there is some truth to the script as a blueprint analogy. No matter what Hollywood and auteur wankers like to say, the screenwriter is the architect of the movie. They’re the one who sits down with a vision and an idea that gets committed to paper and referred to throughout the construction process. Even if the film is an adaptation or a remake, it’s the writer who has to plan it all out and decide what to keep and what to discard. There’s a reason the architect said put the door here, the window there, and the support beam right there. A screenplay is a blueprint, and when you don’t follow the blueprints–or don’t know how to read them– you get cracks, crumbling, and sometimes a full-on collapse.

However…

(Yeah, there’s a however. If there wasn’t you wouldn’t need to read any of this,would you?)

This does not mean the screenwriter is the end-all, be-all of the process. A good architect knows there’s a lot of stuff he or she gets to shape and insist on, but just as many that they have no control over. Frank Lloyd Wright designed some of the most beautiful structures in the world, but he didn’t have a say on the appliances in the kitchen, the living room carpet, or what the owners decided to use for bedlinen. There’s a point the architect has absolute control, but there’s also a point where the blueprints have to get handed over to the contractor, the painter, and the interior decorator. Not to mention the people who are buying the house. Heck, if the architect gets hired to design a beach house and they turned in plans for a Victorian office building, it doesn’t matter how good that office building is, they’re not getting another job.

Let’s stick with this metaphor for a few more paragraphs. Imagine you hired an architect to design your new house and the first two pages of the plans are an explanation of how the building may look odd but is actually modelled after the house the architect lived in as a child. That house was built by his great-uncle who had fought in World War Two and returned home to Boston afterwards to build a home that resembled the structures he’d seen while fighting in the Pacific Rim. None of this has anything to do with your house, granted, but the architect felt it was worth mentioning. And eating up two pages of blueprints with.

How are the carpenters going to react when they see that half of every page is instructions on how to use a circular saw, lists of preferred nails, and step-by-step guides for using a measuring tape? There’s an extra 50 pages worth of blueprints here telling everyone on the construction crew how to do their jobs–jobs that more often than not the architect doesn’t know how to do himself. How far in will everyone get before they start ignoring everything the architect’s written alongside the diagrams? And then what happens when there finally is something important in all those notes?

Anyone who’s ever taken drafting knows how important clean lines are. If the architect’s cluttered every diagram up by drawing in wood grains or micromanaging every stud and strut, it just get confusing. We don’t need to see all those individual nails, but we do need to see that load-bearing beam and it’s getting lost in the glut of useless detail. A good foreman knows there needs to be a load-bearing beam somewhere in this wall, and if he can’t find it in the blueprints he’ll just put it in himself. If that messes up plans for the second floor fireplace… ah, well.

One of the biggest mistakes beginners make with screenplays is not understanding what a screenplay is. It’s not an exhaustive list of instructions for the director and the crew. It isn’t a magical tool for making actors do and say certain precise things. It’s not a chance to dazzle people with high-falutin’ vocabulary or hyper-detailed imagery. It’s a framework.

A screenplay–a good screenplay– is the underlying structure of a film. It’s the solid framework everything else is built on. It’s careful balancing act of minimal, concise language that’s got to have as much punch and nuance to it as humanly possible. It isn’t choked with excess verbiage or screen directions in the same way the plans for a house don’t list china patterns and carpet selections.

It is the blueprint of the film.

Just not in that insulting, condescending way those other folks say it.

Next time, I’d like to talk about something that lifts and supports.

No, not that. You can find that lots of other places online.

Until next week, go write.

Either my latest rants have been pure gold no one can argue with or a lot of you really hated me using LOST as an extended example. Haven’t seen any comments in weeks.

Speaking of things you don’t see, this rant’s title is another one of those clever pop culture references. Anyone remember it?

Okay, fine, I’ll explain.

“To See The Invisible Man” is the title of a Twilight Zone episode adapted by Stephen Barnes from an old Robert Silverberg short story. It’s not one of the classic Zones, but one of the newer ones when the show was revived in the mid-‘80s. It’s the tale of a man in a somewhat-utopian society who is sentenced to a year of “public invisibility” because of his selfish, antisocial behavior. He isn’t actually turned invisible, however. He just gets a small brand on his forehead which tells everyone to ignore him. That’s the curse of it. They really can see and hear and feel him–and he knows they can– but no one will react to him. Even when he desperately wants and needs to be acknowledged (there’s an eerie scene in a hospital emergency room), people pretend he’s not there. As we find out later in the story, seeing an invisible person is a major crime.

In a way, this serves as a clever little metaphor for being a writer. The reader knows the writer is there, that you’ve crafted and shaped these words on the page, but they don’t want to admit you’re leaning over their shoulder. They just want to go on their merry way and pretend they’re alone with the book. As such, the worst thing the writer can do is draw attention to themselves.

For many would be writers, the temptation is to embellish the pixilated page with an exuberant flourish of verbiage which exhibits not only the vocabulary we’re capable of as proficient anecdotists (far above any paltry amanuensis), but also how we can bend grammar to our will; the elaborate and subtle metaphors we can craft; and the clever intricacies we can interweave betwixt the threads of character, plot, and theme.

For the record, it took me almost fifteen minutes to craft that impenetrable sentence. Yes, it looks like a paragraph but it’s just one sentence. A long, sprawling sentence that really tempted you to skim, didn’t it? Heck, let’s be honest. I bet after tripping over your second or third obscure word, at least half of you started skimming, didn’t you?

Y’see, Timmy, every time we make the reader hesitate or pause just for a second, we’re breaking the flow of the story. We’re encouraging them to skim at best, put the manuscript down at worst. The reader should forget they’re paging through the latest Wakko Warner novel or screenplay, perhaps even forget they’re reading a written work altogether. This happens, odd as it sounds, when they forget they’re reading. And the easiest way to make that happen is for them not to see the writing. It’s tempting to wave our arms and shout and try to get the reader to admit they can see us, but all this does is ruin things for everyone. It’s like Sherlock Holmes showing how he came to his amazing deductions or a magician explaining their greatest illusion. That moment is when the whole thing falls apart.

As writers, we need to be invisible. Oh, we want our characters to be seen. We want our dialogue to be heard. We want our action and passion and suspense to leave people breathless. But we are just distractions. If you think about it, who’s the more impressive tough guy– the one who commits unimaginable acts of violence, or the one who doesn’t have to commit those acts? Being able to restrain yourself is just as impressive as how excessive you can be. Less of us is more of the story.

Here’s a few simple ways to keep your literary head down.

Vocabulary— We all know what bright means, but effulgent can make us pause for a moment. That guy can be bald or he can be glabrous. Some sneakers are black with a bit of red and some are atrementous tinged with titian.

A huge problem I see is writers with ego problems. They think they’re cleverer than anyone else, and they’re determined to prove it. More often than not, the writer latches onto (or looks up) obscure and flowery words because they didn’t want to use something “common” in their literary masterpiece. These folks write sprawling, impenetrable prose that makes it sound like they spend their free time wanking off to a thesaurus. All too often they’ll try to defend this wheelbarrow of wordplay by saying it’s the reader’s fault for having such a limited vocabulary. After all, everyone knows what it means if I say I’m going to cast a bantam gallet towards an embrasure, right?

Any word a writer chooses just to draw attention, to prove they don’t need to use a common word, is the wrong word. Any word that makes the reader stop reading and start analyzing is the wrong word. Period. You can try to justify your word choice any way you like, but absolutely no one is picking up your book or looking at your screenplay hoping for a vocabulary lesson. When the reader can’t figure out what’s being said for the fourth or fifth time and decides to toss that manuscript in the big pile on the left… there’s only one person to blame.

(It’s not them, in case you had any lingering thoughts on the matter)

(By the way, it just means I’m going to throw a small stone at a window)

Structure— Like obscure vocabulary, convoluted sentence structure is often the sign of a writer’s ego. One of the most common ways this manifests is to insist on grammatical and structural perfection. This often mean a rigid, formal text and very stiff dialogue. These writers are so insistent on proving they know the correct way to write that their words come across as forced and artificial.

The second most common is needless complication. If something can be described in five words, these writers will manage to do it in thirty, and I guarantee at least half a dozen of those words you’ll have to stop and look up (see above). This is where you find folks that use phrases like “seemed to be” or “appeared to be.” Some of these storytellers also go the non-linear route, even though nothing in their story gets improved by this pointless scrambling.

All of this can be an instant killer in screenplays, because most professional readers won’t put up with it. Your writing needs to be clean, simple, and natural. If there isn’t an in-story reason for it to be overcomplicated, it shouldn’t be.

Said— People will never notice if you use said. Said is invisible. What they notice is when your characters respond, retort, exclaim, pontificate, depose, demand, muse, mutter, sneer, shout, snarl, growl, whimper, whisper, hiss, yelp, exclaim, or ejaculate. Yes, stop giggling, it was a common dialogue descriptor for many years. Once you’ve got three or four characters doing all this (instead of just saying things) you shouldn’t be surprised if your audience stops reading to shrug or snicker. Usually while they’re pointing at you.

Granted, there are times where characters are shouting or whispering or hissing. Overall, though, they’re just going to be saying things. So don’t overcomplicate things and draw attention to yourself.

Names. If used in moderation, names are invisible. They’re just shorthand for the mental image of a character. It’s also worth mentioning that simpler, more common names blend into your writing easier than rare or unnatural ones. A reader can glide past Tony but might stumble a bit on Antonio. Edward is easier on the frontal lobe than Ezekiel, and they’re all nothing compared to Bannakaffalatta.

It’s worth mentioning a little note there for the genre folks. When writing sci-fi or fantasy, many fledgling writers feel the need to rename everything. The characters have all-new, created-for-this-world names. So do their pets. And their gods. And their elements. And their system of weights and measures. Off the top of my head, I would say 90% or this is a waste of time and a distraction. Your elaborate fantasy world will not collapse if the giant, fire-breathing lizards are called dragons, but it might if you insist on calling them pyroreptillicans.

A good rule of thumb–when you’ve made up a name like Grothnixyettiq for one of your characters (or their mode of transport, or their homeland, or the way they measure distance), take a moment and try to say it out loud. Note how long it takes you to figure out how to say it. Now email or text it to a friend, give them a call, and ask them to say it out loud. No hints or clues. Just ask them to say that word you wrote. If their pronunciation doesn’t match yours, you should really use a simpler word.

Always remember that moderation is key. If any name repeats too often, it begins to get cumbersome. Even a simple name like Dot can stack up. When I see a paragraph about Dot reading Dot’s book out by Dot’s pool shortly before Dot decided it was too hot outside and Dot went in where it was air conditioned… well, personally at that point I start counting them. Which means I’m not reading the story, I’m auditing it.

This is why we have…

Pronouns. When proper names start to stack up, we switch to the pronoun. Just like names are shorthand for story elements, pronouns are shorthand for those names. When nouns start to clutter up your writing, they’re there to leap in and shoulder the weight. It’s how Yakko becomes he, that mysterious island becomes there, and the Cerberus Battle Armor System becomes it.

The catch here is to make sure your pronouns are clear, because the moment someone gets confused about which it you’re referring to, they’ve just stopped reading your story and started studying the page. A good rule of thumb—after you’ve referred to Dot as she half a dozen or so times, drop her name back in once. It’s been long enough it won’t look repetitive, and it’s a gentle reminder of who she is.

And there they are. A few simple ways to stay invisible.

Next week, just for whatever budding screenwriters happen to stumble across this site on a regular basis, a few notes on drafting. In the construction sense.

Until then, don’t let me see you writing.

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.