July 21, 2011 / 1 Comment

Tastes Like Chicken

There’s about a hundred jokes in that title. Hopefully one or two of them will fit with this week’s little rant…

Sorry about missing last week, by the way. I’ve been trying to stay ahead on the new project and prepare for Comic-Con, and the blog somehow slipped right past me. Shouldn’t happen again. Well, not for a little while, anyway.

My dad is a phenomenal cook. Have I ever mentioned that? For a guy who refuses to retire and spends his working hours writing up safety protocols, his cooking skills are just fantastic. There was a time when my mother and brother and I were all trying to convince him to open a restaurant, but he wasn’t interested. Cooking was the fun thing he did to relax. He didn’t want to take that extra step and make a job out of it.

We were all fine with it. Mostly because it worked out great for us. My dad can turn Thanksgiving leftovers into a sandwich you’d gladly pay twelve bucks for, so I’m definitely not going to complain. Not as long as I keep getting invited to Thanksgiving.

No, really, this is all relevant. You’ll understand why soon.

As it happens, I’ve had several different friends and acquaintances ask me for writing advice over the past few months. Granted, they all had different skill levels, but none of their questions were really about writing. They were about improving by buying the right books or starting blogs or catching the interest of publishers. I tried to answer as politely as I could, but I’m pretty sure none of them were really listening. I know at least two weren’t.

So, here’s a better way to look at it.

Should you go to cooking school?

I’m sure a lot of you are shaking your heads at that one, but let’s stop and consider it. Cooking is a great metaphor for writing, on a bunch of levels. It’s an art. The end product has to hit certain benchmarks but it also, to a fair degree, is a matter of personal taste. A few rare people have a natural knack for it but most of us need lots of practice. It’s something most of us do every day, but we know only a small percentage of people are good enough at it to deserve recognition or make a living off it.

So, if you want to get better at cooking, should you go to cooking school?

Right up front, let’s be clear. Any cooking school is going to expect that you have a minimum degree of experience and knowledge right off the bat. They’ll assume you can tell flour from sugar on sight and that you know the difference between basil and oregano. The point of cooking school is not to teach you how to make peanut butter sandwiches. If you’re still struggling with these things, cooking school is really a waste of your time and money.

Now, if you plan on making a living off food, cooking school is almost a necessity at some point. Not everyone needs to take classes on desserts and soups and seafood. We’re just never going to use them. There’s about a hundred better, cheaper things we could be doing to improve our cooking skills. There are free recipes online and on the back of most staple ingredients. There are tons of cooking shows and podcasts where we can learn little tips.

And of course, the easiest thing we can do—what hopefully most of you have already seen as the obvious thing I’ve skirted around—is cook stuff. Just get in the kitchen and cook. If I want to be a better cook, the most useful way to spend my time is cooking. Makes sense, yes?

Y’see, Timmy, if you want to be a chef, there’s a point that you need to take some classes, and you’re probably going to keep skimming through cookbooks forever. But it’s all going to come down to spending time in the kitchen. That’s how you become a good cook. Going to Harvard doesn’t automatically make you a great journalist and going to MIT doesn’t guarantee you’ll be a phenomenal engineer. At the end of the day, it all comes down to just doing the work and how hard you’ve been doing it.

In fact, there’s a fair argument to be made that cooking school won’t help you become a great chef. It can make you into a good chef, but the greatness comes when you go out and start doing stuff on your own. You don’t hear about Wolfgang Puck or Gordon Ramsay taking classes. Neither of them probably has in over a decade, at least. If you just keep going back to cooking school and never really stepping into the kitchen, it should be clear you’re dooming yourself to a life of mediocrity (at least, on the food-preparation front).

You’ll always learn more by doing the job than you will by reading books about doing the job. Doing the job is almost always more educational than taking classes about doing the job.

So, with all that being said… should you go to cooking school?

A bit clearer now, isn’t it?

This pile of rants is cooking school, in a way. Not one of the great French academies, but a bit higher up than the Home Ec class you might’ve taken in seventh grade (if you’re of a certain age). Probably better than those cookbooks aimed at recent college grads.

A few people who are reading this right now desperately want advice on getting agents and publishers interested, but they haven’t bothered to learn how to spell. They’re convinced they’ll learn some magic structure or word (mellonballer…) that will make it all easy for them. They’re so desperate to learn the secrets of a good Hollandaise sauce they haven’t bothered to learn how to boil an egg.

I’m guessing most of you can use about half of the various tips and suggestions I throw up every week. There’s weeks that you learn a clever trick or new approach to an issue in your writing. There’s also those weeks you just skim because it’s something you’ve got a good grip on.

And a few of you… well, you’re probably just killing time here, aren’t you? There isn’t much I go over that you don’t already know. You’re just putting off doing some actual work for half an hour or so.

Learn the basics first. Don’t worry about level five before you’ve mastered level one. If you aren’t sure what the basics are, that’s probably a good sign you haven’t mastered them yet. I’m not being glib. If you’re reading this rant with the goal of becoming a better writer, you should already know what it means when someone says “the basics of writing.”

And then, once you’ve hit that level, start thinking about cooking school.

Next time, just for something different, let’s chat about slasher porn and why it’s not as bad as you may think.

(Yeah, I’m probably misleading you a little with that title…)

Until then, go write.

July 8, 2011 / 2 Comments

Can You Describe the Problem?

First off, a bit of shameless self-promotion (because I haven’t done any in weeks now)…

Ex-Patriots, my third novel and the sequel to Ex-Heroes got a slightly early release this week from Audible.com. It’s coming out in paper/e-book format in September, but if any of you are impatient you can go grab it now. There’s also a bunch of videos for their ZombieFest promotion where a bunch of folks wrote in with questions for the authors of all the featured books. So if you’ve ever wondered just how goofy I sound in real life (or look, or act, or dress…) , here’s your big chance to find out.
And now, back to our previously scheduled pontification…
So, if you’ve been reading this pile of rants for a while, you know there was a point a few years back when I helped to run an online fantasy MUD. If you’re not familiar with the term, a MUD is a multi-user dungeon. Because the game is entirely text-dependent, it was a lot like writing or reading a story. In fact, it was a great tool for polishing your writing, because if you got too long-winded with your words people wouldn’t be able to read them—the description would just scroll up the screen and vanish as other things continued to happen. You had to describe things, but you couldn’t get bogged down in useless details. People would either ignore it or lose their forward momentum as they went back to read it.
One of the things staff members had to monitor was the descriptions players wrote up for their characters. We checked for basic spelling and grammar (“His dark hair compliments his thin lips” was a common phrase). We also checked to make sure the style and wording, by way of the game’s narrative nature, wasn’t forcing actions or reactions on other players (“This scarred man may be the most terrifying person you have ever seen, and the mere sight of him makes your stomach churn with fear.”)
Now, I told you all that so I could tell you this little story…
One day, a staffer called attention to the description of a new female character. Y’see, when the game was originally built the coders left some stuff at default settings, and one of those things was the range for the description string. It was ridiculously high, but no one had ever bothered to set it because… well, there were more important things to do. And, really, who would ever fill it, right?
Well, this player had figured out the high-end range and written a description that was yards and yards and yards of purple prose. On a rough guess, their character description was around five or six hundred words. Maybe more. When you accessed it, the first dozen or so lines automatically scrolled up and off the page because it was so long.
I’m sure some of you are already thinking of character sketches you’ve done that are far longer, but keep in mind, this is all just physical description. It isn’t personality quirks or dietary preferences or anything like that. By nature of the game, it’s not clothes or weapons or equipment, either.
Needless to say, we pointed out that it was excessively long and asked her to trim it. She refused. By her reasoning, since the buffer allowed such a long description, it had to be game-legal. And if people didn’t want to see it, they didn’t need to scroll back.
We pointed out that those first dozen lines contained all the gender and age information for the character. This wasn’t “optional” material, it was stuff other players needed to know.
Still, she refused.
Now, stepping away from my tale, let’s think about this for a moment. A writer is refusing to edit a description, while at the same time admitting most people are going to skim over it or ignore it altogether. Even when authorities on the topic are explaining why it doesn’t work, said author is steadfastly refusing to change.
Does this sound remotely like a writer who’s interested in having an audience?
A common problem for all writers is when description gets too excessive. We get caught up in giving all the details and nuances of this character or those rooms or that magnificent sword which seems to be stuck in a stone… a jagged, raw stone, although one could see hints of granite and shale and flecks of white quartz that gleamed like the teeth of ancient dragons, the likes of which the world had not seen in long millennia. So perhaps calling it “a” stone was a misnomer, for it seemed to have a rich ancestry and heritage written through its structure. This was, perhaps, several stones that had come together untold eons ago, perhaps even then sensing the greater purpose they would serve and the rough bed they would form for the sleeping blade. Or perhaps it was just a coincidence that the gleaming sword had found itself in this particular malformed mound of misshapen rock, and in truth any of the many stones scattered around this subterranean chamber could have been oh dear God I think I’m making myself sick.
As I was saying…
We go one and on and sometimes lose track of the fact that somebody’s going to have to read all this. And since most readers are more interested in the story, that active element of your writing, odds are they’re going to start skimming after the fourth or fifth flowery description which they’ve come to realize has no bearing on the story. At which point, any decent storyteller should question why they’re including stuff that people are just going to skim over.

Elmore Leonard famously said that when he writes he leaves out all the parts people would skip anyway. Alfred Hitchcock said drama is life with all the boring parts taken out. And I’ll tell you that a six hundred word description of how a character’s hair hangs over her ears is either wasting time or is going to bring things to a crashing halt.
As I’ve mentioned once or thrice before, this kind of overwriting is a deadly mistake in screenplays. Screenwriting is a very concise, minimal form of storytelling. One of the most common complaints I hear from professional readers is when the writer puts in piles of description that just doesn’t need to be there.
That, of course, leads to another issue with massive over-description. We all tend to form our own mental pictures of people and objects in stories. My lovely lady and I were chatting the other day about Lee Child’s character Jack Reacher and realized we both had very different ideas about what he looked like. That’s part of the joy of books. We can all have our own view of different characters like Taran Wanderer or Harry Bosch or St. George or Stu Redman. And nothing’s more distracting or disruptive than to be constantly reminded of all the many details the author’s putting in that don’t match up with that mental picture we’ve already formed.
Now, there’s another side to description, and that’s when writers never actually describe anything. Sometimes this is an attempt to invoke mystery or suspense (check out that dark figure across the street watching our main character). Other times it’s a way to evoke an emotional response with a clever metaphor or simile (when the knife sinks into your back and it’s like every painful sensation you’ve ever had in your life got balled up, hammered flat, and slipped beneath your shoulder blade).
And sometimes… well, sometimes it’s just a cheat. I can try to avoid the monster for as long as possible, which helps build suspense and dread, but eventually I need to say what it is. It’s not uncommon for a writer to try to find a way around an actual description at this point. After all, I’ve been hyping X for three-quarters of the manuscript now, and an honest description may not live up to all that hype.
I got to interview David Goyer (screenwriter of Blade, Batman Begins, and many others) a few years back. He’d just taken a turn in the director’s chair and I asked him if doing so had affected how he approached writing scripts. He laughed, admitted it had, and then told me a very funny story about working on a script with Guillermo del Toro. At one point, it seems, Goyer had “cheated” in the script and just described something as “a complete nightmare.” As they went through, del Toro pointed out this bit, shook his head, and said “What does that even mean? That’s boollshit.”
Which, Goyer admitted, it was. He’d dodged writing any sort of description because he knew it was something the director and art department guys would deal with. But he’d given them nothing to work with. Which was fine… until he was the director and under the gun to figure out what the hell it was that writer-Goyer couldn’t be bothered to put down on paper.
So, here’s an easy tip. It’s so easy I bet half of you will shake your head and ignore it. And some of you are probably already doing it without thinking about it.
If you’re going to describe something, have a reason to describe it. Thats’ it. Not only that, have a reason for the level of detail you’re using. A soldier in a war zone, a housewife, and a forensic examiner can all see a bullet hole in a person’s head, but they’re all going to treat it differently. And if it takes three or four paragraphs to explain what the housewife sees, where does that put the forensic examiner?
If you’re going to describe a person, have a reason for doing it. I’m betting nobody here can list off all the people they crossed paths with the last time they were pushing a cart through the grocery store. Oh, one or two might stand out in some small way, but let’s face it… there were probably close to a hundred. They just weren’t important in the long run. You can’t describe the police officer who gave you your last ticket, but you can probably give a lot of details about the last person you went out to dinner with.
Give descriptions the same weight you’d give characters or dialogue. Y’see, Timmy, if you waste them on the little things, they won’t have any strength when you get to the big things.
And then… well, then you’ve got nothing.
Next time, I’d like to ramble on about cooking school.
Until then, go write.
July 1, 2011 / 3 Comments

One Time Only

If at first you don’t succeed… destroy all evidence you ever made the attempt.

No, no, don’t do that…

A few years back I was working on a film set where we were staging a bank robbery. The director… well, let’s be polite and say he wasn’t quite as knowledgeable as he thought he was.

We ended up doing a big dolly track move that encompassed the whole scene. Then we did a series of tighter moves. Then we did a wide master of the scene and got all the coverage. Then we did a reverse master of the scene and started doing coverage on that. Then came all the reaction shots for everyone in the bank. And by this time, the crew was starting to grumble, because every one of us knew what was going wrong.

As it turned out, my department had an intern, and he was still watching all this with complete newbie glee. As the day (and the bank robbery) wore on and on, he asked me what everyone was getting so grumpy about. After all, weren’t these all cool shots? I agreed they were, but pointed out that at least half of them were a waste of time. When he asked why, I came up with this way to explain it.

“When all this gets cut together,” I told him, pointing at one of our extras “you can only use one shot of them robbing that bank teller. You can break it up a bit, but not much because it’s happening so fast. At the end of the day, you can only rob teller number five once, so filming nine different versions of her getting robbed is a waste of time. If this guy knew what he was doing, he’d just get the shots he was going to use and that’d be it.”

The intern took those words to heart, and two or three more times during that project he’d give me a nod on days when scenes were just dragging and say “You can only rob teller number five once.”

The point of the story being, I know at least one person has gotten something useful out of my rambling.

No, wait, sorry, the point is that when you’re telling a story you can’t do the same thing again and again and expect it to have the same weight.

There’s an idea in literary theory (sorry, I do have to go there now and then) which says you can only experience a story for the first time once. After that first time, your brain can’t help but restructure your view of the story to see it with more experienced eyes. If you’ve ever read a mystery novel for a second time, or maybe rewatched films like The Sixth Sense, Dead Again, or The Prestige, you know it’s a very different experience when you go through these stories a second time. Or a third time. But you can never, ever get that first time again. Even something like The Empire Strikes Back changes between the first and second exposure to the material.

This is why we all hate spoilers, because the innocence, so to speak, of that first experience is being taken away from us and we can never get it back. To be honest, this is also one of the problems I have with the “film school” approach to movies. A lot of these folks get taught to study and dissect films rather than to watch them, so the first time with the story is lost on these people. They never see the movie the way it was intended to be seen—they just jump straight to the second viewing. Which seems counterproductive when you want to learn how to do something. It’s like going to cooking school and never bothering to taste anything.

Anyway… I digress. But not by much.

There’s another aspect to doing the same thing more than once, and this is the idea of noise. A few times before I’ve brought up Damon Knight and his wonderful observation about facts. A fact we don’t know is information, but a fact we already know is noise. This is true even if we just learned the fact ten or fifteen pages earlier.

An example…

I read a book a while back where one piece of information was “revealed” four times. Essentially, character A discovered a mysterious South American temple that shouldn’t exist. Then A was killed and B found his notes, so B discovered the temple. B quickly related the story to C and then C explained the whole thing to D, so now D learned about the temple. And D… well D was pretty high-ranking, so he went to the President and told the whole Cabinet about the temple. And every single time people would have incredulous reactions and then the reader got the explanation of what the temple represented and who built and how we know it’s ten thousand years old and what we think it is.

Every. Single. Time.

Y’see, Timmy, that information is powerful the first time we hear it. Like so many things that get repeated, though, it loses power every time. In this case, it’s not just losing power, it’s taking a rapid plunge from information to noise.

Plus, it’s taken a huge emotional hit. Finding out that the pyramid strongly implied, if not proved, a pre-human civilization was amazing… the first time. The second time it was something we already knew, even if it was new to this particular character. The third time it was annoying. By the fourth time, personally, I was skimming.

Here’s an easier example, and one we’ve all probably dealt with at some point or another. Have you ever had someone tell a joke (or what they thought was a joke) and then they repeated the punchline when no one laughed? Maybe they repeated it two or three times. Perhaps they went after people one on one (“Hey, Timmy, did you hear when Mike said he wasn’t putting in enough hours and I said ‘That’s what she said’..”). In these situations, as the joke was repeated again and again, we all just got more and more annoyed, didn’t we?

Now, anytime a writer has a fair-sized cast of characters and an even slightly challenging plot, they’re going to have to deal with this issue. You can’t have everybody walking around together experiencing every single thing at the same time. Which means there are going to be points when A and B know something C and D don’t. The trick is coming up with ways to share that information without having the story come to a grinding halt while characters discuss things the reader already knows.

I bring this up not just because of the head-banging nature of that book I referenced above, or because of scarring memories of the bank robbery. Y’see, this is something I’m dealing with right now. In my current project I’m juggling a large cast who are investigating a mystery separately, but keep coming together to compare notes. I know my mystery, but the roadblock is getting past awkward infodump scenes without neglecting this character or that one. I mean, Debbie’s reaction to what they found in the sub-basement is just as valid as Pash’s, isn’t it? She just had the bad luck of having to work that day so she couldn’t go exploring and had to get that information second hand.

You get one chance for your big reveal and that’s it. One. You can’t keep revealing it again and again and expect that reveal to have the same emotional weight. It’s also not going to draw the audience in, because it’s gone from being a surprise to being… well, just another fact.

And if you’re not careful, repetitive facts can get dry and boring really quick.

Next week, I’d like to tell you about the time I sat around for hours watching the most inefficient bank robbery ever.

No, actually, next time I’d like to describe something you’ve probably never seen before.

Until then, go write.

Our three secret weapons are fear, surprise, and ruthless efficiency…

So, a few years back I attended the SDSU Writers’ Conference and got to listen to a gentleman named Esmund Harmsworth. Look him up. Nowadays he’s an agent at ZSH Literary.

He caught my attention one year when I attended a Q&A panel with a bunch of agents. The panel had been running for about half an hour when one fellow stood up and asked a question about his sci-fi novel. One agent immediately told him to throw it away and two others joined in. The trio of battleaxes berated the poor questioner and loudly declared genre as the absolute worst thing to write. Horror, sci-fi, fantasy—it was all garbage. Each of them stressed that they would never, ever look at a genre writer as a potential client.

After a few minutes of them going on and on, Mr. Harmsworth (on the far side of the platform) cleared his throat into his microphone. It tripped them up for a moment, and in the pause he pointed out to the questioner (who had, at this point, shrunk to a height of about two feet and was crying quietly to himself) that if you write something good any agent is going to want to see it. That’s their job, after all, and every agent on the panel was secretly hoping to find the next Stephen King. He sat back in his chair and the battleaxe brigade immediately backpedaled and agreed that quality writing was what mattered over everything else.

Needless to say, when I saw Harmsworth’s name on a seminar list the following year, I made a point of being there. Yeah, it was about mysteries, his chosen field, but I figured there’d be something to glean out of it. And there was, even though Harmsworth admitted halfway through that he’d really only had eight rules but the conference folks said ten looks a lot better on the seminar listings so he made up a couple to round out his list.

That being said—I’m not repeating his entire ten points. If you were in the room that day or have heard him give this little lecture since, don’t try posting an “AHA!!!” because I misnumbered something or left something out. I’m telling you now—things are probably misnumbered and left out.

Also, I can’t understand all the notes I wrote to myself seven years ago…

First Rule – There are no rules. Despite everything I’m about to recount, there is no “A-B-C-Done!” when it comes to writing. I’ve mentioned this here before. You can’t point to any rule of writing without acknowledging there are at least twenty examples of violating that rule. So if people are telling you “you must absolutely, always do this!”—especially when this relates to things like page counts or turning points or redemptive moments– it’s a sure sign they don’t know what they’re talking about.

Now, that being said… Agents sell books (and movies) by comparing them to books that have already sold. Makes sense—that’s how most of us buy books. So saying “it’s not like anything else” makes your manuscript very hard to sell. Your book needs to follow those rules you keep hearing about to some extent.

However… following all of the rules makes you a formula writer. Nothing wrong with that. Lots of people make a decent living writing formula books and formula television shows. Just be clear that no one’s going to sing the praises of such a thing or offer mega-millions for it. Formula manuscripts are the junk food of publishing and Hollywood. They sell steadily, no one pays a lot for them, and most folks forget them half an hour after they’re gone.

Second Rule – Know the difference between mysteries and thrillers. Agents sell your manuscript to publishers and producers, but you need to sell it to an agent. One of the key elements, of course, is to know what you’re selling. It can be a pain in the ass these days with some of the sub-sub-genres out there, but you should have a solid idea which one of them your story fits into. This is when you need be honest with yourself. It doesn’t matter how much you wanted to write a historical drama—if you’ve ended up with a low fantasy story that’s what it is and you need to admit it.

Different genres also tend to have different lengths. You can sell a horror novel that’s 115,000 words, but mystery novels should be topping out around 90,000.

Also, you should know who your audience is. Most mysteries are bought by women (they’re 80% of the sales), most thrillers are bought by men. If you’ve written a kick-ass thriller aimed solidly at a female audience, you’re fighting an uphill battle. Not an impossible one, mind you, but be aware of what you’re up against.

Third Rule – Have a real mystery. One telling thing that came up in this seminar—editors will reject a mystery if they can solve “whodunnit” before the hero does. The story needs to have real clues, red herrings, antagonists, foils—a good mystery isn’t just withheld information. It should involve a lot of thought by the reader—thoughts that a good writer will be guiding down the wrong paths.

As I’ve mentioned once or thrice before, mysteries also depend on strong characters. I need to care about Wakko or his finding clues and working out answers isn’t going to mean anything to me. Plus, if you think about it, most mysteries tend to be mystery series, and no one’s going to want to follow multiple adventures of a character who’s just not interesting or likeable.

Fourth Rule – Location is key to mysteries. Harmsworth summed this up in one neat line. Most mysteries take place somewhere people would go on a dream vacation. People read mysteries set in Las Vegas and Hawaii and New Orleans. These are places most people will read about regardless, and will love to see a clever story set there.

Keep in mind this dream setting can be manipulated a bit and can be represented by some industries or careers. Hollywood is a dream job for a lot of people, so it makes a great setting for mysteries. So is Washington, because we’re all curious about those hallways of power.

Make sure your story is set somewhere inherently interesting—and not just interesting to you.

Fifth Rule – The idea is key to thrillers. I’ve mentioned the term “high concept” here before. It’s when you can sum up the whole idea of a story in just one or two sentences. A great high concept idea doesn’t even need that much, which is how you end up with pitches like “big lizard, big apple,” “Jurassic Shark,” or “it’s like Die Hard in a building.”

A good thriller depends on a central idea that can be summed up in one or two lines. If it can’t, then the whole thing needs work. Because of this, thrillers tend to be very linear and don’t rely on a lot of subplots or a vast array of supporting characters. They’re driven by suspense and the mounting threat that was mentioned in that two-line pitch..

Sixth Rule – Be patient. You can write an amazing novel or clever screenplay and still have the bad luck of finishing it just as interest in said topic has dropped to an all-time low. Some people tried to jump on the supernatural romance boat just as Buffy and Angel were coming to a close, and… well, that ship got dry-docked for a couple of years. Then there was Twilight and suddenly that ship wasn’t just crewing up, it was press-ganging people.

If someone tells you that your book won’t sell, just put it away, go work on something else, and try submitting it again in four or five months. If it’s a good book it will sell eventually. Honest.

If it’s a good book.

And there you have it. Ten (more or less) tips on how to write better mysteries, many of which can be applied to almost any manuscript.

Next week, I’d like to tell you about the time I sat around for hours watching the most inefficient bank robbery ever.

Until then, go write.

Categories