October 3, 2013 / 3 Comments

Do You Need Mechanical Assistance?

Your minds always go there first, don’t they.  You bunch of perverts…

Some of you may remember Watson, the supercomputer that played against two Jeopardy champions and beat them. Watson was specifically built to understand human language. That was the sole point of its appearance on Jeopardy—to show that a machine could be programmed to understand subtext and clues and irony well enough that it could compete against humans using their rules.

Why am I talking about a supercomputer—a fantastic and kick-ass supercomputer, granted—when I keep insisting this place is about writing?

Do you know how big Watson is? Or how long it took to build? How many people were involved? Watson was a six year project for a team of more than twenty engineers and programmers (plus a ton of students interning with IBM). It’s a collection of processors and drives as big as my first apartment in Los Angeles (which means it’s probably the size of your kitchen).

And you know what? Even with all that computing power and information, Watson still got things wrong. Several times in warm up games and even during the main event, Watson would miss obvious clues and give the most bizarre answers. If you run the numbers, Watson didn’t know how to answer a given question almost twenty percent of the time. When it did answer, it still got one out of every ten questions wrong.

Now, again, please remember what I just said how long all those people worked on this machine. A machine that was built for the specific purpose of understanding human language. That’s going to be important when I ask my next question.

How much work do you think went into your computer’s word processor?

For that matter, how much went into just its spellchecker? Or into that automated proofreader? Do you think the people programming it were IBM-level experts in their field? And in the field of writing?

I’m not going to be a hypocrite and say these things are useless tools.  I use my spellchecker.  I usually make a pass with it during my third draft.  There’s nothing wrong with using it as a tool to help me check spelling.  But I have no illusions about the fact that I still need to be the one checking the spelling.

See, I don’t blindly accept every “correction” it offers me.  And this isn’t my entire third draft.  I still go through the whole manuscript line by line, sentence by sentence.  It can take me four or five days.  Because I know the  machine can’t be trusted to do it for me.

I’ve said it before, and I’ll keep saying it until people listen.  A computer cannot write for me.  It doesn’t matter how cool someone’s system is, it won’t do the job.  That’s why, whenever you ask a real writer for advice, they’ll usually say to hire a good editor, not to upgrade your software.

If I want to be a writer—a working, paid writer–I need to know how to spell and how to use words and what those words mean.

These words, for example.

fair and fare –one of these is how you get through an experience

dual and duel—one of these refers to citizenship

vain and vein – one of these refers to similar things

tics and ticks – one of these is a twitch

mute and moot –one of these is irrelevant

reckless and wreckless—one of these means rash

vain and vane – one of these makes you think this song is about you

desert and dessert—one of these has whipped cream

shudder and shutter – one of these means to shake

soar and sore—one of these relates to diseases

vane and vein—one of these shows the flow of air or liquid

wreck and wreak—one of these means to inflict

wait and weight – seriously, it’s embarrassing I have to ask.

As in the past, these are all mistakes I’ve seen in articles or books over the past few months.  When I come across one and it makes me shudder (not shutter), I know I have to add it to the list.  Yeah, I keep a list.  You don’t think I just come up with all this stuff from scratch once a week, do you?

In the interest of fairness… Two of these are mistakes I’ve made in the recent past.  One of them even slipped past me, my proofreaders, my editor, the copyeditor, and then me again while I looked over copyedits and layouts.

Did you know all of the answers?  Did you know what the other word meant, too?  If I don’t know them both (know—not sort of recognize) there’s a good chance I’ll make a mistake at some point.  And, granted, we all make mistakes sometimes.

But some people make a lot of mistakes.  And they don’t catch any of them.  Because they’re depending on their computer to do it for them.

Next time, I want to…

Actually, before I talk about next time, I’d like to break my rule about no self-promotion and guide you to the Kaiju Rising Kickstarter.  It’s a giant monster anthology featuring stories from folks like Peter Stenson, Timothy Long, Larry Correia, and a bunch of others (including me).  It’s already fully funded (even stretch goals), but there’s still a day or two left to snag a copy for yourself, and possibly a pile of add-ons.

Anyway, that being said…

Next time, I want to talk about exceptions.

Until then, go write.

September 27, 2013

Not Dead Yet!

September 26, 2013

How To Be A Drama Queen

            Or a drama king.  I don’t judge…
            When we left off, I’d just finished babbling about narrative structure, which is how my readers experience a story.  Before that was linear structure–how my characters experience a story.  This week, I want to talk about how those two structures come together within a dramatic structure to form the actual story.
            Warning you now, this is going to be kind of big and rambling, but I’ve also included a lot of pictures.  Go grab a snack now and hit the restroom.  No one will be admitted during the dreadful story dissection scene…
            Also (warning the second), the story I’m going to dissect is The Sixth Sense.  If you’ve never seen it and somehow avoided hearing about it until now, stop reading and go watch it.  Seriously, if you’ve made it this long without having someone blow it for you, you need to see that movie cold.  People love to give M. Night Shyamalan crap, but there’s a reason The Sixth Sense made him a superstar writer-director.  So go watch it and then come back.  The ranty blog will be here waiting for you when you get back.
            Seriously.  Go.  Now.
            Okay, everyone back?
            As the name implies, dramatic structure involves drama.  Not in the “how will I make Edward love me” sense, but in relation to the building interactions between the elements of the story.  In most cases, these elements will be characters, but they can also be puzzles, giant monsters, time limits, or any number of things that keep my protagonist(s) from achieving his or her goal.  Any story worth telling (well, the vast, overwhelming majority of them) are going to involve a series of challenges and an escalation of tension.  Stakes will be raised, then raised again.  More on this in a bit.  
            Now, I don’t mean to scare you, but I’ve prepared a few graphs.  Don’t worry, they’re pretty simple and straightforward.  If you’ve been following the ranty blog for a while, they might even look a little familiar.
graph #1
            On this first graph (and all the others I’ll be showing you) X is the progression or the story, Y is dramatic tension.  This particular graph shows nothing happening (the blue line).  It’s an average day at the office, or maybe that long commute home on the train.  It’s flat and monotone.  No highs, no lows, no moments that stand out.
            Boring as hell.
            Harsh as it may sound, this graph is a good representation of a lot of little indie art films and stories.  There are a lot of wonderful character moments, but nothing actually happens.  Tonally, the end of the story is no different than the beginning.
graph #2
            As a story progresses, tension needs to rise.  Things need to happen.  Challenges need to arise and be confronted.  By halfway through, the different elements of the story should’ve made things much more difficult for my main character.  As I close in on the end, they should be peaking. 
            Mind you, these don’t need to be gigantic action set pieces or nightmarish horror moments.   If the whole goal of this story is for Wakko to ask Phoebe out without looking like an idiot, a challenge could be finding the right clothes or picking the right moment in the day.  But there needs to be something for my character to do to get that line higher and higher..
            Now, here’s the first catch…
graph #3
            Some people start with the line up high.  They begin their story at eight and the action never stops (I’m looking at you, Pirates of the Caribbean: Dead Man’s Chest).  This doesn’t leave a lot of room for things to develop, but the idea is that you don’t have time to see that because we’re hitting the ground running and going until we drop.
            You might notice the line on this graph looks a lot like that first one up above.  It’s pretty much just a straight line because there isn’t anywhere for things to go.  And, as we established, straight lines are pretty boring.  They’re monotone, and monotone is dull whether the line’s set at one-point-five or at eleven.
Rising with setbacks
            That’s the second catch.  Dramatic structure can’t just be a clean rise like that second graph.  That’s another straight line.  And straight lines are… well, I’m sure you get it by this point.  In a good story, there will be multiple challenges and the hero isn’t going to succeed at all of them.  He or she will win in the end, of course, but it’s not going to be easy getting there.  They’ll face mistakes, surprises, bigger challenges, and determined adversaries.  For every success, there’s going to be some setbacks.  So that blue line needs to be a series of peaks and drops. 
            If you know your physics, you know that we don’t feel a constant velocity.  Think about riding in a car.  As long as it’s a steady speed, you don’t notice.  You can drink coffee, move around, whatever.  What we feel is acceleration—the change in velocity.  Those ups and downs are when things stand out, when we know something’s happening.
            Make sense?
            So, with that in mind, here’s a big graph.
             This is everything together.  X is narrative structure.  It’s the story progressing from page one until the end of my story, novel, or screenplay.  Y is dramatic structure. We can see the plot rising and falling as the characters have successes and failures which still continue to build.  And the letters on the blue line are the linear structure.  We’re beginning at G, but there are two flashbacks in there that go back to A and D.
            Notice that D-F flashback.  Even though it’s near the end of the story, it’s got more dramatic weight than G through K.  This is the big, easy trick to dramatic structure.  No matter what my narrative is doing, it has to keep increasing the tension.
            Y’see, Timmy, this graph is what pretty much every story should look like if I map it out.  They’re all going to start small in the beginning and grow.  We’ll see tension rising and falling as challenges appear, advances are made, and setbacks occur.  They’re not going to be exactly like this, but the basic structure—an escalating, jagged line—is almost always a given.  Small at the start, increase with peaks and dips, finish big.
            Simple, yes?
            Keep in mind, this isn’t an automatic thing.  This is something I, as the writer, need to be aware of while I craft my story.  If I have a chapter that’s incredibly slow, it shouldn’t be near the end of my book.  If a scene has no dramatic tension in it at all, it shouldn’t be in the final pages of my screenplay.  And if it is, it means I’m doing something wrong.
            Now, that being said, it should be clear that where things happen within a narrative is going to effect how much weight they have.  Again, dramatic structure tells us that things in the beginning are small, things at the end are big.  Something that’s an amazing reveal at the end of the story won’t have the same impact at the beginning.
            Let me give you an example.  It’s the one I warned you about at the top.  I’d like to tell you an abridged version of The Sixth Sense.  But I’d like to tell it to you in linear order.
            Ready?
            The Sixth Sense is the story of Malcolm, a child therapist who is killed by one of his former patients in a murder-suicide.  Malcolm becomes a ghost, but doesn’t realize he’s died so he continues to “see” his patients.  Several months later, across the city, a woman becomes jealous of her new husband’s daughter, Kyra, and begins to slowly poison the girl.  It’s about this time that Malcolm meets Cole, a little boy with the power to see ghosts, and decides to take Cole on as a patient, helping him deal with the crippling fear the ghosts cause.  When Kyra finally succumbs to the poison and becomes a ghost, she finds Cole, too—inadvertently terrifying him when she does.  Malcolm suggests to Cole that helping her might help him get over his fear.  Cole helps expose Kyra’s stepmother as a murderer and also helps Malcolm come to realize his own status as one of the deceased.  And everyone lives happily ever after.  Even the dead people.
            The happily ever after is a bit of an exaggeration, granted, but it should make something else clear.  When the narrative of this story follows the linear structure, a huge amount of drama is stripped away.  It’s so timid and bland it almost reads like an after-school special rather than a horror movie.  A lot of the power of this story came from the narrative structure.  The order Shyamalan told this story in is what gave it such an amazing dramatic structure (and made him a household name).
            This is what I’ve talked about a few times with flashbacks and non-linear storytelling.  There needs to be a reason for this shift to happen at this point—a reason that continues to feed the dramatic structure.  If my dramatic tension is at seven and I go into a flashback, that flashback better take it up to seven-point-five or eight.  And if it doesn’t, I shouldn’t be having a flashback right now.  Not that one, anyway.
            For the record, this is also why spoilers suck.  See, looking up at the big graph again, E is very high up in the dramatic tension.  It’s a big moment, probably a game-changing reveal, in a flashback.  If I tell you about E before you read the story (or see the movie or watch the episode or whatever), I’ve automatically put E at the beginning–it’s now one of the first events you’ve encountered in the narrative.   And because it’s at the beginning, it’s now equal to G in dramatic tension.  Because things at the start of the story always have very low tension ratings.
why spoilers suck
            The thing is, though, E isn’t at the start of the story.  It’s near the end.  So now when I get to where E really is in the story, it isn’t that big spike anymore.  It’s down at the bottom.  The dramatic structure of the story is blown because I didn’t get that information at the right point.  It even looks wrong on the graph when the blue  line bottoms out like that.
            If you want an example of this (without giving anything away), consider Star Trek Into DarknessI can’t help but notice that a lot of people who were demanding to know plot and character information  months before the movie came out were also the same ones later complaining about how weak the story was.  Personally, I went out of my way to avoid spoilers and found the movie to be very entertaining.  It wasn’t the most phenomenal film of the summer, but I had a lot of fun with it
            It’s dismissed as coincidence.
            Now, here’s one last cool thing about dramatic structure.  It makes it easy to spot if a story is worth telling.  I don’t mean that in a snide, demeaning way.  The truth is, though, there are a lot of stories out there which just aren’t that interesting.  Since I know a good story should follow that ascending pattern of challenges and setbacks, it’s pretty easy for me to look at even the bare bones of a narrative and figure out if it fits the pattern.
            For example…
            By nature of my chosen genre, I tend to read a lot of post-apocalyptic stories and see a lot of those movies.  I’ve read and watched stories set in different climates, different countries, and with different reasons behind the end of the world.  I’ve also seen lots of different types of survivors.  Hands down, the least interesting ones are the uber-prepared ones.  At least a dozen times I’ve seen a main character who decides on page five to turn his or her house into a survival bunker for the thinnest of reasons, filling it with food, weapons, ammunition, and other supplies.  But twenty pages later, when the zombies finally appear…  damn, are they ready.  Utterly, completely ready.
            In other words… there’s no challenge.  There’s no mistakes, no problems, no setbacks.  The plot in most of these stories just drifts along from one incident straight to another, and the fully prepped, fully trained, and fully loaded hero is able to deal with each one with minimal effort.  That’s not a story worth telling, because that story is a line.  And I’m sure you still remember my thoughts on lines…
            On the other hand we have C Dulaney’s series, Roads Less Traveled.  The series begins with The Plan, protagonist Kasey’s careful and precise strategy for surviving the end of civilization.  But almost immediately, the plan starts to go wrong.  One of the key people doesn’t make it, a bunch of unexpected people do, and things spiral rapidly downward.  Challenges and setbacks spring up as the tension goes higher and higher.
            That sound familiar?
            And honestly… that’s all I’ve got for you.  I know I’ve spewed a lot, but I wish I could offer you more.  Y’see, Timmy (yep, it’s another double Y’see, Timmy post), while the other two forms of structure are very logical, dramatic structure relies more on gut feelings and empathy with my reader.  I have to understand how information’s going to be received and interpreted if I’m going to release that information in a way that builds tension.  And that’s a lot harder to teach or explain.  The best I can do is point someone in the right direction, let them gain some experience, and hopefully they’ll figure it out for themselves.
            So here’s a rough map of dramatic structure.  
            Head that way.
            Next week, I’ll probably blab a bit about Watson, the supercomputer.
            Until then… go write.
September 19, 2013

Once Upon a Time…

            …there was an aspiring writer.  And he lived in a beautiful world of wild dreams and deep denial…
            But let’s not talk about that guy.
            Last week I talked about basic linear structure.  This week I want to talk about narrative structure.  Narrative structure relates to—big surprise—my narrative.  It’s about how I’ve chosen to tell my particular story.  While events unfold in a linear fashion for the characters, how I decide to relay these events to my audience can change how the story’s received and interpreted (more on that in a bit).  So linear is how the characters experiences the story, narrative is how the reader experiences the story.
            One quick note before I dive in.  Within a story there might be a device or point of view, like a first person narrator, which gives the appearance of “telling” the story.  For the purposes of our discussion here, though, if I talk about the narration I’m talking about the writer.
            That being said…  here we go.
            In a large chunk of the stories any of us will encounter, the linear structure and narrative structure are going to be the same thing.  The story starts with Wakko on Monday, follows him to Tuesday, through Wednesday and Thursday, and concludes on Friday.  It’s simple and straightforward, but that doesn’t mean you shouldn’t use it.  My own book, 14, fits in this category.  It’s loaded with twists and reveals, but the linear structure parallels the narrative.
            There are also a fair number of stories, though, where the narrative doesn’t follow the timeline of the story.  Sometimes the writer does this with flashbacks, where a story is mostly linear with a few small divergences.  Other times, the story may be broken up into several sections and the reader needs to follow clues as to where these sections line up.  These are often called non-linear stories, or you may have heard it as non-linear storytelling (it was the hip new thing for a while there). 

           A great example of a non-linear story is Christopher Nolan’s early film Memento, where the story is actually told in reverse order, starting at the end and moving to the beginning.  My own Ex-Heroes series employs numerous flashbacks (although it’s worth mentioning that the flashbacks are all in linear order).  There was also a brilliant Marvel Comics miniseries by Roger Stern and John Byrne called The Lost Generation, which involved a time traveler moving back through history to see a forgotten superhero team, get wiped out as they saved the world, then moving forward (for the traveler) to see how the group formed and the origins of the heroes.  The issues were even numbered in reverse order.

            Now, there’s more to narrative structure than just wanting to switch around my story elements so I can look all cutting-edge.  If I’ve chosen to jump around a bit (or a lot) in my narrative, there’s a few things I have to keep in mind.  Be warned, we’re moving into an area that requires a little more skill and practice.
            First off, putting things in a new narrative order can’t change the linear logic of my story.  As I mentioned above, the week goes Monday through Friday, and this is true even if the first thing I do is tell you what happened on Thursday.  Monday was still three days earlier, and the characters and events in my story have to reflect that.  I can’t start my book with everyone on Thursday baffled who the murderer is, then roll the story back to Monday were everyone witnesses the killing and sees the murderer.  If they knew then, why don’t they know now?  There’s no logic to it (barring a case of mass amnesia).  If I have Phoebe act surprised that she owns a cat on Friday and then have the narrative jump to her finding the cat in an alley on Tuesday, I’m going to look like an idiot while my linear structure collapses. 
            These are very broad, simplistic examples, yes, but it’s amazing how many times I’ve seen this problem crop up.  Writers want to switch stuff up, but ignore the fact that the logic of their story collapses when the narrative elements are put in linear order.  This is an easy one to fix, it just requires a little time and work.  And sometimes a bit of rewriting.
            The other big issue with having narrative and linear structures so far apart is that people need to be able to follow my plot.  I can have tons of fancy word choices and beautiful language in my story, but readers are still going to put it down if they can’t figure out what’s going on. 
            For example…
            Think about when a little kid tells you a story about Iron Man and Batman and Snuffleupagus and there’s a moon base and they had a spaceship that Iron Man made before they fought the werewolf and the werewolf hates only getting to go out on Halloween so he decided when he was a little kid because only Snuffleupagus liked him and the rest of the time he has to get shaved because it’s too hot so he decided to go to the Moon so he could be a werewolf all the time and no one would make fun of him cause he didn’t know there were aliens on the moon but Batman saw the wolfman spaceship and tried to stop it and asked Iron Man to help and they fought the werewolf and Batman knew the werewolf when they were kids before he was Batman so he decided to help him move to the moon because they broke his spaceship but Iron Man had another spaceship he built after the Avengers movie and it looks like a big Iron Man and the werewolf had promised Snuffleupagus when they were little that he could come and so they got him out of the broken ship and you kind of tune it out and start mentally skimming.  I mean, you just skimmed a lot of that, right?  It jumps around so much that after a point it just becomes noise.
            Y’see, Timmy, the problem with chopping up my narrative too much is that people are automatically going to try to put it in linear order.  As I mentioned last week, we all do this almost automatically because it’s how our brains are set up.  The harder the narrative makes it for someone to reorganize the linear story, the less likely it is they’ll be able to follow it.  Which means the more likely it is that they’ll put it down.
            I talked about the idea of a detective at a crime scene last week.  If you’ve read a few mystery stories—or watched a few crime shows—you know a standard part of the mystery formula is the hero going through the events of the story and putting them in linear order for the other characters and the audience.  And how many are there? Eight or nine, usually?  Call it ten elements that are out of order and  the writer’s admitting it might be kind of tough to keep up at this point.
            There was a movie that came out about eight or nine years ago (I’ll be polite and not name it) that was a non-linear mess.  I don’t think there were two scenes in it that followed each other.  So we’re talking about well over a hundred scenes that were all scrambled and out of order.  Maybe as many as two hundred.  The actors were fantastic, but the story was impossible to keep up with.  It didn’t help that certain events repeated in the story.  Again, to be polite and protect the innocent, let’s say one of the characters was in a serious car crash and then was in another serious car crash two years later.  The audience was getting random scenes of burning cars, ambulances, emergency surgeries, recovery, and physical therapy… from two car crashes.  So we’re left trying to figure out which car crash the character was experiencing/recovering from at various points–once it was clear there’d been two car crashes–and then figuring where this scene fit in relation to all the other scenes.  The audience had to spend their time trying to decipher the movie rather than watching it.
            So non-linear structure can be overdone and become a detriment if I’m not careful.  This can be really hard to spot and fix, because it’s going to depend a lot on my ability to put myself in the reader’s shoes.  Since I know the whole linear story from the moment I sit down, the narrative is always going to make a lot more sense to me, even though for someone coming in cold it might be an illogical pile.  This is one of those times where I need to be harsh and honest with myself, because if I don’t my story’s going to be incomprehensible.
            That’s narrative structure in a nutshell.  Maybe more of a coconut-shell.  However I decide to tell my story, it still needs to have a linear structure, it still needs to be logical, and it still needs to be understandable. 
            Next time, I want to explain how linear structure and narrative structure combine via dramatic structure to tell a good story.
            Until then… go write.

Categories