Prequels, Problems With

— March 05, 2012 (8 comments)
Prequels are not always bad. Just want to throw that out there. But in general, when I hear a new book or movie is a prequel, I'm immediately less interested than I could be. Why?
  1. Because sometimes the prequel is not the story I want to know more about. The original was. Example: Phantom Menace. (I really, really, really don't care that Anakin built C-3P0, even if you could solve all the plot holes that represents.)
  2. Because sometimes the questions raised in the original are best left unanswered. Example: Phantom Menace. (Midi-chlorians. Nuff said.)
  3. Because the prequel's story often ends near the inciting incident of the original -- usually an unsatisfying place to end. Example: Phantom Menace. (I know Anakin is Obi-Wan's apprentice. I know he becomes a great Jedi then betrays Obi-Wan. I know he's corrupted by the Emperor. This is not the cliffhanger you're looking for.)
Maybe the prequel's should've started here instead.


I don't intend to ever write a prequel, but if I did, I would ask myself the following questions:
  • Is this a story I would want to tell, even if I'd never made the original? Example: X-Men: First Class. I don't know about you, but for me, the relationship between Magneto and Xavier has always been one of the main draws to the X-Men story.
  • Does this story answer questions that need to be answered? Better yet, is it about separate events entirely? Example: Indiana Jones and Temple of Doom. Yes, this was a prequel (having occurred before the events of Raiders of the Lost Ark). It might not have been as good as the other two, but it didn't try to answer stupid questions like: "Where did Indiana get his whip and fedora?" *
  • Could this story stand alone without the original? Would it be satisfying? Example: Captain America. Technically a prequel (having occurred before the events of Iron Man and directly leading to the upcoming Avengers movie), but pretty dang satisfying on its own. (Except for the fact that he probably could've avoided getting frozen in ice).

So, prequels. What do you think makes a good one? What else is wrong with Phantom Menace?

* The Last Crusade did answer those questions, but because it was a flashback, and related to the rest of the story, I was cool with it. What I didn't want was an entire movie with River Phoenix Indy.

Enjoyed this post? Stay caught up on future posts by subscribing here.


There is No Way This Could Fail. None.

— March 02, 2012 (14 comments)
You know that moment in Mockingjay when they finally rescue Peeta, and Katniss spends a paragraph or so thinking how happy she and Peeta would be and how she would hug Peeta and tell him all the things she was never able to tell him before?

And was anyone surprised when Peeta wasn't okay?


I think this is becoming a pet peeve of mine, in YA especially, where the MC starts thinking about how great it will be when their plan works then (of course) the plan doesn't work.

(This goes the other way, too. Whenever the MC is dubious about a plan or is certain someone has died, it's a sure thing the opposite has occurred and everything is going to be okay.)

It shouldn't bother me. It's just a trope, right? I mean, you can't have the MC go, "Was that his voice in the next room? It had to be. Of course it was! He was back home safe, and everything would be like it was." And then he's really there and everything is just like it was. That's boring, right?

But when I read a narrator's thoughts like that, it either makes me feel like the MC is dumb or it blows away all the tension ("Well I thought it might be him for a second, but now...").

But what to do about it? I'm sure I do this all over the place, and it can't be a bad thing all the time, can it?

Seriously, is this even an issue? Or should I file this under temporary insanity (too late)? What do you guys think?

I think what I want is for authors to be aware of the signals they send the reader. We (authors) go, "I'll trick the reader into thinking everything is okay then BAM!" But the reader is all, "Do they actually think I'm buying this? Oh, look: 'bam'."

We need to find a better way.

Enjoyed this post? Stay caught up on future posts by subscribing here.


Living With Boys

— February 29, 2012 (7 comments)
When Anthdrawlogy challenged us to do a self-portrait, I admit I kind of cheated. Then again, this is what you're most likely to see if I'm playing with the boys, or if I lie down, or sit down, or step away from the computer for two seconds...


Enjoyed this post? Stay caught up on future posts by subscribing here.


Why Starting With a Flash-forward is Cheating

— February 27, 2012 (13 comments)
First, definition. A flash-forward is when the story jumps forward from the present time (you know, like a flashback, but the other way around).

Second, clarification. Flash-forwards by themselves are not cheating. They're a perfectly valid literary device that goes in your toolbox with all the others. I'm specifically talking about starting a story with a flash-forward.

Third, disclaimer. Starting with a flash-forward can be done well. This post is about why it usually isn't.

Got all that? Let's move forward.


Here's what it looks like. You're reading an awesome action scene. The MC is hunting the villain, terrified that, if she doesn't find him in time, the villain will turn her little brother into one of his Zombie Ninja Minions. She must be on the right track because she is suddenly ambushed by three ZNMs. She beats one off in an awesome display of intelligence and martial arts, but the other two grab her, force her off the edge of a cliff...

The chapter ends. You turn the page, desperately wanting to know what happens only to discover the next chapter starts weeks before. The MC is with her little brother, both happy. Nothing is wrong. There are no Zombie Ninja Minions. The MC is not an awesome martial artist yet.

Writers will often do this to start with action or to hook the reader. They want the reader invested in some moment further in the story so they'll read through the whole beginning to get there. There are some problems though:
  1. The reader is forced to start the story twice. If your regular beginning isn't good enough, don't add a more exciting one. Fix the first one.
  2. A lot of tension and surprises are gone. We know about the ZNMs, and so feel nothing when the MC first discovers their existence. Likewise with when her brother is kidnapped. And we know that, no matter what horrible things happen to her between now and the flash-forward, nothing permanent will happen to her until then.
  3. Even though the opening is a flash-forward -- and the next chapter is the present -- the reader will feel like everything leading up to the flash-forward incident is backstory. Really, really long backstory.
Now if the reader keeps going, they'll eventually get over that feeling and get invested in this new present. But not all readers will keep going. The trick to hook the reader doesn't always work.

This doesn't mean you can't do it. As I said at the start, it can be done well. Not having done one myself, my tips to do so are rudimentary:
  1. Your second beginning (in the present) has to hook the reader just as much, if not more, than the flash-forward beginning (just like any other prologue).
  2. Be intentional about what you reveal in the flash-forward.
The Firefly episode "Out of Gas" is a great example of flash-forward (seriously, go watch it RIGHT NOW). Part of why it works is because we see so little. We only know that the ship is dead in space and everyone is gone except the captain (who's bleeding from a stomach wound). So not only do we want to know whether the captain will live, but we also want to know how things got so bad to get him in that state. Where is everyone else? Are they dead? Who did this to them?

Have you seen flash-forward done well? Where (and why, do you think)?

Enjoyed this post? Stay caught up on future posts by subscribing here.


The Perfect Utensil

— February 24, 2012 (8 comments)
(Remix)

For some, the perfect eating utensil is the most elegant, the most practical, or simply whatever they're used to. But me? I want a utensil that allows me to eat the most amount of food with the least amount of trouble. Let's begin.

Like most Westerners, I grew up with the knife and fork. It's the perfect combination for a culture that eats primarily meat (although I'll never understand why manners dictate you switch hands for slicing and eating). Ideally suited for steak, the fork/knife can handle a wide variety of other foods. So it's good, but not the best. Let's look at some other options.

The chopsticks are the choice of the East. They are an elegant utensil, and you're super-cool if you can use them. But cool as they are, they just don't make any sense for countries whose primary dish is rice. I mean, seriously guys, how am I supposed to eat this?

Next up is the spork. The scooping action makes it an ideal choice for rice and small pastas, and the tongs give it the versatility to spear larger chunks of food. The spork is almost perfect, but used alone, it is difficult to get reluctant peas onto the shovel or to slice foods too big for one bite.

Enter Thailand. In Thailand, chopsticks are only used for noodle dishes (sometimes not even then). The preferred combination is a fork and spoon, but you'll have to throw out your Western mindset: the fork goes in your off hand. The spoon is your primary utensil.

The spoon allows you to carry much more food. And the fork allows you to fill the spoon to overflowing with a minimum of effort. You can also use them to cut anything except a tough steak.

But then why are you eating tough steak anyway?

The fork-and-spoon is the best combination I've found yet, to the point where I often ask for a spoon when I visit the States. But there is one eating utensil that tops even these.

The tortilla! This amazing invention serves as a plate, but you can eat it! Pile it with food, roll it up, and shove it all into your mouth. The best part is, when you're done, there's nothing left to wash but your hands.

Geez, I could go for some Mexican food right now.

How about you? What do you like to eat with?

Enjoyed this post? Stay caught up on future posts by subscribing here.


Reasons to Quit Writing

— February 22, 2012 (15 comments)
A lot of people quit writing because they wrote one (1) novel and were told it was no good.

Now I don't care who told you that -- whether it was agents, editors, Gene Wolfe, or your mom -- that is a terrible reason to quit writing. Of course your first novel is no good.

Here are some real reasons to quit writing:
  1. You actually want to make money.
  2. You'd rather watch Downton Abbey.
  3. There is a contract out on your life, and you have to stay off the grid.
  4. Telling stories is against your religion and/or you have taken a vow of silence.
  5. You hate writing.
  6. Jesus has returned and/or the Mayans were right.
  7. You want to be a doctor, a teacher, or some other job that actually helps people.
  8. Writing would postpone the completion of your freeze ray.
  9. You are part of an alien race that shares a single hive consciousness and, therefore, does not tell stories.
  10. You are dead.
So next time one of you tells me you're not going to write anymore, don't tell me you don't have the talent or you're out of ideas or that Stephen King said you couldn't string two words together with a teleprompter. Those are not reasons, they're part of the game.* They are obstacles to overcome.

But if you finish that freeze ray, let me know. I might want to borrow it.

Can you think of any other good reasons to quit writing?


* Except maybe the Stephen King bit.

Enjoyed this post? Stay caught up on future posts by subscribing here.


Describing Beauty

— February 20, 2012 (7 comments)
If you don't remember, I suck at description. But that means I learn obvious lessons all the time and can pass the savings on to you!

Today's lesson: describing someone that is beautiful.

My problem was I didn't want to just say she was beautiful (although I did that too). I wanted to show it. But how? What features are beautiful? Long hair? Sparkling eyes? Pink lips?

Turns out (and this will be obvious to most of you, but such are the depths of my sucking) that the specific features don't matter. Like that old cliche about the eyes of the beholder, what matters is how the narrator feels about the character.

And you show that the same way you show any emotion: through comparisons, thoughts, actions, etc. For example:

Sister Victoria was a dark-skinned woman in her forties. She sat cross-legged on her own cushion, wearing the same white robe all the monks wore. Her hair was black as the shadows, curled at her shoulders.

What Hagai noticed most was her eyes. They were alluring in a way that made Hagai uncomfortable, only because she was over twice his age. He shuddered.

"Ten years ago, men would dance naked in the streets just so I'd smile at them. Now," she smiled, "they shudder."
There are all kinds of features here, but we don't really know Victoria is beautiful until the 2nd paragraph.



A red-haired girl in a white robe stood over Hagai. She wasn't much older than Hagai, though she was far prettier. She watched him patiently, her hands clasped beneath large sleeves, a polite smile on pink lips.
 Hagai straightened, scratching his head. "Uh, hi."
This one comes right out and says she's pretty (which is fine too, sometimes), though it doesn't say much about how Hagai feels about her, except that he's a little uncomfortable. Either way, that has nothing to do with her features.


"You're a pirate?" Sam asked her.

"Oy, ain't you the nummer." Then before he could blink, she was in his face with a blade under his chin. "Aye, I'm a pirate. Now give me a reason to cut you."
 
Bottomless eyes were cents away from Sam's. The smell of garlic and vanilla filled his head. He didn't want her to cut him, didn't want her to back off either.
This one hardly has any features at all (seriously, what does "bottomless eyes" even mean?), but there's no question what Sam thinks of her.


Anyone got any more tips for me?

(And before you go saying, "How can you say you suck! Those are great!" Let me remind you that these passages are the result of gobs and scads of revisions. Whatever good you think you see in them is the result of many fabulous beta readers.)

(Maybe one of these days I'll show you what these scenes used to look like.)

Enjoyed this post? Stay caught up on future posts by subscribing here.