Monday, October 22, 2012

No Mo Wri Mo: Why I Am Regrettably Not Doing NaNoWriMo This Year

I am a two-time NaNoWriMo winner. It took me years to get up the courage (and a lost job) to finally get around to it in 2010. Right before NaNoWriMo, I had nearly completed my first novel, Emerald City Dreamer. For NaNoWriMo, I paused that project, and started a whole new project, an alternative history vampire fantasy, with my novel The Sun Never Rises.

As much as I loved the world I built, and my character, and the ending, I have not read The Sun Never Rises. Not once in two years. I haven't had time.

My third novel, Emerald City Hunter, I wrote during last year's NaNoWriMo.

For both projects, I came in at higher than 50,000 words. Right around 65,000 each. I proved I have no problem cranking out high word counts. Awesome.

Unfortunately, those words suck. Not all of them, but enough of them to make editing a real problem. I realize this is the point of NaNoWriMo, to write words that suck, just so long as you write them. And yes, those were my first novels, so they were probably going to suck anyway. I had a lot to learn about how to make 50,000+ words not suck. Some of those I learned during the writing process itself, and some during the grueling editing process.

Now that I've learned those lessons, I'm going for the long view.

I understand my pace better now. It is similar to my process for short stories. Plan, outline, write a few chapters, go back, revisit the outline, revise some future scenes in the outline, edit the past scenes a little bit, write the future scenes, revisit the outline, edit some old scenes, and so on.

When I do it that way, I end up with is a draft that is more satisfying and very solid. It is nearly ready, with some slight polish, to be shown to my writer's group, Cloud City Wordslingers. It is less frustrating and time-consuming when it comes to editing.

Word counts are antithetical to this process. And it takes longer than 30 days.

November is coming, and I see everyone talking about NaNoWriMo. I'm sad. I want to be along with you guys, cheering each other on, sharing problems and woes, and hitting 2-4k words per day. I will feel a little left out, and a little nostalgic for those past NaNoWriMos that were probably a lot more miserable than I remember. It will be hard, knowing I could have another novel under my belt. But I know it will be a novel that will likely have to sit in a drawer for years before I get time to edit it.

I will, however, be doing "WriMo". I will be writing all month. I won't be watching word counts. I won't be aiming at 50,000 words on a single project. I am aiming to finish Emerald City Iron (novella, already half done) to draft that can be read by my fellow Wordslingers. And I will be aiming to begin plotting the next novella. I will share progress on Twitter and here.

Good luck to all WriMos, whether you're doing a novel, a couple novellas, or a pile of short stories. I thank the NaNoWriMo people for holding that carrot out to me for years prior to 2010, to make me keep thinking, "I ought to get back to writing someday", and to letting me win two years in a row.

Labels: , , , , ,

Monday, July 25, 2011

Fuzzy-Wuzzy Was A Bear: Killing 'Was' Brings Prose To Life

Every time our writer's group gets a new writer, I give a certain speech: Was is a dead-word.  Kill it.  It is the low-hanging-fruit of better writing, an alarm that jumps off the page and demands, "Make me more interesting!"

Was is clearly a verb, but doesn't move.  It offers no description or action.  It notifies us that a thing exists, but tells nothing about how it exists or what it is doing.  The nouns and adverbs that follow it will surely describe more, but that is no excuse.  Replacing a was is an easy opportunity to make prose more colorful and active - and possibly a chance to trim extra words. 

Was (and his sister were) is also a warning that something may be amiss.  Many was's indicate that the passive voice was used.  (See what I did there?)  It can also indicate that the writer was using an extra verb that can simply be cut.  (See what I did there again?)

So what do we do with those was's?  Some of them are extremely easy to cut if you know the tricks.  Some are troublesome -- you know it needs to go, but how?  And some are impossible to remove.  Moreover, not all was's are bad.  Fuzzy Wuzzy really was a bear, and I can't think of any better way to say it.  And there are other factors to consider -- like voice, rhythm, and pacing -- and it we don't want to sacrifice those, do we?  Sometimes not.

So let's start with the easy was fixes, and move up to the more complex.

Replace with a more active verb.

The soldier was on the hill.

Snore.  There he was.  On a hill.  Boring.  I want to know more about that soldier; I want to see him.  Here, the was indicates the author is telling, not showing.

The simplest fix: Find another verb.   

The soldier stood on the hill.

It's still kind of boring, but maybe the soldier is boring, and he'll be doing something exciting in a moment.  Maybe we don't want to distract the reader with what that soldier is doing, because all we need say is that he's there, and the real action is coming up from a different direction.  But maybe the soldier is doing something else while he's standing there, and it is I, the author, who is being boring.  Here are a few better examples:

The soldier waited on the hill.
The soldier paused on the hill.
The soldier hid on the hill.
The soldier gripped the side of the hill.
The soldier watched from the hill.
The soldier shivered on the hill.

All of these examples give more depth, more information about the emotional state or intentions of the character.

The last one is my favorite.  He's still just standing on the hill, but with just one word-change, he is now feeling something and we know
it's cold or scary up there.  Even if he's just a side character, a cardboard cutout, our story feels more real.

The first two examples required very little work.  But the others?  I had to make an extra effort to think and visualize, until I came up with some idea of what that guy was actually doing up there.  In many cases it is worth the extra effort, because if we can't see it, our readers surely can't.

Replace with the verb that is already there.

Frank was asking about the party.

Was is superfluous here.  It adds nothing.  Simply cross it out and change the tense of askFrank asked about the party.

Very rarely, the was adds a subtle connotation of additional information.  For example: I was hoping we could go out tonight.  This indicates that maybe it's too late, that some doubt has crept in about the verb, or that the status has changed.  Was is then sometimes a substitute for the dreaded had which we also want to reduce, i.e. as an alternative to, I had hoped...  In this case, keep the was, or go with the had.  They are equals.

Sometimes with this method, we need to change the verb for it to make sense.  And that's good, too.  See how this sentence transforms:

Pie filling was stuck all over her face.

vs:

Pie filling covered her face.

Passive voice.

Passive voice rarely belongs in fiction prose.  It takes a lot of practice to get good at finding passive voice in your prose.  Was is an easy warning sign.  (Bearing in mind that these are not mutually exclusive: you can write active voice with a was, and can write passive voice without it.)

Much has been written on passive voice, what it is, and why it is bad, so I won't go deeply into it here.  In summary, it is a sentence structure where something is acted upon, rather than an actor acting on that thing.  The reader never knows who the actor is, only that an action was done.

Here is an example with a was:

The old man was killed in cold blood.

So what?  The old man may be murdered, but so is any sense of shock over the crime.  We almost have an exciting sentence there, but it sounds a little stilted and stifled.  Let's change it to active voice, and watch that was disappear:

Someone had killed the old man in cold blood.

Even with a had in there, this act of murder is now a surprise -- as it should be.  We still don't know who the killer is -- that is still a mystery -- but now I feel more interested in finding out who dun it.

The sentence would be better rearranged.

Sometimes the was indicates an awkward or weak sentence.  A rearrangement of the ideas, the order in which they are presented, will remove the was and also make it a better-written sentence.

Simple example:

Billy wanted to say something nice, but all that came out was, "You're not very fat."

This is clumsy, and the was lets us know.  Not a lot of rearranging here:

Billy wanted to say something nice, but he could only manage, "You're not very fat."

Let's try another one:

Of all the things the witch loved, the wand was her favorite.

This sentence is okay.  It loads the concepts of action in the prepositional phrase, and all that's left is to note the wands existence (and then modify that with favorite).  There is a certain voice to that, but it's a little awkward. 

We could logically rearrange the sentence, putting the concept of the wand first:

The witch loved her wand most, out of all her favorite things.

That method works better the more complex the sentence is.  I've seen a lot of unweildy paragraphs smooth right out after rearranging the order of the concepts and dropping the was's.

Or we can keep the logical order, but break it up:

The witch favored a lot of things.  But mostly, she loved the wand.

New example:

Walking all the way to Mordor was out of the question.

Try:

No, they couldn't walk all the way to Mordor.

Show, don't tell.

That squirrelly was: it shows you that you may be telling.

I know I said this already.  But in my soldier example, I took the easy way out.  I simply replaced the verb.  But the was may indicate a drastic lack of detail you should fill in.  So allow me to elaborate.

She was old.

Holy crap, so much telling!  I heard we're not supposed to do that!  But if it is true that she really is old, how do we say it?  Describe the things that make her old:

She walked with bent back, her hair coarse and gray.  Her voice rasped like the last breath of a dying animal.  And she smelled like orange juice.

That's better.  And not a single was anywhere.  The change hurt my word count, but at least it's not boring.

That being said...

Don't kill every was.  Sometimes they are stubborn things that are not worth the trouble.  Sometimes simplicity is best.  Sometimes you are just describing a scene, and don't need your objects doing anything, just lying there being red or dirty or strong or soggy.  As with all writing rules, this one is meant to be broken.

But generally, this tip will clarify your prose, give your characters and settings depth, and add pep to your action scenes.

Labels: ,

Tuesday, August 10, 2010

Defcon 18, Writer's Group, and Publishing

Three topics that have nothing to do with one another!

Two weekends ago, I attended Defcon with Roland. Last year, I live-blogged the event, but that was a different year, a different blog. :) This year, I learned interesting things about facial recognition software, cyberwarfare, psychosonics, and how to flirt. The first three I learned via talks, and the latter I learned via practice at parties.

As Defcons go, this one was very uneventful. There were only two things of note: GSM cellphone conversations can now be hacked. In other words, even though your conversation is encrypted, someone can set up a listening station and hear your call. For about $1500. I expected to hear of someone getting arrested for this, but oddly, no. Secondly there was a knife fight at a party next door to the party we were attending. Yes, there was an arrest in that case.

No killer bees, no ATM fraud, no amazing pranks for everyone to buzz about. Even the Wall of Sheep was pretty weak, since they encrypted the Defcon network this year.

I wonder if it was just an off-year, or if Defcon really is going mainstream.

Last Saturday I attended my new writer's group for the second time. I ended up liking this this group. My expectations were really high, but they've met them. I've loved the stories I've critiqued so far.

The only thing I worry about is that I'm not sure anyone is a grammar Nazi. My old group had a great grammar Nazi. Sure, she'd strongly disapprove of stylistic creativity; i.e. if the story flowed better to break grammar, she would still make a big deal out my precious sentence fragment. But she served a very useful function: She knew all about grammar, and nothing missed her careful eye.

In the new group, I worry that I am the grammar Nazi. This scares me for two reasons: One, I don't actually know everything there is to know about the elements of style. And two, if I'm the grammar Nazi, who will catch my mistakes?

Maybe next time I'll have something to submit, and then I'll know for sure. I should work in a few intentional, glaring mistakes, just to see if anyone catches them.

Yesterday I worked really hard on the final steps of publishing my novella, Make Willing the Prey. It took much longer than I had planned to do the final revisions, think of a title, write the new epilogue, finish the cover art, format the text, reformat the text, write the description, and do the final tweaks. I was almost two weeks past my unrealistic self-imposed deadline, so yesterday this thing was getting published OR ELSE!

So at something like 6:30pm I finally clicked Save and Continue at Amazon. Now I'm just waiting for their final review. I'll make a formal announcement when it's finally ready.

I am a bit worried about the cover image. Even though I uploaded a file of the right dimensions, the sample thumbnail looked distorted. I'm really hoping it was just a low-quality preview and that the actual cover art will look fantastic. Otherwise I will have to keep tweaking it and will likely hold off on the official announcement until it's perfect. Amazon's 24-48 hour lead-time on any changes is really frustrating in this regard.

I'm going to take the rest of this week to focus on marketing and posting it to Smashwords and other markets. (Unrealistic expectations again? lol).

Then I'm going to start cooking on the next project. I only have vague ideas right now. Since I haven't written any fiction from scratch in ??? years, I will spend some time this week on writing exercises to get the juices flowing. I can work from an outline, but I need my characters and settings to exist first so I know what actions they might take. I'd like to talk more about this, but this post has wandered enough already. :)

Labels: , , , ,

Friday, July 16, 2010

Too busy to blog?

The life of a full time writer is apparently a very busy one. I've been so busy with editing and marketing that I haven't had time to blog. :)

I've been studying all the methods for self-publishing ebooks. I really want to avoid spamming, but also somehow need to build momentum. This is the quandary all indie authors face.

Today I'm going to a writer's group for self-publishers. I've also found a few possible workshop-style writer's groups, so I can critique and be critiqued. This will be especially important as I write entirely new pieces. For now, I've just been editing stories that have already been through a workshop in one way or another.

My horror novella is coming along quite well. I'm pleased with how I've revitalized the plot. It was a lot of work, but I think it was worth it. I should finish the finale scenes today (barring interruption) and then the second draft will be done! I'm sure it will need one more round of minor edits, a review from the family, and then another round of major edits, then to Amazon it goes!

Last week I posted about how I'd published one of my stories, but I don't think I included any links. Which is folly. This week I improved the description and lowered the price to $.99. Just 99 cents! Well, it's short, and it's my first story, so y'all get a discount:
Guardian at the Gate by Luna Lindsey


Van (aka Zornon the Devastator) has helped to create a new world within a world. But his most recent code patch has caused a bit of havok, unlocking a puzzle that isn't just a game. Pretend fantasy becomes real, and Van's friends must strike a bargain with the Guardian at the Gate .

Guardian at the Gate
is a lighthearted novelette available on Kindle books for only 99 cents.

Oh, and I almost forgot! I made my first sale this week too! I've sold two copies. That's a grand total of $.70 gross profit! I'm on my way now for sure. ;)

Labels: , , ,