Major massive milestone

IMG_0473

Ten years.

That’s kind of a long time. Over the course of the past decade, aside from the usual 8-5 job and various successes there, I’ve built most of a house, added a workshop, duck-house, chicken-coop, took up woodworking (I managed to sell a few pieces of furniture), fiddled with bonsai, learned much about the art of home-brewing, and, not least significantly, had three children (okay, I didn’t, my wife did, but I was present). In short, a lot has happened. I’m sure at this point you must be thinking: This guy is a smug and self-important bastard isn’t he? If you’re not, perhaps you should be -I would be. The thing is I’m not. In fact, if you think I’m calling these ‘accomplishments,’ you’re wrong*. These are the daily distractions of my life, all of which I have chosen, for the past several years, but don’t worry, I’m going somewhere with this.

When our first son was born, I had my trusty notebook with me for the hospital stay, where I was treated to three nights on a too-short couch and the absolute panic associated with being a new parent. The story I was working on is the very same I’m working on now. It started as two separate sci-fi novels that morphed and merged into a single fantasy series that dropped all of the sci-fi elements**. Back then, I was mostly focused on background and constructed language development. I’d be a lying jerk if I tried to claim I had anything like a plot, and the characters were sketches of people, without any sort of personality.

Now, for the milestone bit: I finally, after a decade, have a full first draft.

Holy crap, it took you ten years to write 90,000 words? What’s wrong with you?

Hey! – I got it done, and bits of it are fairly well polished and have even been through beta-readers. It happened last night. I hit the end of a sentence and spent a few minutes trying to think of where I might go next with it and realized the remainder of the ‘story’ was superfluous. Nothing more needed to be said.

Wait! You dodged the question about what the hell took you so long!

Alright! Jeez. It may be that it took me a decade, but in all of that random stuff I was spending time on, I wasn’t necessarily spending much energy on writing. In fact, there were stretches of months, maybe even as long as a year, where I didn’t spend any time thinking about writing at all. It wasn’t until about two years ago that I once again dusted off my notebook and started working on my story. I made some serious progress. Over the course of a few months I ran through what’s now the first five or six chapters of the book, as well as a few other chapters sprinkled in throughout later parts of the book. Then, I sort of shelved it again. We had some family stress and I just didn’t work on it.

An interesting side note here, I had only confided in my wife about this project while working on it, that is until last spring. I started thinking about it again and decided to confide in a friend and co-worker what I was doing. I’m not sure why, but I did.

Anyhow, sometime last summer, I had a shit or get off the pot moment. I don’t remember it exactly, and neither does my wife, though she assures me that’s what happened. The bottom line is that I said (probably after a few beers), I’m going to finish this book dammit!

Are you going to get to the point or just ramble on?

I’m just about to get there, stop interrupting.

What I think I realized is that I had been waiting for some sort of inspiration to strike me. (Emily Russell wrote a good article related to this, if for some reason you’re reading this and haven’t seen that, just stop and read that first – but come back here!). Inspiration isn’t going to finish a book. It’s not the sort of thing that just hits you while you’re driving down the street thinking about the trees*** It happens while you are trying to write, while you are actively thinking about your story. Sure good creative ideas do seem to strike in a flash of brilliance, but the truth of the matter is that you were thinking about it. It’s even better if you’ve written something down. Of course, I’ve had those moments where something strikes me as funny or odd, and I scribble down a note for later. Perhaps that’s a bit of inspiration, but inspiration doesn’t make a book. Writing does. Work does. Effort does. Like it or not, sacrifice does.

Possibly one of my favorite inspiration stories is the J.K. Rowling story about Harry Potter. She was on a train and the boy who lived just sort of walked into the train car with her. Isn’t that lovely? Boom – A multi-million dollar franchise was born! Bullshit. After that bit of inspiration, Rowling worked her ass off on back-story, setting, character development, plotting, and themes. It took years and loads of work (and quite a bit of luck too, but I’m not going there). For all practical purposes, ALL of the story comes from hard work and focus.

So. There it is. Lesson learned. If you want to finish, you have to focus and not make excuses about having too many other responsibilities. One paragraph per night? Good enough. You’ll get there, just keep on it.

* Except for the day-job stuff. I really am pretty full of myself there, but that’s not what I want to talk about.

** Someday I will blog about the circumstances leading to this, but not today.

*** I do this, don’t laugh. My family all thinks I’m a freak because I’ll fawn over the trees on any sort of hike. I will actually stop on a trail, grab a leaf and pontificate about a particular type of tree.

Progress report – stuckish

Storm

Did I mention I gave up on trying to finish the book before fixing the main character? No? Well, that’s because I haven’t been on here much lately. I should be, it’s good for me, forces me to write more.

Anyhow, I have been working on my book, but haven’t managed to finish those last pesky few chapters. I got stuck. In part, I’m tired from my day job – this is our busy season, and also because I wasn’t able to make chapter 17 work. The reason I couldn’t make it work has to do with the fact that it’s the point in the story where the main character has to make some decisions. Since the character started out so weak, it had no punch and basically fell flat for me as both a reader and writer.

How am I supposed to make the reader care about the character and decisions he’s having to make if they didn’t care about him in the first place? Well, that’s a good question. So, stuck as I am, I went back to chapter one, and stared at it for a day or two. No help there. So, I went back further to a page or three of back-story that won’t ever see the light of day (at least not in the book). I wrote my character with a new perspective. Gave him a reason to fall into the circumstances that come later. In a few sentences, I laid out his world view in something like a monologue. This seemed to work. Of course, it means re-writing the entire book as it is so far. Not awesome, not awesome at all, but necessary. That said, I’m not really changing the plot or the events, more the reaction to those events, and perhaps a little be of how those elements of plot are arrived at.

What was good about this approach though is that if I get stuck or the story starts to seem flimsy, I can refer back to that bit of writing to remind me how the character is supposed to react. So far, I’m back up to chapter 12. One interesting side effect of revising the main character in this manner is that it gives the main supporting character more to work with thus making him stronger as well.

At this point if you’re not asking, why didn’t I just do this to begin with? you probably should be. Truth is, I thought I had. I wrote a whole long chapter of back story, but it didn’t really get at his motivations and perspective. Most of the other character’s I’ve tried to write usually start out fairly strong in my mind, but this character never has. It’s one of the reasons this project took so long to get off the ground.

I’ve still got lots of polishing to do, but now I feel like I’m once again making progress – even if I still haven’t actually finished the first draft.

Fantasy research – creepy in fantasy (Coraline)

One of the lovely things about writing is that often your research involves reading other stories. Not to lift work, of course, but to understand tricks of the trade, analyze what worked, or didn’t, and try to figure out why. One of the key things War of Shadow needs, in certain parts, is an element of creepy. I want the setting to feel slightly uncomfortable as the characters move through the landscape. So, in an effort to understand how other writers do it, and discover tricks to how it might be adapted for my ow purposes, I started by picking up Coraline by Neil Gaiman. There are other books in the queue, but that was the first. It’s a book I should have picked up a long time ago. I did see the movie just after it came out, and thought it was very good and pretty darn creepy.

First off, my opinion of the book – Inside the first couple chapters, I felt as though it was more of a sketch, and left me wanting. However, the story really picks up the second time Coraline goes into the world in the other flat. All throughout, the imagery is very good, and the writing excellent. As I went through, I’m not sure I felt particularly unsettled, or creeped-out. The last few chapters were just suspenseful enough, not overdone, and I was compelled to go on to the next page.

From the perspective of a writer, if I take only one thing away from the book, is the suspense at the end. That said, I did read it for the creepy, and I have to say that I don’t know what I was expecting to feel while reading the book. Perhaps that I’d lose a bit of sleep thinking about a disembodied hand because I’m waiting for it to scrabble out from under the bed? Maybe find my self thinking twice about opening a locked door in case I might find button-eyed mockeries of a loved one? No, I didn’t feel any of that. But was that the point? Probably not.

In verbally ruminating upon the story, my wife reminded me that Coraline was meant to be for younger readers. From that perspective, had I read this when I was a child, it probably would have kept me from sleeping. However, as an adult not so much. The reason, I think, I didn’t find it as creepy as I may have been expecting is because Coraline does not, except for one place, seem to be in any imminent danger of certain death from the Beldam. It sort of feels like this is a possible outcome, at some distant point in the future, not an immediate threat. I sort of wonder if that distinction doesn’t tend to temper the ‘creepy’ for me. I also wonder if this was not by design, to make the story a little less horrifying for young readers.

After having read this book, did I learn anything about writing creepy?

I think so. First off, you need to rely on the principle of “things aren’t what they seem.” I can see this being difficult for the writer to pull off in a fantasy novel because the reader already isn’t familiar with the world. I think it’s one of the reasons I’m having some trouble with it. There are so many things being introduced, this concept can be a bit of a challenge to really highlight. How does the reader know that we’re dealing with something that’s not quite right? In urban fantasy, where the world is generally the same as the one we’re sitting in, you can rely on that familiarity to set the bar for ‘normal.’ In this case, unexpected things are going to seem unusual to the reader, and the character only needs to react in a manner generally consistent with things not being as they should be. I think the same trick can be used when you have an unusual world. The reader will have to rely on cues from the characters. Elements of the world that are mundane to the characters should read that way. When things are supposed to be creepy, they should be contrasted with things that the character takes as normal, as well as what the reader would consider normal.

Another thing that I was reminded of while reading this book is the choice of words used for imagery. In one particular example from Coraline, Neil Gaiman uses the look of a spider to describe the color of the other mother’s skin. What he did there was use something generally regarded as uncomfortable (I mean who likes spiders, really?) in the description when other descriptions would suffice. Of course, this is just how it’s done, although it’s also easy to lose sight of when you’re trying to manage some 100K words of text. Think about any particular story that has a bit of creepy to it. Inevitably there are sentences about slithering snakes and the jerky motions of spiders and the like. However, I also think that this can be overdone.

For now, I’m not quite ready to begin going back and polishing in this particular flavor, I’d like to finish a few other books for research, and I’d rather focus my attention on finishing up the first drafts of the last 2 – 3 chapters of War of Shadows (I really need to start working out a name that I plan to use, or this is going to stick.) and also finish fixing up the bits that need help.