December 28, 2013 / 2 Comments

That What Got Done, 2013 Edition

            Well, here we are yet again.  Another year gone by.  Time to look back and see how well we stuck to our resolutions.
            If you bother to stop in here and read these little rants, I’m guessing you’ve thought about being a writer.  Not a weekend dabbler, not an incorruptible artiste, but someone who wants to make some sales and write for a living.  And the only way to do that is to write.  Not to plan, not to research, but to sit down at the keyboard and start typing out my story one word at a time.  There’s no other way to get something done and no other way to get something sold.  If I’m not writing… it’s just not going to happen.
            So, all that being said… what did you get done this year?
            Me?  I started 2013 already waist-deep in Ex-Purgatory, which was due at the end of April.  Of course, before I could finish that my editor at Broadway had some notes for me on Ex-CommunicationReally good notes, for the record.  There were only one or two things we argued over, and even on those we found a solid middle ground that made us both happy.
            But before I did those, I had to go over the copyeditor’s notes on Ex-Patriots.  They were doing a quick run through it before the re-release in April.  So I spent a day or three on that.
            At least, I would’ve, but first I had to go over the new layout proof for Ex-Heroes.  It was coming out in February, after all.  So that got priority.  Then Ex-Patriots, then Ex-Communicationnotes, and then back to working on Ex-Purgatory.
            Of course, by that point, I now had copyedits on Ex-Communication.  And a layout proof for Ex-Patriots.  And even some very last minute input on the Ex-Heroescover.  And after all that, I could get back to Ex-Purgatory.
            Until… well, I’m sure you can see the pattern at this point.
            Despite all this, I still managed to get Ex-Purgatory done on time.  It went long, and then I cut it way back, and then my editor suggested a few other cuts and some other additions.  We did a bunch of work on it, and in the end it went from a book I was kind of worried about to one that I’m almost proud of.  And it’ll be in stores in less than three weeks.
            That was the first eight months of 2013.
            Somewhere in there, between rewrites and layouts for Ex-Communication, I started a new book.  Something kind of urban-fantasy-ish, but a lot darker.  I was about 15,000 words into it when I went to Comic Con.  Alas, after talking with my agent and my editor, it’s going on the back burner for a little bit.  Hopefully it won’t end up being my new Dead Moon
            There was also another idea I worked with for a while.  I pitched this one to my editor as “Neil Gaiman’s Neverwherecrossed with Cannonball Run.”  Which, if nothing else, caught his attention.  For the double-handful of you who were at Booktopia this summer, it’s the story I mentioned about the Model T Ford. I was about 19,000 words in when new deals were finalized with Broadway.  This one’s still going to happen, but it’s been pushed a bit further down the line.
            I wrote a handful of short stories, too.  “Flesh Trade,” alas, didn’t make it into Clive Barker’s upcoming Midian Unbound anthology (I only cried a little bit at that).  But the guys at Kaiju Unbound really liked “Banner of the Bent Cross” and the folks at Evil Girlfriend Media said yes to another story (which I can’t talk about quite yet).  I also polished up an old tale, “Contraption,” for an upcoming collection of short stories from Permuted Press.
            And since then I’ve been working on my current book, The Albuquerque Door.  Well, there’s been some concern about the title, but I’m hanging onto it as long as possible.  I’m about 25,000 words into it so far. 
            Plus there were also thirty-eight posts here (to be honest, one of my worst years since I started the ranty blog).  And another thirty posts on other pages I keep.  Plus a dozen or so promo articles for different books (including a handful of titles from Broadway’s new Doctor Who line).
            Thing is… I feel like I slacked off a lot this year.  There were a few times when I was waiting to hear back on deals or between drafts or just feeling burned out by that glut of work at the start of the year… and I took a day off.  In and of itself, there’s nothing wrong with it, and I didn’t miss any deadlines, but the truth is I took off a couple of days I really had no business taking off.  Days I should’ve been writing.  I look back at this past year and I think that I really should be further along in that urban fantasy story.  The Model T story should have a lot more to it, too.  I look at this list and think I didn’t write enough this year.
            How about you? How much did you write…?
            Next time—next year, really—I’d like to take a few minutes to talk about what I talk about here.  A mission statement, if you will.
            Until then… Happy New Year.
            And go write.
June 3, 2013

Bonus Preview!

Just a quick note for those of you who are interested in such things.

There’s a free preview of Ex-Communication up on Scribd right now.  It’s the first flashback chapter, and it comes right after the preview in the new edition of Ex-Patriots.  Check it out.

So if you already bought that, you’ve got the first two chapters of the book.

Enjoy.

September 21, 2012

One Step Ahead

            First off, if you want it, there’s kind of a bonus post this week.  Go check out Ebon Shores, a great little horror site from down under, where I was asked to prattle on for their “Wednesday Writer” column.  Actually, page through some of the past ones, too.  There’s a lot of really good stuff there.

            Speaking of horror…
            By nature of my chosen career, I tend to read and see a lot of horror stuff.  Specifically, post-apocalyptic stuff, usually with some form of zombie in it.  And there’s a certain recurring flaw that always gnaws at me. 
            It’s when characters do or say things that experience says they shouldn’t.  The kind of things that common sense tells you they should’ve figured out not to do or say ages ago.  How often do you see zombie hunters in t-shirts, even when they know one scratch could mean death?  Or that one guy who sets his gun down and walks a few yards away from it?  Or, knowing there could be zombies in the area, they reach into the dark room and start feeling around for a light switch with their one, ungloved hand…
            Or sometimes it’s what characters don’t do.  They’ll find a door and talk about how it might be locked, how it could be dead bolted, or how there may have been a cave in that’s blocking it from the other side.  The one thing none of them will do is actually attempt to open the door.  And if they did and it didn’t open, it’d never occur to them to try that key they found on the floor down the hallway.  Even though they know there’s a zombie apocalypse going on, they’ll forget to barricade windows.
            Simply put, it’s when the readers can see one step ahead and the characters can’t.  It’s when the audience can foresee the consequences of an action (or inaction), but the people in the story don’t.  And if the reader stops to think about that sort of thing, then I’m doing something wrong as a writer.  It means my characters’ choices or actions are breaking the flow of the story.
            There’s a very, very bad sequel to a very, very good classic World War Two movie.  Early in the film, our heroes arrive in Germany in a stolen plane.  The plan is to pose as German soldiers and officers, sneak away, and then begin their mission behind enemy lines.  It’s only after the four hour flight, as the plane is taxiing to a stop at the end of the landing strip, that the mission commander realize the one flaw in their plan.  One of the team members is a black man!  How will they pass him off as a Nazi?
            The resolution was kind of clever in that quick-fix sort of way, but it didn’t change the fact that the whole situation was stupid as hell.  The one question everyone asks at this point is “Why the hell did no one think of this before?”
           Y’see, like most readers and movie watchers, I have a tendency to think about what I’d do in a given situation.  I’d punch that guy.  I’d lean in and kiss the girl.  I’d make sure my shotgun was loaded beforeI stepped out into the zombie-filled hallway.  And nothing frustrates me more as a reader than when I see an immediate, obvious flaw in a character’s motivations or actions.

            That’s not to say every character should react like me (or you, or that guy).  If the writer’s got any sense of empathy, though, I should at least be able to see why characters make the choices they do.  I might’ve punched that guy, but Jack Reacher might be biding his time or just trying to keep a low profile and not to stir up too much trouble.  Many of us might’ve leaned in to kiss Elizabeth Swann, but we all understand why Will Turner feels bound by duty, honor, and social mores to let that opportune moment slip by. 

            Y’see, Timmy, one of the best things I can do as a storyteller is think one step ahead.  For the most part, the audience shouldn’t be able to think of something I didn’t already think of.  Oh, there’s always going to be that five or six percent who shriek about “totally obvious” things, but forget them.  I don’t need to cover everything, I just need to answer the immediate questions.
            “Hanging a lantern on it” is a great example of being one step ahead.  I know this odd coincidence is going to bother the reader, so I’ll have one of my characters point out how odd and coincidental it is
            LOSTdid this a lot to help take the edge off some of the oddities of the island and the plot devices they needed to further the story.  Hurley questions why there’s a brand new washer and dryer set in the otherwise very retro underground station called The Swan.  Kate and Sun wonder what kind of person travels with a pregnancy test.  Ben questions the odds of a spinal surgeon literally dropping out of the sky just a few weeks after he learns he’s got a tumor on his spine.
            Looking ahead can also be a good gauge for exposition and figuring out how much is too much.  In a couple of my books and novellas I have scenes of scientific jargon and techno-speak.  But I don’t need to explain things out in full and exacting detail.  I just need to be one step ahead and address enough points that my story doesn’t get hung up on my lack of explanation. 
            In Ex-Patriots I explain that the military’s been “training” zombies to follow simple orders.  But I don’t leave it at that.  In the same chapter I introduce the idea of the Nest—a NEural STimulator—which sends electricity to parts of a zombie’s brain in order to reactivate it.  I don’t need to explain what parts of the brain, how much voltage or amperage, or how they first tested it.
            A famous example of this is in Back to the Future, when Doctor Emmet Brown tells us he’s made a time machine out of a DeLorean.  Even as we’re processing this, though, part of us wondering… well, how?  How does someone turn a sports car into a time machine?  It’s kind of goofy and ludicrous all at the same time.  And then Doc shows us the flux capacitor and tells Marty (and the audience), “this is what makes time travel possible.”  And it’s glowy and it buzzes and, well… yeah, okay, that makes sense. A DeLorean on its own couldn’t travel through time, but a DeLorean with a flux capacitor channeling 1.21 gigawatts of electricity…
             Doc’s addressed our question before we even got to ask it out loud. So the story never pauses and we get carried along into the next bit.  And the DeLorean goes down in history (no pun intended) as probably one of the top three fictional time machines.
            Sometimes all staying ahead takes is being aware of where the characters are in the story.  If I’m confusing the first time I’m showing something to the reader with the first time the characters have seen it, that’s going to lead to problems.  There are mistakes and screw ups that we’ll accept from amateurs in any field, but not from people who’ve supposedly been doing this for a while (whatever this is).  If my plot point depends on a Master Sergeant in the Army not knowing how to load a pistol or the head chef at a restaurant not being able to tell salt from sugar… well, there better be a damned good reason for it.
            Stay one step ahead of the reader.  Know where they’re going to go, be there waiting for them, and guide them back to the path you want them on.  Not the path where they growl in frustration and shout “Why the heck did they…?”  And then toss your manuscript in that big pile on the left
            Next time, by request, I wanted to talk about how you can use plot and story to develop an idea.
            Until then, go write.
August 17, 2012

No Coloreds Allowed!

            Well, that title got everyone’s attention real quick, didn’t it?

            Allow me to explain, then feel free to report me…
            When it comes to adjectives, one of the easiest bits of description to drop into writing is colors.  I can tell you I’m sitting here right now on a gray chair wearing a blue shirt and black shorts (there’s a major heat wave going on in Los Angeles right now) and my tan cat is trying to get my attention.
            Now when a lot of us hit that mid-phase in our growth-as-a-writer arc, we start using metaphors for everything.  My shirt isn’t blue, it’s sky-colored.  My shorts are the color of coal.  My cat, Charlie Baltimore, is linen-colored.  Some folks get comfortable at this point of the arc and they’re the ones who tend to use lots and lots of purple prose (color pun not intended, but it works so I’ll go with it).
            The catch, however, is when people develop the habit of describing everything as “colored.”  Even colors.  Which is wrong.
            I’ve seen some folks describe things as red colored, yellow colored, and blue colored.  That’s just silly.  And it’s excess words I could cut.
            Y’see, Timmy, colors are inherently “colored.”  If I tell you my shirt is blue, it’s understood that I mean “my shirt is the color blue.”  So I wouldn’t tell you “my shirt is the color blue colored.” 
            I should never use the word colored with colors.  I shouldn’t have blue-colored sky or green-colored grass.  They’re already colors—what else could they be?  Blue flavored sky?  Green textured grass?  Snip that word and have blue sky and green grass.
            I use coloredwhen I’m making descriptive comparisons.  A girl with strawberry-colored hair can wear a grass-colored dress, for example.  My zombies have chalk-colored eyes.  One draft of Ex-Patriotshad Stealth described as “shadow-colored.”
            Use the Find feature and search through your latest work for uses of the word colored.  Make sure it’s being used correctly.  Slash it if it isn’t.
            Next time I may be a bit cramped for time, so you’re either going to get a rant about time bombs or another screenwriter interview (if I’m really up against the wall).  But if I do, I’ll make sure it’s a fun one.  Or, at least, highly controversial. 
            Until then, go write.

Categories