Skip to content

A Heartwarming Knit

When I was a kid, my stepmom tried to teach me how to crochet. That didn’t go as well as either of us hoped. I eventually learned how to crochet a stitch, but I could never double back to make a second row, much less a third or fourth. None of my crochet projects ever made it past the “really long chainA ball of blue, green, and yellow yarn with two knitting needles crossed under it of yarn” stage.

Flash forward to this December when I was scouring the stores in town (all three of them) looking for some inexpensive slipper socks, just something simple and cheap that I could wear around the house and toss in the wash every few days. I found plenty of slippers and lots of socks, but the only slipper socks I could find were $5 to $10 a pair. I might pay that for something handknitted by an indie crafter using high quality yarn, but for something that cost maybe, maybe 50 cents in yarn and would have been cranked out in 30 seconds by a machine in a factory? Forget it. I’d learn how to knit them myself. How hard could it be?

Yeah, because I’d done sooooo well at crocheting. And this time I didn’t even have anyone to teach me.

Still, that was thirty years a long time ago. Besides, yarn’s cheap. Knitting needles are, too, so even if I ended up tossing the whole mess in a drawer as a bad attempt, I’d be out no more than a pair of those overpriced store slipper socks.

A word of warning here. When I get excited about a project, I tend to overbuy. Ooo, I think, I could make such-and-such with this. Or I could do such-and-such with that. Chad cringes every time he hears those four little words: “I had an idea…”

This time, though, I decided to be smart. One skein of yarn. One pair of knitting needles. A free project pattern. And if I finished that first project, I could buy more. I didn’t even buy a “teach yourself to knit” book or sign up for a class. I searched the web and found a site with free instructional videos: knittinghelp.com, which I highly recommend to anyone interesting in learning to knit.

I struggled at first. I could not figure out casting on for the life of me. I burned through massive amounts of bandwidth watching those knittinghelp.com videos. I even made Chad watch them, and then watch me try it to see what I was doing wrong.

Slow going to say the least. But eventually it clicked, and one row turned into two, then three, then more.

I scheduled time each day to knit. A half hour here, an hour there. I started knitting at night while we watched TV. After we got back from my dad’s funeral in Kentucky, I couldn’t think straight enough to write, so I lost myself in knitting instead. And then early last week, I finished this:

Green, yellow and blue knitted scarf with ribs, raised squares, and fringes

Guess what everybody's getting for Christmas this year?

Not bad for only picking up my first set of needles a month ago, eh?

The pattern is called Heartwarming. It’s a simple one that uses nothing more than knit and purl stitches. Perfect for a beginner like me, and yet it looks anything but plain.

The yarn is called Banana Berry Print and is part of Red Heart’s Super Saver Economy line. A bit coarser than I’d like, but I’m happy to report that after washing it once, it’s softened up considerably. Hopefully washing it a few more times will take the last bit of roughness out of it. If not, I’ll probably stay away from the Super Saver Economy line for future projects. I can get softer yarn for not much more money, both from Red Heart and from other manufacturers.

I’ve already started my next knitting project, a pair of armwarmers in a light blue yarn from Caron’s Simply Soft line to coordinate with this scarf.  And after picking up a stitch dictionary, some knitting magazines, and several skeins of yarn from a variety of shops like Michael’s, A.C. Moore, and Gate City Yarn in Greensboro, I’ve got my next few projects planned. I’ll post pics of each as I get them done.

My whirlwind tour of yarn shops this weekend did teach me that not all yarn is cheap. Although the Banana Berry yarn I used for my scarf only cost $2.37 a skein at Walmart, I don’t think I saw any yarn for less than $10 a skein at Knit Picky in Winston-Salem. Gate City Yarn had some unbelievably gorgeous silk yarn that was $56 a skein. But we’re talking great yarn like cotton, linen, alpaca, wool, bamboo, and, of course, that lovely silk. Handspun, hand-dyed, handpainted. Definitely worth the premium price. And definitely out of my league right now.

________________________________________________________________

Do you knit? What was your first project? What are you working on now? Post in the comments below. I’d love to hear from you, or even see pictures of your projects.

Getting in Tune with my Ukulele

I had a good day yesterday. The day before, too, and it had a lot to do with this little gadget:

A ukulele chromatic tuner

You can call it an auto-tuner, a chromatic tuner, or a headstock tuner. I call it a godsend!

For the uninitiated, that’s a ukulele auto-tuner. Also known as a chromatic tuner or a headstock tuner or possibly a few other names. I’m pretty new to this stuff myself. One thing I do know is that it’s a lifesaver if, like me, you’re completely hopeless at tuning a stringed instrument by ear.

See, Chad got me a ukulele for Christmas because I’d seen one on our anniversary trip in October and mentioned that I wanted one. He’s pretty awesome that way. He also got me a “teach yourself ukulele” book, and I diligently sat down on day one and started working through it.

Step one, after learning the parts of the uke, was to get the thing in tune. As I know from trying to learn the guitar twenty-some-odd years ago, I suck at that. I can’t tell if two notes are different when I play them together, and I can’t remember what the first one sounded like by the time the second one’s done if I play them separately. So it came as no surprise when my friend Dan told me that my uke was out of tune when he was at our house the other night.

I’ll admit that I’d been getting a little frustrated because I knew my uke didn’t sound right. I knew it was out of tune. But for the life of me, I couldn’t get it right. I told Dan that, and he suggested I pick up an autotuner.

So I did.

An autotuner — or, at least, the one I got — works by sensing the vibrations in the instument when you play it. Which makes sense when you stop to consider that all sound is just vibrations. Anyway, you clip the autotuner to the head of your ukulele (or guitar, or whatever instrument you’re playing, provided, I assume, it has strings). Pluck a string, and the tuner flashes up the nearest note that the string is tuned to. If the string’s in tune for that note, the background on the tuner turns green*. Otherwise, the background turns red* and the speedometer-like graph lets you know how sharp or flat you are. Then it’s a simple matter of twisting the string’s tuning knob until the pointer is in the middle of the graph and the background turns green.

Three images showing a chromatic tuner that's one, with an out-of-tune A string, and with the A string in tune

How sweet is that?! If I’d had one of these twenty years ago, I might have done more than butcher “Desperado” for a few weeks before setting my dad’s old guitar aside.

The guy at Guitar Center warned me that nylon strings like to stretch and I’d have to keep getting them back in tune until they eventually hit a sweet spot and stayed in tune. So now my ukulele practice sessions start with clipping my tuner onto my uke and checking to see if anything’s out of tune. (Usually the A string, which on my uke apparently has a deep-seated terror of staying in tune, because it can’t manage it for more that a few minutes at a time.) And, because I’m a geek and a chromatic tuner is a nifty gadget, my practice sessions usually wrap up with checking to see if my uke’s still in tune.

It’s a simple thing, but it’s made playing a lot more fun. I look forward to it and was actually a bit disappointed when I checked my schedule for today and saw I hadn’t scheduled any time for uke practice. I might try to sneak in a half hour or so tonight, time permitting.

Oh, and for the curious, I got Chad some drums for Christmas. A set of Irish bodhráns. Who knows? Maybe we’ll start a band.

 

*You’ll have to trust me that the background turns red or green, depending on whether the string is in tune. My camera refuses to acknowledge it, but it’s true. Apologies to the pics-or-it-didn’t-happen crowd.

By Popular Demand: The Flying Cow!

Chad got me lots of great gifts for Christmas this year, including a fountain pen display case, an F nib for my Pelikan M205, a Franklin-Christoph pen holder/journal cover, a ukelele, and a flying cow.

Yes, a flying cow.

When I posted a picture of my Christmas goodies to Twitter, someone asked what the black and white thing in the photo was. I replied that it was a flying cow, which immediately prompted calls from other folks that they wanted to see video of him flying. So, without further ado, I give you The Flying Christmas Cow!

I hope you had as wonderful a holiday as I did, and I hope the new year brings you nothing but fun and happiness.

Happy Holidays!

Reflections on my First #NaNoWriMo

An old-style black alarm clock

Time's up!

It’s December 1st, which means that midnight last night was pencils down and check your word count for hundreds of thousands of writers participating in NaNoWriMo. For once, I was one of them.

I didn’t manage to write 50,000 words, but I did knock out a little over 21,000. And now I’m going to throw them all away.

Okay, I’m not actually going to toss my notebook in the garbage can or run the pages through a shredder. But I am going to start my story over again. This is not a bad thing.

I could blame not getting to 50k on November being an even busier month than normal for me. After all, I did have my usual MACE gaming convention, ARFP charity book sale setup, and two yummy, fun Thanksgiving dinners. I also had a couple of follow-up doctors appointments, sick kitties, and the unexpected stress of having to get a new $5500 furnace and heatpump.

But even before all that I was struggling with the story. I felt like it was boring. That it dragged. The characters didn’t seem believable to me. Even as the writer, I had a hard time buying that the female main character wouldn’t try to escape at least once after being captured — magical bonding or not. At one point I thought I needed to start the story earlier, with the death of the male main character’s wife. Then I thought I needed to change the female main character to a gypsy instead of a river nymph. I wasn’t willing to give up on the story, but I knew something was wrong.

A couple of days before the end of NaNoWriMo, it hit me. Jump ahead in the story. Not a day, not a week. Fifteen years. Skip the boring bits and get to the good stuff now. And all the problems that were supposed to plague the characters over those first fifteen years? Hit the characters with them all at once. Boom boom boom. Don’t even give them time to breathe.

So those 21,000 words I wrote for NaNoWriMo are getting tossed aside.

Writing them wasn’t a waste of time, though. Far from it. For one thing, I know my characters better now. I don’t think I’d be able to say that if I hadn’t written those 21k. They’re backstory, and some of it I’ll work into the story later on. Some of it’s important. It’s just not important enough to drag a reader through for a hundred pages or so.

Then again, maybe I’ll get a few dozen pages into this new version and realize that the real starting point for the story is somewhere in that 21k. If so, I can always open that notebook again and pick up where I left off. Either way, it doesn’t matter, as long as I keep writing until the book is done. For me, that was the whole point of NaNoWriMo. Not writing 50,000 words by November 30th, but keeping going once the clock ticked over to December 1st.

And continuing to write until I reach “The End”.

_______________________________________________________________

Did you do NaNoWriMo this year? If so, how did it go? Did you hit that magical 50,000 word mark? Have any epiphanies about your story? And are you keeping going now that NaNoWriMo is over? Post in the comments — I’d love to hear!

Comments are moderated to keep spammers at bay. If you haven’t commented here before, it might take a while for your comment to show up.

The Other Thing I Wanted to Say

A Chrysler Sebring flipped on its roof with one wheel missing

I still get chills when I look at this.

I had the post-lumpectomy follow-up with my surgeon this morning. He gave me a clean bill of health, told me that my papilloma was fibrocystic changes, and assured me that not only was it not cancerous, but that it doesn’t increase my risk for breast cancer in the future.

“Just make sure you’re religious about getting your annual mammogram,” he said. As I’m sure you could tell from my last blog post, he’s preaching to the choir there.

The first thing he said, though, when he walked into the exam room was, “So, do you feel better now that it’s all over?” He knew how scared I’d been, not just about the surgery or the possibility of breast cancer, but about going under general anesthesia.

Do I feel better? Yes, I do.

It’s weird, but in a way I’m glad all this happened. Not that having a cancer scare is fun, but it’s amazing how it changes your perspective, your attitude toward life and the people around you.

Most people are surprised when they find out I write horror and dark fantasy fiction. “But you’re so sweet!” they say. “You look too nice to write horror.”

But horror isn’t about gore or violence or torture. It’s about fear. And fear is something I understand. I’ve been afraid of so many things for so much of my life. Things everyone’s afraid of, like spiders, heights, and flying. Things most people aren’t afraid of, like crossing bridges, going to the doctor, or getting lost at sea. Things most people don’t even think about, like going to sleep. Riptides. My house burning down. Carbon monoxide poisoning. Going through tunnels. Going off a cliff in the mountains. The water heater exploding during the night (it’s directly under our bedroom, directly under our bed).

For years I’ve mined that fear for stories. And I’ve written some great stories because of it, because my mind naturally goes to the worst, most terrifying thing that could happen.

But at the same time I’ve passed on doing a lot of things I probably would have enjoyed, simply because I was afraid. I’m not what you’d call a risk-taker. I love life — love being alive — too much to risk losing a second of it. “Is this really worth not being here tomorrow?” I’d ask myself. And the answer was always no.

When the doctors found the microcalcifications during my mammogram and started saying words like “biopsy”, “abnormal papilloma”, and “lumpectomy”, I thought of the song “Live Like You Were Dying” by Tim McGraw.

 

A lot of the first verse mirrored my own situation. I’m in my early forties. Since my family tends to live — and be very active — well into their eighties, by all rights I should have a good forty or fifty years ahead of me. And when I got the mammogram results, you’d better believe that stopped me on a dime, had me thinking about the surgery, about what I’d do if it was, in fact, cancer and had spread too far.

I thought about what Isaac Asimov said when asked what he’d do if he only had six months to live. “Type faster.”

And I thought about a small, framed poster my friend Sharon had on her wall when I first met her that said one of the keys to beating cancer was to make plans for things you wanted to do in a year, two years, five years — and believe you’ll be there to do them.

My wedding anniversary was three days before my lumpectomy. Chad and I had planned a trip to Southport, NC, that weekend to celebrate. When I asked the doctors about it, they all said, “Go! Take the trip. Enjoy yourself. Don’t even think about the surgery while you’re there.”

I wanted to cancel the trip, to curl up in a corner and hide. But I kept thinking about that Tim McGraw song, about Asimov’s attitude toward death, and about that poster on Sharon’s wall. “I should do this,” I told myself. “Because who knows if I’ll get another chance.”

Even though everything turned out fine, that’s been my attitude since then. I should do things now, because who knows if I’ll get another chance. I don’t know what happens after we die. I don’t know if we have any consciousness at all. But I know that up until the moment I go, I want to experience as many things as I can. If there is an afterlife, I want a million memories to keep me company while I’m there.

Now, I’m not going to go skydiving or Rocky Mountain climbing. Not because I’m scared, but because I have no interest in falling several thousand feet through the air, with or without a parachute. And I’m simply too damned lazy to put in the hard work and effort to climb a mountain (although I’d love to go indoor rock wall climbing). But I might ride a mechanical bull sometime, because that sounds fun. Or walk across the bridge at Grandfather Mountain. Or even fly in a plane again.

I’d like to learn to surf and play the ukelele and the saxophone. I want to learn to drive race cars, and make my own paper, and I want to travel everywhere.

And I want to write. More than ever before, I want to write. In fact, that’s the first thing I said when I woke up after surgery. “I want to write.” The nurses kept offering me crackers and water and painkillers, but all I really wanted was pen and paper. (My nurses were awesome, by the way. The whole surgical team was.)

The day before my surgery, about five minutes after we left the hotel on our way back from Southport, Chad and I saw a bunch of stuff scattered across the road. At first I thought it was a bag of garbage that had fallen off a truck and gotten strewn about by traffic. Then I saw the car, flipped over on its windshield, the tires still spinning.

Chad pulled over, and as we ran across the road to help I remember thinking, “There’s no way anyone could survive that. It’s not just on the roof — it’s on the windshield. I don’t want to see a dead body. Not the day before I go in for surgery.”

By the time we got there, both people in the car had made it out on their own. The passenger was holding the driver close, telling her over and over, “You’re alright. You’re alright.”

The only injury either of them had was the cut the driver had gotten on her knee, probably while crawling out of the car.

I’m still awed thinking about that accident, remembering how destroyed that car looked and yet how they both walked away. If it taught me anything, it was to stop looking at the world and seeing all the ways I could die. To start looking at it and seeing all the ways I could live instead.

I don’t know how long this new attitude of mine will last. This isn’t the first time I’ve had an epiphany, and I’m sure it won’t be the last. But I’ll hold onto this newfound bravery as long as I can, live as many new experiences as I can, and, to paraphrase Asimov, write faster.

For the curious, the car was a Chrysler Sebring. And you damn well better believe I’m looking at one of those when I decide to buy a new car!

It’s Breast Cancer Awareness Month, so I had a Lumpectomy

A self-adhesive bandage partially opened

They gave me a Bugs Bunny bandage after the needle biopsy

When I met my friend Sharon about fifteen years ago, she was fighting breast cancer. She was one of the strongest, smartest, most amazing women I’d ever met. And she still is.

I’ve thought about that a lot over the past few weeks, about how Sharon had breast cancer but she’s still with us today. I had to keep reminding myself of that because after my mammogram last month, I didn’t get a letter in the mail that everything was normal. I got a phone call that they wanted more images.

See, they’d spotted something in my left breast that hadn’t been there the year before, a cluster of microcalcifications about the size of my pinky fingernail (3-6 mm). They took more images. They did a needle biopsy. They told me I had an intraductal papilloma.

Intraductal papillomas are fairly common, and in more than 90% of cases they turn out to be nothing. A lot of times the doctors simply do a follow-up mammogram in six months to see how things look. In my case, the needle biopsy came back abnormal-not cancerous, which is a good thing. It means they didn’t find any cancer cells. And there was only one papilloma, which was a good sign — as long as it was non-cancerous, it wouldn’t even raise my risk of having breast cancer in the future.

But it was shaped like an arm from the elbow up with the fingers on the hand splayed. Because of that, the doctors wanted to excise the papilloma and biopsy the entire thing so they could make sure there weren’t any cancer cells hiding out between those “fingers”.

My philosophy on breast cancer is simple: I’d rather be alive without breasts than dead with them. Of course, when I told the surgeon that he said, “That’s a conversation for a different patient. That’s not a conversation for you.” Excising and testing the papilloma was simply an abundance of caution. So I had the lumpectomy on Monday. I got the pathology results yesterday. All negative. No sign of cancer at all.

Feel free to join me in my happy dance. :-)

When I sat down to write this blog post, to let everyone know what’s been going on and that I’m fine, I thought about what I wanted to say most to the folks out there. And I came up with this:

If you’re a woman over forty and you haven’t been getting regular mammograms, call your doctor and schedule one. Right now. Don’t wait. Don’t put it off until tomorrow, or next week, or after the holidays. Just do it. Now. Guys, nag the women in your lives until they do.

If you’ve got a family history of breast cancer, don’t wait until you’re forty to talk to your doctor about mammograms. Talk to him now. Don’t wait until you feel a lump, and don’t expect you or your doctor to find everything during a breast exam. I had my annual gynecological exam the same day as my mammogram. My doctor didn’t feel any lumps or bumps when he checked my breasts. My surgeon told me that with where my papilloma was and as small as it was, there was no way anyone could feel it. They only found it because the radiologist spotted those calcifications on my mammogram.

For the record, I don’t have a family history of breast cancer. My only risk factor is that I’ve never had kids. I don’t drink. I don’t smoke. I eat a low-fat, low-sugar, high-fiber diet. I don’t even drink caffeine. I almost never eat red meat. I’m not overweight. I exercise at least a half hour a day almost every day. I’m only 41 years old. Most of my relatives live to their eighties despite a lifetime of smoking, drinking, and eating a diet that would make a cardiologist shudder. Heck, my grandfather on my dad’s side worked around asbestos most of his adult life and died in his eighties because, as my dad put it, he was old. Not from cancer.

But I’ll be getting a mammogram every year now, just in case. Because even though this wasn’t cancer, it could have been. And if it ever is, I want to catch it as early as I can.

So if you’ve been putting off getting a mammogram, call your doctor. Now. Mammograms don’t hurt, no matter what sitcoms try to tell you. Needle biopsies do hurt, but honestly dental work is worse. The wire localization for my surgery was no worse than getting a shot, and the lumpectomy itself? I slept through it. ;-)

As for my recovery from surgery, I’m doing fine. I haven’t needed any pain meds since leaving the surgical center — and the only reason I took them there was to make sure I wouldn’t have a bad reaction. I had my surgery Monday afternoon, and I’ve been up and about like normal since about 6 o’clock that night. Most of the time I forget I even had surgery until I look down and see the bandage again. (And before you ask, no, I do not have a dent in my breast. It looks just the same as it always did, except I’m sure I’ll have a small scar after the bandages come off.)

Oh, and in case you’re curious how long all this took, I had the initial mammogram on September 22. They did the lumpectomy October 17 (three days after my wedding anniversary). And yesterday they told me I’m fine. :-)

The Writing Don’ts

A stop sign by a treeline road

Stop! In the name of good writing...

During his “Redline Your Writing” talk at the 2011 Write-Brained Network Writing Workshop, David L. Robbins gave attendees his list of “Don’ts” — things to avoid to make your stories their best.

1. Don’t switch POV in the middle of a scene.
I mentioned this one in my post “The Importance of POV”, but it bears repeating. Switching POV in the middle of a scene confuses readers, weakens the POV, and cuts the reader’s attachment to the character — and therefore the story — in half. It’s okay to have multiple POVs in a novel or even a short story. Just limit it to one per scene.

2. Don’t treat the POV character as separate from his body.
For example, don’t say, “He could feel his hands shake.” They’re his hands, so obviously he can feel them shake. Saying it is redundant and makes your writing flabby. And flabby writing is weak. Instead, simply say, “His hands shook.” Not only does it avoid stating the obvious, but you end up with a stronger verb, too.

Another example: “He knew his brothers would leave him.” He’s thinking it, the story is in his POV, so you don’t need to tell us he knew it. Change it to “His brothers would leave him.”

And one more: “He gave his captain a sardonic smile” would be stronger as “He smiled at his captain.”

3. Don’t tell instead of showing.
If you’ve been writing for any length of time, you’ve heard this one before. If you keep writing, odds are you’ll hear it again.

4. Don’t have physical redundancies.
Like treating the POV character as separate from his body, this falls under stating the obvious. For example, “He looked up at the stars.” As David put it, unless you’re in a space station, the stars are always above you, so you can lose the “up” and simply write, “He looked at the stars.” David also pointed out that you can trim a lot of (unnecessary) word count simply by eliminating physical redundancies like these.

Another example: “She picked up the cup and took a sip of coffee.” Obviously you have to pick up the cup before you can drink out of it, so you can cut that and simply write, “She took a sip of coffee.” (Show of hands, how many of us have been guilty of that one? Yeah, my hand is up.)

5.Don’t use a reflective surface so you can describe what a character looks like.
I think this falls under the category of not needing to describe a character’s appearance (or a place, or a building, or…) at all. Still, David said it’s okay when someone, including the character himself, observes something about a character, as long as you show these things and make them contextual. I’d go a step further and say unless it’s important to the events of the story, don’t waste the word count on it.

6. Don’t rely on asterisk scene changes.
Okay, I have no idea what this means. Maybe I’ll see if I can convince David to do a guest post about it sometime. I’d like to know so I can make sure I’m not doing that.

7. Don’t rush to tell the reader everything about a character.
I’ve read a lot of stories by newer writers where the first several pages are bogged down with facts, figures, and character backstory the writer felt I needed to know before he could get on with the story itself. Oh, is it tough to push through! I agree with David’s advice on this: Let it come out naturally in the course of the story.

David used the first line of Dan Brown’s The DaVinci Code as an example. “The international banker ran across the street.” At that point in the scene, David asked, to whom, exactly, is the character an international banker? If we need to know that the character is an international banker, that can come out much more vividly later when he’s doing something banking related. But at this point, the important thing is that he’s running across the street. Keep the focus on that, not on something the reader doesn’t need to know yet.

8. Don’t kill characters just to end a story.
Death is not a resolution. I’d take it a step further and say don’t kill characters just to kill them — anywhere in a story. It’s one thing if the events of the story naturally lead to a character dying. It’s something else entirely if a character dies when he doesn’t have to because you thought it would be shocking, or poignant, or a clever twist, or because you couldn’t figure out any other way to end the story. Readers don’t like literary murders. You lose their trust, and they stop letting themselves get emotionally invested in the rest of the characters in the story because they don’t that you won’t murder them, too. And if there’s anything I learned from David’s panel, it’s the importance of getting your readers emotionally invested in your characters.

That wraps up things on David’s “Redline Your Writing” panel. Next I’ll move on to the “First-Page Pit Stop” clinic, where David was joined by author Tiffany Trent as they critiqued first pages from attendees and members of the Write-Brained Network forum.

The Telling is Separate from the Story

Blueprint of a ship

Like this, but with words

In my last post I covered what David L. Robbins taught us about the first half of being a storyteller — the story — during his “Redline your Writing” talk at the 2011 Write-Brained Network Writing Workshop. Today we’re going to focus on what David said about the second half — how you tell the story.

If “the firetrucks have to be going to YOUR house” was David’s mantra about story, for the “telling” part of the equation it was “clarity is paramount”. When you write a story, he said, your only task is to give the reader the blueprint to build the story in his head.

Let me repeat that, because it’s important: As a storyteller, your ONLY task is to give the reader the blueprint to build the story in his head.

To do that effectively, avoid flaccid language that has too many modifiers and physical redundancies. Pick images and modifiers carefully and with an eye to building the image in the reader’s head. Remember that sometimes less is more. The simpler your language, the more the poetry comes out. That doesn’t mean you have to emulate Hemingway. Just choose carefully.

David used the following example to illustrate this:

The clock struck seven, and the cock crowed.

I myself am guilty of that kind of construction. But David warned that a sentence like that diffuses its power. Which I take to mean that since it’s about two different things, it’s hard for the reader to picture them both at the same time. As readers, we digest a whole sentence at once. We don’t stop until we reach a period. So in this case, one image — probably the clock — is going to get glossed over as the reader moves on to the next part.

If the second clause was something about the clock itself that would help build the image in the reader’s mind, the compound sentence would be fine. But these are two separate ideas, so David advised letting them stand individually:

The clock struck seven. The cock crowed.

Because the reader now knows what each sentence is about, it’s more powerful.

On a larger scale, David said to start the action of the story as close to the complicating event as possible, but remember that you still need a character your readers care about first. The story should get complicated a third of the way in, more complicated two-thirds in, and by 20 pages from the end the reader shouldn’t know what’s going to happen.

Barge into a scene; stumble out of it. Start a scene at an ending, something that makes the reader want to know what’s next. And avoid the Don’ts.

What are the Don’ts? Ah, well, we’ll cover that next time. ;-)

The Firetrucks Have to Be Going to Your House

A red firetruck parked on the street

Please, please, PLEASE don't be going to my house!

Wow, has it really been that long since my last blog post? Sorry about that. When I went to the doctor for my annual checkup, they thought an extended poking and prodding would be great fun this year. It’s been a bit distracting. Still, even though they aren’t quite done with me yet, that’s no reason to miss deadlines, so let’s get back to it.

In his “Redline your Writing” panel at the 2011 Write-Brained Network Writing Workshop, David L. Robbins told us there are two parts of storytelling: story and telling. Seems obvious, doesn’t it? Of course, there’s more to it than that. So today we’re going to concentrate on what David taught us about story.

If you’re like me, I’m sure you’ve had the importance of a strong opening scene drilled into you. That’s what I thought David was going for when he told all of us at the workshop to imagine a scene describing a bunch of firetrucks tearing down the street, lights and sirens going, cars pulling off to the side to let them pass, people on the sidewalk craning their necks to watch and wondering out loud what’s going on. “Yeah, good strong opening,” I thought. “Starting in medias res, making the reader wonder what’s going to happen next.”

But then David said, “Now imagine that as one of the firetrucks slows a bit to round the corner, one of the firefighters, who is a friend of yours, spots you in the crowd and yells to you, ‘We’re going to your house!’”

If you’re as paranoid about your house burning down as I am, that scene just got eminently more interesting. As curious and concerned as any of us are when we see emergency vehicles racing down the road, it matters a whole lot more when it’s our house that’s on fire. David repeated that mantra to us throughout the workshop: the firetrucks have to be going to YOUR house.

As we learned in my last post, the POV character represents the reader and creates an emotional bond to the story. Needing the firetrucks to go to your house is why a strong POV is important. As David explained, every action in a story must be taken by or affect a character we care about. Which is why you’re never wasting time in a book by making readers care about a character — and then beat the crap out of the character, because then you’re beating up the reader, and the reader will care about that.

At the same time, David cautioned against creating complications for a character the reader doesn’t care about yet. That goes for villians, too. The reader has to hate the villian first for the complications to matter.

A writing book I read recently put it this way: people read to worry. They might pick up a book to escape from life for a while or to be entertained, but they keep reading because they worry. They worry about the characters, about whether they’ll get what they want, about whether everything will work out okay in the end. But how can we worry about people we don’t care about?

And how can we help but worry — and keep turning pages to make sure everything’s going to be alright — when we do?

Which takes us into the second part of storytelling: how you tell the story. I’ll let you know what David said about that in my next post.

The Importance of POV

In my last post about the 2011 Write-Brained Network Writing Workshop, I revealed David L. Robbins’ bombshell that “write what you know” is a lie. This time I’m going to share his advice about what he considers the most important thing to know about writing: POV.

In a story, David explained, the point-of-view character represents the reader. He exists to link the reader to the page, to give the reader an emotional bond to the story. The stronger the POV, the better. That, David said, is the key to JK Rowling’s success — the Harry Potter books are strongly rooted in Harry’s point of view. (David did ellicit some gasps from the audience when he said Rowling could be a better stylist. FWIW, I agree with him, although I’ve heard her writing gets better in the later books. I love the movies, though.)

Although it’s okay to have multiple POVs in a novel or even a short story, David advised against switching point-of-view in the middle of a scene. It weakens the POV, and the reader’s attachment is cut in half. Instead, separate the different POVs by scenes or chapters.

As for which POV to use in a story — third person limited, first person, etc — David didn’t endorse one in particular, but he did caution againt using an omniscient POV. It leaves the reader behind, so they no longer have that emotional bond to the character. And first person POV requires mastery as a writer. To write good first person stories, you have to be a great empath.

So my takeaway from that is that third person limited is probably the best way to go. Which normally would be great news for me, since that’s pretty much all I write. Except I recently decided to change one of my short stories to first person limited. Hmm….

Anyway, in my next post, I’ll tell you what David taught us about the two parts of storytelling — the story and how you tell it.