Showing posts with label information. Show all posts
Showing posts with label information. Show all posts

Thursday, August 5, 2021

Shhhhhh! Say Nothing!

Let’s have a little moment of truth between us. At some point or another, for any number of possible reasons, most of us have been in a position where it’s in our best interest not to answer a question.  Or, at the very least, to take as long as possible to answer it.  A few such questions might be....

— “Hey, what’s in the bag?”
— “Do these jeans make me look fat?”
— “Are you actually claiming this as a deduction?”
— “Did you eat the last piece of cheesecake?”
— “So, where were you last night?”

Now, by the same token, there are questions that should take no time at all to answer. Things where, if someone asks us and we know the answer, there are very few situations where it makes any sense for us to delay or be evasive. These are the ones where I have to seriously wonder why someone isn’t answering--and they’d better have a damn good reason for their lack of response. A few examples of that would be things like

— “Do you love me?”
— “How the hell do we get out of here?”
— “What are tonight’s specials?”
— “Which one of these is the antidote?”
— “WTF is that thing and how do we kill it?”

I mean, why would you hesitate on any of these? If we need the antidote and I know which vial it is, that's a no-brainer, right? Grab the yellow vial marked #23 and pour it down his throat.

For example, I loved LOST.  Yeah, sorry, absolutely loved it. Even the questionable third season. Yes, I will fight you if you say foolish things about the ending.

But... I can admit LOST suffered a bit when Benjamin Linus became a regular member of the cast. And a big part of that was because we all knew there was a lot of stuff he wasn’t telling anyone. There were still lots of cool mysteries on the island and Michael Emerson is a wonderful actor... but there were also lots of times where the “mystery” was just Ben sitting there... not talking.

A concept I’ve brought up here a bunch of times is withheld information. I’ve mentioned it a couple times recently, but it occurred to me I haven’t’ really explained it in... wow, ten years? Seriously? Okay, so this is long overdue.

Withheld information is when the characters (or really, the writer) hold back information from the audience for no other reason than to drive the plot forward. Characters just don’t talk about things, even though it’d be very natural for them to. Or they make vague statements when they could just as easily make clear ones. We’ve all seen things like this, yes? Where the only reason there are conflicts or challenges is because characters just aren’t saying what they know.

Withheld information’s the clumsy, unskilled version of mystery and suspense. It’s what I fall back on when my story doesn’t actually have a mystery but I’m trying to create the illusion of one. Because there’s more to a mystery—or suspense, or a twist—than me just not telling my readers stuff.

The thing is, withholding information is really just me and my characters... not doing anything. The plot may keep advancing in a clumsy way, but it’s almost always going to end up falling flat. Because information in a story tends to hit a tipping point. There comes a time when that knowledge has to come out because it just makes absolutely no logical sense for it not to. And when it doesn’t...

Y’see, Timmy, the one thing withheld information definitely creates is frustration with my reader. If Wakko’s been poisoned, Phoebe knows which one of the vials is the antidote, and she’s just not telling anyone—that’s just going to annoy the hell out of my reader. I mean, yeah, it makes the scene more tense, but why wouldn’t Phoebe save her friend? Why wouldn’t she help? If she’s the villain, sure, but other than that...?

And, wow, if we get to the end of the story and that’s when we find out Phoebe knew which one was the antidote and didn’t say anything? I mean, I need to have some ironclad reasons for her silence then. That’s when my readers are going to be looking to punch holes in things, so I need things to be sooooo solid if I’m going to go this way.

Now, all of this doesn’t mean I need to tell my readers everything. But what I don’t tell them depends on what kind of effect I’m trying to create in my story. If I withhold (or give out) information at the wrong points, my story’s going to trip over its own feet. So to speak.

So here are three story elements and how they use information.

A mystery is when the main character and the audience are aware a piece of information has been hidden from them, and my story usually involves a search for that unknown fact. At it’s simplest, a mystery is a question someone in my story is asking and trying to find the answer to.

Suspense is when there’s an important piece of information the audience knows and the characters don’t. The key here is that the characters don’t know that they need to know this vital fact. ussually as soon as possible. Like that Phoebe (who Wakko’s taking back to his hotel room) is the murderer. Or there’s a bomb under the table. These are common suspense situations we've all been in, right?

A twist is when a piece of information is revealed that my characters and my readers didn’t know was being kept from them. They didn’t even suspect those facts were out there, waiting to affect the story. A twist comes from out of nowhere and changes a lot of perceptions for the reader and probably the characters. We’ve all been assuming <<SPOILERS>> Luke Skywalker’s father is dead, so when we learn that Vader is his father, it’s a twist that alters our view of several things we’ve been told up until now.

Yeah, sorry. Blew the big Skywalker family secret there.

If I’m trying to use one of these devices, I want to make sure I’m using them correctly. I don’t want to just withhold information. My characters should be just as smart and clever as my audience, and if they aren’t talking... well, I should be sure there’s a solid reason why.

Next time, I’m going to try to answer another question that got tossed my way.

Until then, go write.

Thursday, November 5, 2020

TMI

So, hey... anything interesting going on in the world?

I kinda touched on this a month or so back, but since we’re all suffering from a bit of information overload right now, I thought it’d be a good topic to talk about. I mean, we’re all familiar with this feeling, right? Dealing with that person who just feels the need to tell us a little too much about things. Seriously, I get that Wakko’s excited about having a kid but do we need that many details about how the child was conceived? No, I completely understand why you thought she couldn’t get pregnant while she had her no y’know what, let’s just stop there.

Actually, let me stay here for another paragraph or three so I can tell you a porn story.

Years ago I was mildly obsessed with a little Canadian show called The X-Files. Maybe you’ve heard of it. It was kind of famous for bold storytelling choices. Multi-part stories and arcs. Realistic lighting. And some bold tricks for getting around the standards and practices rules for what you could show on television. As someone working on a television show at the time, I was amazed by some of the things they did. Especially one time when a recurring character killed a man by pistol-whipping him until he dropped to his knees, pressing the gun against the man’s head, and blowing his brain out.

Of course, we didn’t actually see this. Seeing something like that on broadcast television in the early 90s was strictly verboten, as Kurt Wagner would say. So the X-Files had Mr. X drag the nameless thug around a corner and we saw all this action the same way Mulder did, playing out on the walls as shadows and half-muffled sounds. You can probably picture it in your mind, even if you haven’t seen it. They showed less and did so much more.

The next day at work I was lamenting to my boss, Brad, that we never did anything this cool. Our little martial arts show was kind of... blunt. In the sense that sledgehammers are blunt. Brad just shrugged and said “It’s because all we do here is porn. Doesn’t matter what kind of show it is. Porn is when you show everything. That’s all anyone here knows how to do.”

That was many, many years ago, but I’ve always remembered it. I mean, porn really is the ultimate TMI situation, isn’t it? It’s pretty clear those two (or three) people went off to the poolhouse to have sex, but in porn we see... well, all of it. Every minute. From multiple angles.

Sometimes... our writing leans into porn. I’m not talking about sex, but like Brad said, we start showing everything.  We explain things that don’t need to be explained. Sometimes with far too much detail. A distracting amount of detail. Can you imagine if Ant-Man & The Wasp had a ten minute scene explaining how Pym particles work? Or how Hope controls her wings? Not only would it slow thing to a crawl and break the flow, but I bet anyone with even a thin grasp of science and physics would be able to punch a dozen holes in it.

But there’s another aspect to TMI as well. Experiencing a story is a personal thing. We’re reading it, but we’re feeling it in our gut and filling in a lot of details ourselves. As writers, we try to guide (and maybe even manipulate) how readers imagine things, but in the end a lot of it’s going to be very individual. If you’ve ever read a Jack Reacher book, you’re probably not picturing Tom Cruise, but you’re also not picturing the same person I am. The way I picture Danielle in the Ex-Heroes books probably isn’t the same way you picture her, and I probably don’t envision Veek from the Threshold books the same way you do.

So when I start describing too much, things stop meshing in my reader’s mind. I’m breaking the flow again. I’m repeating “six foot blonde” again and again while you’ve already decided Phoebe should be a brunette.

And there’s another way too much information hinders things. In the bigger, overall world of the story, we like having space to wonder and imagine. Especially in speculative fiction. We enjoy filling in some of the blanks ourselves.

For example, when I was a little kid growing up on Star Wars, I assumed the Rebellion was poor (like me) and couldn’t afford to buy cool new ships to fight the Empire. So most of what they had—the X-wings and Y-wings—was essentially kitbashed stuff they cobbled together. They had the basic instructions and diagrams, and they just made the ships out of whatever parts they had (which is why they all had little differences). Heck, I was so convinced of this, I assumed when the Rebellion started using A-wings in Return of the Jedi they were retrofitted snowspeeder hulls, now with airtight canopies and stronger engines. 

Was I right? It didn’t matter—the story had space for me to fill things in on my own. Which is a big part of what I loved about it. Sometimes, leaving things unanswered and unexplained is good. It leaves room for my reader (or my audience) to fill things in on their own and create their own mythology.

Not to mention, it gets harder to tell stories. A good story is about things we don’t know. It’s about the characters (and us) learning and experiencing new things. But the more I know about a character or event, the harder it is to tell a really strong story about them. All the information’s already out there. People give Disney a lot of crap for wiping the Star Wars slate clean and starting over, but the simple truth is it opened up tons of storytelling opportunities. Most of the great Star Wars stories of the past eight years couldn’t’ve been told before, because all those spaces had been filled up and sanded smooth. There were no gaps of knowledge left to fill in.

This can be tough, the idea of not explaining things. There’s a lot of empathy needed. I really need to understand what information my readers will want to know, what they’ll enjoy figuring out for themselves, and when they’ll be fine with nothing more than a handwave explanation of me saying “the flux capacitor is what makes time travel possible.”

It’s also tough because—like with research—sometimes we’ve worked out a really cool explanation or some ironclad reasoning, and we want to share it. We want people to see how clever it is and how well we thought it out. We want them to know we’ve thought of everything.

And let’s be very honest with each other... sometimes we want to fill pages. Nothing wrong with that. Filling pages is kind of the job. I mean, pretty much the first 100 pages of The Fold is scientists and engineers talking about how their little project works. But I’ve also never explained how the Cerberus armor works in the Ex-Heroes books or how Barry turns into Zzzap. And nobody’s complained yet.

Y’see, Timmy, I shouldn’t be scared about not explaining things. Look at some of the explanations and descriptions in your book. It might be new information, but is it necessary information? Does the story need it or does it maybe run a little smoother without it?

Next time... I’d like to talk about how we start things.

Yeah, I know. Great post to do halfway through NaNoWriMo.

Until then, wear your mask, wash your hands, and go write.

Thursday, October 15, 2020

YOU LIAR!

 No, no, I’m not talking about you.

 I’m talking about him.

You know who you are.

There’s an issue that came up in one of my weekend B-movies recently, and it also came up in a book I was reading last month. Not the first time I’ve seen it in either format. And I thought it was worth talking about for a minute or three.

And that issue is cheating.

I’ve talked about twists many times here on the ranty blog. I friggin’ love a good twist.  Seriously. I will forgive a story a lot if it can knock me over with a completely unexpected reveal that seems obvious in retrospect. That’s the kind of thing that makes me want to grab a book and read the whole thing again. There are movies I love to rewatch just to see how beautifully the filmmakers set up a fantastic twist.

Now, in the past, I’ve addressed a problem some writers have when they try to set up a twist. And that’s when the revealed information—the twist—is something the reader couldn’t possibly have known or even guessed. If I tell you Wakko is actually the clone, it makes us realize how we-misinterpreted some parts of the story and a couple things line up now that didn’t before. If I tell you Phoebe is actually the clone, it makes us ask who the hell Phoebe is. Is she even from this story? Also, wait, this story is about clones...?

In the past I’ve tried to soften this criticism by saying the writer didn’t understand how to set up a twist. And while that’s still true in the big scheme of things, I think it might be  a little more helpful to just be direct. When this happens, the author is cheating in how they tell the story. They’re lying to the readers.

And sometimes, you just have to call out the liars.

Yeah, this sounds a little harsh and a few folks may already be raising their defenses, so let’s take a moment and be clear what we’re talking about. This is a very specific thing I’m referring to. Cheating is a deliberate thing, a choice, as opposed to a simple mistake.

All that said, let’s talk about what makes a good twist. I’ve talked about these all at different times, but I think a good twist always has four distinct elements.

1) My readers and my characters don’t expect a twist is coming. If I tell you there’s a big secret about my cat you’ll never guess, you’ve been flat-out told there’s something about my cat you wouldn’t expect. Likewise, if the shadowy figure is constantly referencing things only certain people could know, they’re probably connected to one or more of those people. It’s hard for any twist to land well when people are on the lookout for it.

2) The information a twist reveals has to be something my readers and characters didn’t already know. Telling you I have cats is not a big reveal, especially if you follow me on Instagram. This information has no weight. Telling you one of my cats is a cyborg is a reveal—that’s something you didn’t know.

3) The information revealed in a twist has to change how my readers and characters look at past events in the story but (very important) this information can’t contradict the information they’ve been given up until now. I can’t say my cat’s actually a plush toy dog after calling her a cat for a hundred pages and talking about the vet bills when she got her cyborg parts. Worth noting—this is when a lot of twists go wrong.

4) Finally, a twist needs a certain amount of time to build up strength. It’s really tough to have a good twist in the first five pages of a novel. As I mentioned above, a twist needs to alter our view of past events, which means... there have to be past events. If my cat’s showing off her laser eyes and adamantium claws on page eight, this isn’t a twist—I’m just introducing a character.

Granted, these are my own requirements, not something (to the best of my knowledge) taught in any courses or books. For this little rant of mine, it’s 2) and 3) we’re most concerned, because that’s where the cheating often comes into play. Because cheating (and lying) usually involve the manipulation of information to suit your own needs.

Now, right up front, it’s really common for me, as a writer, to lead my audience into believing something. To carefully choose words and phrases to make them think X when the truth is Y. This is a standard aspect of storytelling—what I want the reader to know and when I want them to know it.

But it’s important that I don’t cheat. I may leave a few facts out. I may deliberately guide them down a different path. But I can’t lie to them. The moment I lie—even if I’m doing it to make the story “better”—I’ve broken the contract. They’ve got no reason to trust me, and it’s not unfair for them to start doubting and questioning everything in the story.

So what do I mean when I’m saying cheating or lying? Let’s break it down by those two points from above...

As far as 2) goes, I need to be revealing information the audience doesn’t know, but it has to be information they could know. It can’t break the characters or the world I’ve established. It needs to fit within that context.

For example, if my twist is that Bron from Game of Thrones has psychic powers because he’s actually a mutant from an alternate future timeline... well, it’s definitely information we didn’t know. But we never could’ve known it. With everything we’ve been told it’s just an impossibility in this story. Likewise, if I’m writing a murder mystery and the big twist is that the murderer is Phoebe... we should all know who Phoebe is. Revealing a name we’ve never heard before at a critical moment doesn’t really solve anything.

A good way to think of it is whatever information I’m revealing in my twist is something my readers should be able to guess—even if it might mean a few guesses. If I have twenty characters/potential suspects in my murder mystery, the reader shouldn't need thirty-seven guesses to name the murderer. If I’m three hundred pages into my grimdark medieval fantasy story, I can’t abruptly say the dark lord’s secret weapon that’s wiped out armies is a battlemech with a meson death ray. Why would anyone ever guess that?

When we’re talking about 3), the big cheat is usually just a straight contradiction. The facts I give on page 150 or 200 just don’t line up at all with the facts I’ve given you before. I’ve told you two or three times that Wakko’s a computer programmer but then it turns out really he’s a genetic engineer.  Numerous characters have said there’s nothing within a hundred miles of our village, but then they escape to the town on the other side of the valley. And if you find out on page 175 of my political thriller that the secret informant is actually an angry ghost... well, I’d understand if you tossed it aside at that point.

One of the worst examples of cheating is when we’ve been seeing over a character’s shoulder or “hearing” their thoughts for a hundred or so pages and they just, y’know, never happened to think about the fact they’re the serial killer the whole city’s searching for. Or that Wakko constantly calls himself as a computer programmer (even in private) until we find out he’s the genetic engineer who activated Dot’s Zoanoid genes (double-geekery reference). This is the kind of things that make readers grind their teeth, and it really stands out on a re-read.

In the end, these lies are just about no being honest with my readers. I’m lying to them about what Wakko does. I’m lying about what’s going on in his head. I’m cheating to create a certain effect rather than actually creating the effect.

Y'see, Timmy, I think the reason some writers fall back on these blatant cheats and lies is... it’s easier. Doing the work is tough. Lying is simple. And if I just don’t feel like doing the work, it’s really tempting to just say Wakko’s a computer programmer and move on.

Good writing is tough. It’s work. Sorry to be the bearer of bad news, but it is. There are a lot of nuances to this art and they’re going to take actual effort if I want to come close to mastering them. To pull off a really good twist is probably going to mean going over my manuscript two or three times, making sure everything lines up and fits together just right.

But when you do it--when you do the work and don’t lie, don’t cheat—that’s when you make something that sticks with people. Something fantastic they’ll remember and talk to people about and recommend constantly. Because a great twist makes a good book twice as good. The readers get to enjoy the whole story, and then they get to enjoy it again, seeing and appreciating how everything fits seamlessly together.

True story. Like a lot of my books, Ex-Patriots has a twist in it. It’s such a big twist that, when one reader hit it, she couldn’t believe I could’ve slipped this past her for the entire book without her noticing. In fact she immediately re-read the whole book, convinced I had to have cheated. And when she realized I hadn’t, she (somehow) hunted down my phone number and called me to rave about it and congratulate me.

And that, friends, is how I met Seanan McGuire.

Do the work. Don’t cheat. Don’t lie.

Good advice for writing and life.

Next time, I wanted to talk to you a bit about characters.

Until then, go write.

Thursday, October 1, 2020

Allow Me to Explain...

 There’s a storytelling idea, sort of a method, I suppose, that I’d been batting around for a while as a possible topic. Something I see crop up enough that it was worth mentioning in that “something else to keep in mind...” way. I decided to add it to my list of topics here and then, in a weird synchronicity, said problem showed up in a TV miniseries I finally got around to watching and a book I was reading (some formats may be changed to protect... you know).

The miniseries I mentioned involved an aggressive computer virus. And it explained how the virus worked. In detail. It used a few specifics and a few generalities, but it spent three whole scenes explaining this virus, the logic behind how it worked and how it selected targets.

The problem was... even as I was watching this, I could see a bunch of holes in the explanation. Holes that were only pulled wider as the story went on. And my computer skills more or less peaked in the very early 00’s. But I still knew enough to know the virus wouldn’t work the way it was described. Couldn’t. If it chose targets this way, why didn’t it go after that or that? If it propagated like that, how had it reached here and here?

For a brief time I was wondering if this was some sort of foreshadowing that there was more to the virus than was being let on. Maybe some sort of AI or a living virus that had been transcribed but then... mutated or something? But no, in the end it was just a computer virus that didn’t make any sense.

Which was doubly annoying because the virus didn’t really need to be explained in this story. The plot was much more about the repercussions of this thing being loose on the web and how it was affecting lives, society, and so on. The explanation slowed things down.

And, yeah, sure—part of this is on me. Any genre story is going to involve a degree of suspension of disbelief. Nobody wants to be the guy picking apart the energy requirements of a lightsaber or arguing how the Hulk can’t be that strong because his muscle/bone density would mean he’d sink into the earth. And as for Mjolnir, look...

Okay, yeah... there are some people out there who love being that guy.

(looking at you, Neil...)

But here’s the thing. I couldn’t’ve picked it apart if the writer hadn’t put so much down in front of me. I wouldn’t’ve had anything to pick apart. I can’t complain about your wardrobe if you never show me your wardrobe. But this writer decided they needed a whole scene (three scenes, really) explaining the computer virus in detail. And the details didn’t match up.

So what does this mean for me if my story needs explanation? I mean, speculative fiction is filled with different forms of technobabble. It’s got FTL drives and magic systems and AI computer viruses and alien life cycles and bringing dinosaurs back with cloning and mutant superheroes and... I mean, I’ve got to explain it all somehow, right?

Maybe? Consider Jurassic Park. How much does Crichton (or Spielberg and Koepp) actually tell us about the process of recreating dinosaurs? No, seriously—what do they tell us? If you look back, it’s actually a pretty bare-bones explanation of what’s a fairly complicated process (especially twenty-five years ago!). In fact, it encourages us to fill in a lot of the blanks ourselves and make it seem more complete.

So here’s a few things to keep in mind as I’m writing out that long explanation...

First, be clear if the story really needs this explanation. Is this what the story’s actually about, or is this a minor element I can handwave away or just skip over? Back to the Future gets away with a ridiculously simple explanation of time travel because it’s not really about the time travel. It’s about actions and consequences, and becoming a better person. Time travel’s just the mechanism that lets it happen. It’s just short of being a MacGuffin. We don’t need that explanation the same way we don’t need to read about someone hitting every step on the staircase, how many keystrokes it took to log into their cloud account, or a list of every item of clothing they put on when they got dressed (in order). The reader will fill it in.

Second, if I decide I really need to explain this at length, it’s got to be solid. I’ve waived the right to say “just trust me, it works” and now I need to make this as rigorous and believable as possible. I need to do my research, double-check my logic, triple-check my numbers, and let it marinate overnight in plain-old common sense. Trust me when I say if I get a fact wrong or use garbage science or make a math mistake... people will let me know. I don't even have to ask them. Not only that, but...

Third, I need to keep in mind the more something gets explained, the easier it is to punch holes in that explanation. Like in the example I first mentioned. As the characters went into more and more detail about the computer virus, the flaws in that explanation became more and more apparent. How often have we seen the person digging themselves deeper and deeper because they won’t stop talking? It’s soooooo tempting when we’ve done all that sweet, cool research, but I need to figure out how much explanation my story really needs and stop there. I’ve mentioned screenwriter Bruce Joel Rubin here onceor thrice, and his idea that we experience stories in our gut, but we analyze them in our head. I never, ever want my explanation to drive people into their heads.

Fourth, closely related to the last one, is that this sort of explanation is almost always going to be exposition. Yes, even if I try to work it into a conversation or presentation or something like that. As we’ve talked about here a bunch of times, exposition gets boring really fast because so much of it is either things we already know or things we don’t need to know. For our purposes here, there’s a chance the reader doesn’t even want to know. So if I decide I need this explanation in my story, I need to make sure it’s going to be clever and engaging for the reader.

And that’s me explaining how to explain things.

Next time, I’d like to talk about if you should be reading next week’s post.

Until then, go write.

Thursday, June 25, 2020

A Quick Follow-Up Question

I’ve been talking about genre writing for a few weeks now, I know, but I actually had one last thing that’s been tickling my brain.

I’m sure I’m not the only one binging shows right now. Things I’ve wanted to see again or watch for the first time. My partner and I are kinda doing a Voyager rewatch, but we’re also stretching out this last season of She-Ra. And I just finished Parasyte, an anime I’ve meant to watch since I first read some of the manga... jeeez, twenty years ago? I tried rewatching The Prisoner but gave up on it and settled for some old G1 Transformers cartoons.

There’s also another show we’ve been watching, and I’ll politely not name this one. It’s another older show (a few years now), and it’s got a strong mystery element. Well, it tries to have one, anyway.

(to be polite, some of the following plot points may be altered from of the actual show we’re watching... or are they?)

The main subplot is that our hero’s trying to learn why his father left decades ago, and has tracked down the small farming town where Dad ended up living. And dying—with a lot of things left unanswered. Things like why did Dad abandon his family? Why come to this small town? What’s with all the old books in the study? Or the ring of corn around the house? And the strange old guy who takes care of the corn who has the same name as our hero? And is this mysterious woman, Lacey, his half-sister or... something else?

Pretty much ever other week, said hero finds out some tantalizing new clue about his long-lost father and then does... nothing.

Again and again, the show has moments where we learn that Bud, the town mechanic, played chess with Dad every week... and they talked a lot. Helen, the retired nurse who hangs out in the park? It turns out she was there for Lacey’s birth... and it wasn’t exactly a normal birth. And Sheriff Mawkin? well, she was only a deputy when Dad moved to this town, but he took her aside then and told her that some day his son might come looking for him.

And our hero would be amazed and thrilled and confused about what he’d just learned... until the end of the scene. At which point, he’d completely forget about these little tidbits and act like nothing had happened. Until they came up again two or three episodes later.

We end up getting annoyed with things like this because in theory our characters are supposed to mirror our readers (or audiences, if you will). If the point is to make my readers think “Wait, what the hell does that mean...?” then this is something my characters should be thinking—and maybe even voicing—too. And they should be acting on that reaction. I can’t have a character say “this changes everything!” and then go on acting as if nothing has changed. They can’t find out Bud has the answer to the question that’s haunted them for years and then not get around to asking Bud about it. It’s frustrating because we know we wouldn’t leave it like this. We’d want more. We’d demand more!

One of the easiest things we can do at any point in our writing is to just ask ourselves “What would I be doing right now?” How would we react? What would we say? What would we be important to us right now in this situation? And if we’d demand more in this situation, well, maybe I should really think about why my characters aren’t.

I think this is also one of the reasons using mysterious characters flops so often. Because Mister X offers some vague statement or response and the main characters just... accept it. They don’t have follow-ups. They don’t demand more. They don’t take what they’ve learned and run with it. They just shrug their shoulders and say “Huh.”

Now, to be clear, I’m not saying we need to answer every question the moment it’s asked. They can get teased out and end up being false answers, misunderstandings, or red herrings. That’s part of a good mystery. A necessary part, some might argue.  So it’s okay not to answer questions right away.

But y’see, Timmy, it’s not okay to never ask those the questions. If my characters don’t care enough to ask, they can’t really care about the answers. Which means my readers probably shouldn’t care.

Which means all this mystery stuff is just a waste of time because nobody cares about it.

Next time...

Okay, I’m juggling a couple things right now. I know I haven’t updated the FAQ in a while. I’m also trying to set up theWriters Coffeehouse as an online thing. And, hahahahaaa yeah I’m trying to finish a book right now.

I guess what I’m asking is, what would you like to see in the next few weeks? Any particular topics you’d like me to blather on about? Something you want to hear a fresh take on, or a problem that’s been gnawing at you? Let me know down below.

And if nobody says anything... I may take a week off and try to get a bit caught up on things.

But for now... go write.

Monday, March 16, 2020

Again and Again and Again and Again and

So, hey... things are a little crazy and intense in this world of ours right now. Hopefully you’re somewhere safe and hunkering down a bit. Also hopefully you’re not someone going “Ha ha ha look at me” as you wander around potentially endangering other people.

Be a hero. Don’t willfully endanger anyone else right now. Okay?

Anyway... bonus post. Figured everybody could use a little extra stuff to read while they're stuck at home.

I'd like to share a random writing-type thought that’s bounced back and forth through my head a few times recently. I think it’s something a lot of you may automatically get, but this might help solidify it a bit in your own heads. And for some of you, this may be an all new concept.

I’ve mentioned the idea of repetition in writing here a few times, coming at it from a few different angles. It’s one of those elements that can be very powerful if used the right way... and completely brutal if I use it the wrong way. Or overuse it. It’s like one of those vitamins or minerals that we absolutely need to live, but just a little too much and now it’s a deadly poison.

Anyway, it recently struck me why repetition can turn on us like that and—oddly enough—it ties back to another idea I’ve mentioned here once or thrice. And that’s a concept Damon Knight talked about in one of his short story books. The idea of information vs. noise.

To sum up quickly, it goes like this. When we come across a fact we don’t know, it’s information. When we come across a fact we already know, it’s noise. We pay attention to information, but we tune out noise because... well, it’s noise. It’s just a distraction, keeping us away from the stuff we’re actually here for.

Now, Knight was talking about this mostly in the sense of exposition, and this makes perfect sense. We don’t want to read two pages about why Nazis were bad because, well, we all know that already (okay, most of us know that...). But we’re up for two pages about how true artificial intelligence came into existence, because this is something we don’t know and (hopefully) find interesting and relevant within the context of the story.

Getting hit with the same facts we already know is... well, boring. Sometimes flat-out aggravating. It feels like the author is padding and wasting time rather than giving us what we want.

But here’s the thing. This is true of pretty much all repetition. As I’m putting words down on the page, repeating anything the reader knows (or can figure out) is going to quickly become noise.

Think of names in dialogue. We roll our eyes when characters constantly use names while talking to each other. Or if the author constantly uses dialogue descriptors with names rather than pronouns (or just assuming we can follow who’s talking). After hearing Wakko said... a dozen times on one page, we start grinding our teeth. We can’t help it. It’s noise to our ears.

The same thing holds for descriptions. Yes, I know Phoebe is over six feet tall. You’ve mentioned it seven times in the past ten pages. Or that the blood is bright red. Or that Phoebe is six feet tall. Or that Yakko is a cyborg. Or that one of my over-six-foot characters is Phoebe. See what I mean? I’m clearly doing it as a humorous way to make a point, but it’s kinda getting on your nerves, isn’t it?

And I’ve talked before about doing this with reveals. The first time I reveal something to my readers is an amazing, jaw-dropping thing. Because it’s facts they don’t know. It’s information. But the second time I show it off it’s... well, it’s not as interesting. And the third time, if there’s no point to this, it’s kinda boring. By the fourth time okay seriously can we just get on with this? What? A fifth time? Seriously?

Repetition can turn anything I have to say into noise fast. So I want to be very careful if I’m going to repeat any information for a third or fourth time. And like I just joked, if I hit a fifth time...

Wow, I should probably rethink some things.

Next time we’re going to jump back to the A2Q and talk about theme. Yeah, I know. You just had this gut, high school reaction to that word. I’m going to try to help you get past that.

Until then, go write.

Thursday, October 29, 2015

Gentlemen... BEHOLD!

            Okay, it’s just going to be a quick post this week. I found out kind of last minute that I’m hosting the Writer’s Coffeehouse in San Diego on Sunday (noon at Mysterious Galaxy—stop by), so I’ve got to scribble up some notes for that.  Also, I’ve got a big Halloween party the night before, so please don’t be surprised if I show up dressed like Rick from Rick and Morty...
            Speaking of which, I think this is the first time I haven’t done a horror post on the week of Halloween.
            But let me get back to this week’s point, which is...
            This!
            One of the greatest parts of storytelling, in my opinion, is the reveal.  It’s when we find out who the murderer is, or that Phoebe isn’t really dead, or maybe how Wakko ended up with the Elder Blade, or maybe that it isn’t really the Elder Blade, or maybe that Phoebe is actually Wakko’s long-lost sister Dot and she’s had the Elder Blade all along.  Or maybe it’s something a little more mundane, but still a bit of a shock.  It might just be finding out someone died last week, or that someone actually came over to break up with you and not to make wild monkey-love, or even getting those test results back... not with the result we wanted.  On one level or another, pretty much every story is going to have a reveal of some kind.
            This is how I get information across to the reader—I reveal it.  My characters answer the phone, open a book, get a text message, pull back a curtain, step around a corner, tear open an envelope, or turn slowly to see who’s sitting in that chair by the fireplace.  Lots of reveals are minor, some are subtle, and a few carry a ton of dramatic weight because they’ve just changed how my readers are viewing the story.
            Now, there’s an important thing to remember here, and it ties back to something I’ve mentioned once or thrice in the past.  Facts we don’t know are information. Facts we do know (or could’ve very easily deduced) are noise.  Another way to think of noise is that it’s literary static--clutter on the page. 
            Since a reveal deals with information, it can’t be about facts we already know or could’ve figured out on our own.  Even if my characters don’t know it, it’s still noise to the reader.  So if I structure a paragraph or scene or chapter around a reveal that, well, isn’t really a reveal... it’s going to fall flat.
            Let’s look at an example (one I’m making up off the top of my head).
            Our first shot will be Yakko being sworn in as President of the United States.  Maybe ten or twenty pages later we’ll see him chatting at length with the White House press secretary. After that, he’ll be stepping off of Air Force One, waving to the crowds.      
            And then, finally, we’ll have him on the phone.  A black phone, one that’s still connected to a hard line.  And as Yakko tells someone on the other end “Make it happen,” our point of view pulls back to reveal he’s calling from inside... THE OVAL OFFICE!!!
            Big shocker, right?
           Okay, it’s not.  Really, it’s not a surprise at all.  All of us know where the President spends his workdays.  And, well, since I’d made it really clear Yakko was the President, none of us are surprised to see him in the Oval Office.  So my big reveal at the end of that example is supposed to carry dramatic weight, but instead it stumbles because it isn’t carrying anything except noise.
            Y’see, Timmy, a reveal should give my readers information if expect it to have some dramatic impact.  It isn’t dramatic if we already know it.  Or if we easily could’ve figured it out.  And if my writing’s all done around the idea that it is a  dramatic reveal... that’s how my manuscript ends up in the pile on the left.
            So go forth and reveal yourself in--In your writing!!!  Jeez, it’s Halloween, yeah, but there’s little kids out there...
            Next time... well, I’ll do something.
            Until then, go write.

Thursday, May 8, 2014

Information vs. Noise

            Many thanks for your patience.  Sorry I missed last week, but—as suspected—travel stuff kind of overwhelmed me.  Texas Frightmare was pretty amazing.  If you’re a fan of horror, or any subgenre of horror, I highly recommend it.
            Enough of that, though.  Let’s make some noise.
            Actually, let’s not.
            Writer and writing coach Damon Knight made an interesting observation about how we receive facts as we read.  When we come across a fact that we don’t know, it’s information (I have four different statues of the Egyptian god Anubis on my desk).  Information is new, and we tend to pay attention to it. 
            A fact that we already know, on the other hand, is noise (the sky is blue, candy is sweet, the KKK is bad).  Noise is annoying.  It’s repetitive and distracting.  We try to block it out and focus on other things, because we know listening to noise is a waste of our time.
            Let me give you an example...
            I saw the pilot for a television show a few months back.  Well, most of the pilot.  I shut it off halfway through.  Normally I wouldn’t call out shows or movies for mistakes, but since this one’s already been cancelled, I don’t think it matters.  The entire first act of Once Upon A Time In Wonderland goes back and forth between young Alice adventuring in Wonderland with her Djinn boyfriend and adult Alice in an insane asylum, where she’d been for years because she insisted her childhood stories were all real. 
            As we kept going back and forth, the style of storytelling (and, granted, the whole premise of the show) made it very clear that Alice actually experienced these things.  So the ongoing inquisition at the asylum became doubly pointless.  I knew they thought she made it up and I also knew it really happened. 
            And information we know is just noise. 
            What’s interesting, though, is that as this back and forth continued, a shift happened.  The Wonderland sequences became noise, too.  Even though they were giving new information, it was still couched in the frame of “this really happened.”  And I already knew it really happened, because that was established early on.  So I began to glaze over the entire first act of the show and wondered when the actual story—something new—was going to begin...
            I just finished a book where everyone in a small village is being affected by mood-altering technology that are making them dull and listless.  The most vibrant people are tired and apathetic, and even pale from lack of sunlight.  As our young heroine returns home, she keeps observing how everyone is tired and apathetic and pale.  The girl at the local Quik-E-Mart is tired and apathetic and pale.  The clerk at the grocery store is  tired and apathetic and pale.  The deputy who she confronts about it is tired and apathetic and pale.  And she comments to her as-yet-unaffected friend about how tired and apathetic and pale everyone seems to be, and they wonder what’s going on.
            And I’m sure you were skimming a bit at the end there, because there’s only so many times you can see “tired and apathetic and pale” before you start glossing over it. It’s what I ended up doing.  I have to admit, I skimmed large swaths of the book because it kept showing me the same things over and over again.
            Y'see, Timmy, I need to be aware of noise not only in my story, but in the way I tell my story.  It’s unavoidable that I’ll need to repeat something every now and then.  But this should be the rare exception, not the standard pattern of my storytelling. 
            My story should always be moving forward.  My characters should be growing and learning and developing.  This is all progressive motion, and it’s what every story needs to survive. 
            Because if my story doesn’t have forward movement, it’s just me sitting there making noise.
            Next time, I’d like to speak in code for a bit.
            Until then, go write.

Thursday, April 26, 2012

The Nine Alcatraz Events

            Pop culture reference.  Sort of.  More of a portmanteau, really.
            Anyway, please bear with me.  This one’s a bit long, but I think it’s worth it.  And there are extra pictures.
            Some of you may remember a little show called LOST that aired a few years ago (yeah, we’re just a couple weeks away from years--plural).  I’ve mentioned it here a couple times because it completely redefined the one hour drama for television, and it also offered many brilliant lessons about executing mysteries and twists in a story.  It inspired thousands of writers, in film and in prose.
            It’s only natural that networks would want to duplicate the success of LOST.  Television is a business—it’s their job to be as successful as possible.  If X works, it’s only natural to try more X.
            Of course, it’s not quite that easy when we’re talking about storytelling.  Sometimes a story works, sometimes it doesn’t. The smallest tweak in structure, tone, or character can flip something from phenomenal to average or even trite.
            After watching another one of these would-be successors to the throne tread water for a few weeks, I though it might be time to address what a lot of these storytellers are doing wrong.  Not that any of them will ever see this or listen to me if they did.  But there’s something here that all of us should keep in mind, no matter which format our tale of eerie puzzles and mysterious strangers happen to be written in.
            So here are three shows that were all an attempt to cash in on the mystery/genre success of LOST. 
            The Nine followed the lives of the survivors of an extended bank hostage crisis.  When the police stormed the building after fifty-two hours, these eight hostages and one captor were the only ones still alive.  And despite having a huge impact on their lives, plus the lives of their family and friends, all of them are remarkably close-mouthed about what happened during those almost-three days.  Husbands, wives, and others are left wondering why these nine people are so changed, and why the only people they seem to be able to relate to anymore are each other.
            The Event was about three parallel plotlines.  One was the story of a resourceful young man whose fiancé is kidnapped while they’re on a cruise and his ongoing attempts to find her.  One covered a newly-elected President who’s learned the US government has been holding extraterrestrials in an Alaskan prison for the past fifty years and has decided to open negotiations and release them.  The last thread is about the aliens themselves and the long-term secret plan they’ve been trying to carry out, even while imprisoned.
            Last but not least, we’ve got Alcatraz, which just finished airing a few weeks ago.  And I feel pretty confident when I say it finished airing, but I still might be proved wrong there.  It focused on San Francisco police detective Rebecca Madsen who gets pulled onto a special government task force.  It seems all the stories about America’s greatest prison being shut down fifty years ago aren’t exactly true.  All the prisoners weren’t transferred, they vanished.  And now they’re reappearing, one by one... and some of them seem to have missions.
            Seems like a decent array of shows, yes?  Now, here’s the really interesting thing.  All three of these shows failed for exactly the same reason.  They all had the same flaw.  Perhaps even more interesting is that the one that was the most blatant example of it, The Nine, was the first to air.  The others followed and still repeated the same mistake.  And to be honest, I see this mistake crop up in prose manuscripts a lot of the time, too.
            Allow me to explain
            The core idea of The Nine—the unconnected people who share the same mysterious experience—is interesting, but here’s the catch.  The narrative wasn’t about all their friends and family trying to figure out what happened to these folks during their two-plus-day captivity.  It was about the nine survivors.  They were the characters the show focused on as they approached the world with new attitudes and unknown motivations... yet still refused to talk about all those hours inside the bank.
            The Event also had a very interesting idea, but you probably spotted the same issue just in the synopsis.  Much of the ongoing plot circles around this secret alien mission, and the aliens are a third of the show’s cast.  Of course, if the aliens discuss their plans the mystery goes away, so they always speak in vague generalities rather than, y’know, talking about anything.  
            And then there’s Alcatraz.  Our big mystery is these time-shifting prisoners.  How and why are they doing it?  Since the show’s split between present and past, though, we see what our heroine doesn’t.  It’s evident early on in the run that the Warden’s behind it all, or contributing heavily at the least.  Not only that, it’s clear Rebecca’s new boss, Hauser, knows a lot more about it than he’s letting on.  Part of the show’s “mystery” is that he isn’t telling her things she needs to know in order to do her job.
            Everyone see the common link here?
            Consider this—is it a mystery what day my brother’s birthday falls on?  Sure, almost no one reading this knows the answer.  Some of you might even be surprised to hear that I have a brother.  But does that make this a mystery? 
            The problem with having a story that hinges on something like this is that there really isn’t a mystery.  A real mystery depends on the characters and the audience looking for an answer.  But when a story’s falling back on withheld information, the characters and the audience know right where the answer is.  They’re just being told to sit and wait for it to be revealed.  And since the characters are supposed to mirror the audience, this means everyone’s just getting frustrated.
            This is the real problem all these shows had.  They each had a couple other problems past that—every first season show does—but this was the crucial mistake they couldn’t get past.  All three of them are just cases of characters who are deliberately withholding information from either the character or the audience.
            Yeah, that’s right.  The audience (or the readers, depending on your situation).  My lovely lady made the observation once that any time the narrative of The Event shifted to the aliens, they always spoke like they thought the room they were in was bugged.  In a way, she was right.  There was someone listening to those conversations that wasn’t supposed to be—us.  The aliens can’t talk freely because we’d hear the answers to all the “mysteries” on the show, so instead their leaders had conversations like this...

            "We're going to have to do it."
            "You mean...?"
            "Yes.  Just as we discussed."
            "But what about--"
            "I've considered it.  I think the potential risk to our people is acceptable."
            "All the risks?"
            "Even back at the beginning, we knew something like this might happen.  We can't back out now because we don't like the options that have been forced on us."

            I know this sounds a bit silly, but... well, I’m not the one who was writing it.  You could see the same thing on The Nine, when the former hostages would either have conversations just like that with each other, or repeatedly tell their friends and loved ones they wouldn’t understand because “you weren’t there.”   And it happened on Alcatraz, too.  The Warden would constantly dodge questions or try to bury answers under pseudo-philosophic homilies.
            Let me give you an example of doing this sort of thing correctly.  One you’d heard of long before LOST.
            I’m sure most of you are familiar with Psycho, the Robert Bloch novel that was adapted into the famous Hitchcock film.  Even if you haven’t seen it (or the pointless shot-for-shot remake) you probably know the general plot, yes? 
            So... who’s the main character of Psycho?
            If you said Norman Bates, you’re wrong.  He doesn’t even show up until half an hour into the story.  The truth is, Psycho is almost an anthology of three different stories connected by the theft of a large sum of money and the motel where the supposed thief vanished.  Our main characters are—in their respective tales--the thief, the police detective, and the thief’s sister.
            Y’see, Timmy, this is why Norman’s secret is so powerful.  We’re never seeing it with him, we’re always seeing it through the other characters—the one’s the story’s actually focused on.  If Norman had been one of the main characters, the story would be required to focus a certain amount of attention on him—while at the same time trying not to let us see or learn anything about him.  Instead he’s relegated to a supporting role in the story, even though he’s the character we’re most interested in.
            The Nine, The Event, and Alcatraz (and more than a few other stories I’ve read) all tried to put the mystery front and center while also trying to keep it a secret.  They wanted us to be interested and invested in characters who didn’t want us to know anything about them. 
            And that just won’t work.
            Next time, I want to talk about my collection of zombies.  Sort of.
            Until then, go write.

Thursday, January 26, 2012

Feels Like The First Time

            Okay, first off, a bit of shameless self-promotion that also pushes my street cred, as the kids say.  Amazon Studios is developing a film with the working title of Original Soldiers.  It’s a sci-fi tale about human soldiers leaping into action when America’s droid army is shut down by an opponent.  I’m one of five folks (well, four folks and a writing team) who were hired by Amazon to expand my simple pitch off their logline into a full treatment.
            So, between that and Ex-Communication, things might slow down a bit in the month of February.  Just letting you all know now.
            Oh, and check it out.  You can still pick up The Junkie Quatrain.  It's very cheap for your Kindle or Kindle app of choice.  Just saying...
            Anyway...
            I’d like to begin this week, if you don’t mind, with a personal question or two.  You don’t have to answer them, but I want you to keep the answers in mind.
            Your current significant other—girlfriend, boyfriend, wife, husband—do you remember the first time you saw them naked?
            Not just the date or time, mind you.  Do you remember how you felt when you saw them like that?  What thoughts were going through your mind?  What emotions?  What your pulse and breathing were like?
            Follow up question—do you remember the most recent time you saw them naked?  How did you feel then?  What thoughts were going through your mind?
            Next question—do you remember your first day at your current job?  Do you remember looking at things, meeting people, learning the ropes?  Can you recall any thoughts that went through your mind?
            Follow up question—what was today like at your current job?  What did you think about?  Who did you see?
            Some of you may have picked up on the point I’m trying to make here.  There’s a big difference between the first time something happens and the fiftieth or hundredth or five-hundredth.  My first day on a film set was exciting as hell, but at the six year mark even the days with naked women on set were pretty dull, and at twelve years I was generally known as one of the cynical people on any given set.
            Now, I make that point so I can make this one...
            One mistake I see a lot in stories and screenplays is when writers can’t make the distinction between the first time your readers or audience are seeing something and the first time the characters are seeing it.  Characters go to work, have dinner with family, or teleport to their secret lair and express confusion or wide-eyed amazement at these things.  It knocks a reader out of the story because it’s immediately apparent this is something the characters should be familiar with.
            It sounds silly to say it so blatantly, but if I’ve been living in New England my whole life, a brutally cold winter shouldn’t come as a real shock.  If I’ve worked for Discorp for over a decade, their business practices shouldn’t catch me off guard.  If I’ve been with Phoebe for eight or nine years, the odds are we’ve seen each other many, many times and had many, many conversations about many, many things.
            The thing is, many storytellers become focused on the fact that this is the first time the readers have seen Wakko in action or me and Phoebe together.  So these folks tweak dialogue and reactions to play to the audience, rather than the genuine responses of the characters.  It seems correct from a mechanical point of view, but once you really study the moments this sort of thing falls apart.
            Here’s an example of doing it right that ties back to my opening questions--Mr. and Mrs. Smith.  When the film begins, the title characters have been married for several years and... well, things are getting a bit stale between them.  They’ve had all their conversations.  This is why Mr. Smith doesn’t really react much when Mrs. Smith—played by Angelina Jolie—is walking around their bedroom in her underwear.
            Let me repeat that last bit—Angelina Jolie is walking around their bedroom in her underwear.
           While this would be an absolutely amazing moment for about half of the folks reading this, Mr. Smith barely notices it.  He’s been seeing her in her underwear for years, after all.  It may be the first time all of us have seen her dressed (or undressed) like that, but for him this is just like every other day.
            This is closely related to another problem I’ve brought up once or thrice before, the dreaded  “As you know...”  When one of my characters says “as you know,” they’re admitting right up front that they and the person (or people) they’re speaking to already know the facts that are about to be spoken.  It’s clumsy, it’s wasted space, and it’s unnatural because it sounds like these folks are having a conversation for the first time when common sense tells us this has to have come up a dozen times before.  My girlfriend and I have been together for over seven years now, so we don’t need to talk about when our birthdays or anniversaries are.  I helped my best friend move into his house, so I don’t need to ask him where he keeps the rum or how to get to the bathroom.  My dad’s been an expert in his field for decades, so I don’t think he’d be stunned to learn working on reactors involves potential exposure to radiation.
            This is why the ignorant stranger is a great story device.  When I’ve got a character who’s new to the world of the story it gives me someone who can experience things for the first time while my other characters can be well-established sources of knowledge.  Yeah, I know where the rum’s kept in the house, but Yakko doesn’t, so my readers will accept it if Yakko and I talk about where to find the booze or the bathroom.
            Another great example if this is—
            SPOILERS—
            Men In Black .For James Edwards, the police officer who becomes Agent J, the MIB is an intergalactic wonderland of non-stop discovery.  He’s the ignorant stranger.  Alien life forms, alien customs, alien technology—it’s all new to him.  But consider Agent K.  Everything that excites or stuns J makes him yawn.  Invading battle fleets, extraterrestial assassins, talking dogs, rocket cars, a warp-drive powered superball... these things all bore the hell out of him.  In fact, as the story progresses it becomes clear that K is at a disadvantage because he’s become so jaded by the world he lives in.
            One of the worst things I can do as a writer is confuse the first time the audience sees something with the first time the characters do.  It’ll come across as false and it’s one of those clumsy mistakes that’s hard to recover from.  So just remember... the first time for you might not be the first time for me.  And it’s almost definitely not the first time for him.
            Next week, as we’re close to opening day for a lot of the big screenplay contests, I thought I’d talk about a lot of common screenplay mistakes I’ve seen.
            Until then, go write.