Wednesday, November 19, 2014
Like many of you, I'm deep into my NaNoWriMo manuscript. I've passed the 33,000 word point. Yay! If you want to find me on NaNo, click here.
When I say 33k words, you know that I mean absolutely horrible words, right? Like, toss 'em over the bridge kind of bad.
I used to worry about those horrible first drafts. I no longer worry. I plan my books with a loose outline and use index cards to keep me on track. If I'm inspired to change directions, I do.
Here's the thing. I don't worry about the crappy first drafts because I know they can be fixed. What I'm writing now will be like 50,000 words of detailed plot notes. It's when I work the story out in my head and bring the outline to fruition. Barely any dialogue, world description, etc.
But there's one fun thing that I do that I wanted to share with you. I amuse my future self.
You see, when I read through this for the first time (which will be weeks, maybe even months from now) I'll need a chuckle. I'll be convinced that I'm the worst writer ever, and how did I ever think I could shape that fuzzy idea into a full-length novel? (Note: the manuscript is never as bad as I think it will be)
So what do I do? I write notes to myself. Sometimes it'll be as simple as (dumb). Or sometimes I'll question myself (didn't I write this a few pages ago?). But sometimes my notes will make my future self smile. I might type (lame) or (is that the best you can do?) or (crappity crap crap). I might even type (this is where I felt like throwing my laptop at the wall. but i didn't. i kept going. now fix this mess)
This way I don't take myself too seriously. I'll remember that what I accomplished during the month of November was capture a story on the page. Nothing more. When revision time comes, I'll flesh out the characters, add dialogue, and ground the reader with sensory details.
First drafts are the toughest part for me, so right now I must focus on getting the story from my brain to the laptop. No looking back. And if I can make my future self smile in the process, I'm all good.
How about you, writers? Are you participating in NaNoWriMo? Do you have any tips you can share with the rest of us?
Wednesday, November 12, 2014
I'm a huge Nicholas Sparks fan, so I was excited to read The Longest Ride. Of course I learned some helpful writing lessons!
First, a little about The Longest Ride:
Ira Levinson is in trouble. Ninety-one years old and stranded and injured after a car crash, he struggles to retain consciousness until a blurry image materializes beside him: his beloved wife Ruth, who passed away nine years ago. Urging him to hang on, she forces him to remain alert by recounting the stories of their lifetime together--how they met, the precious paintings they collected together, the dark days of WWII and its effect on them and their families. Ira knows that Ruth can't possibly be in the car with him, but he clings to her words and his memories, reliving the sorrows and everyday joys that defined their marriage.
A few miles away, at a local bull-riding event, a Wake Forest College senior's life is about to change. Recovering from a recent break-up, Sophia Danko meets a young cowboy named Luke, who bears little resemblance to the privileged frat boys she has encountered at school. Through Luke, Sophia is introduced to a world in which the stakes of survival and success, ruin and reward--even life and death--loom large in everyday life. As she and Luke fall in love, Sophia finds herself imagining a future far removed from her plans--a future that Luke has the power to rewrite...if the secret he's keeping doesn't destroy it first.
Ira and Ruth. Sophia and Luke. Two couples who have little in common, and who are separated by years and experience. Yet their lives will converge with unexpected poignancy, reminding us all that even the most difficult decisions can yield extraordinary journeys.
Ok, and now for some writing lessons learned. Warning! If you haven't yet read The Longest Ride, and don't want to know any plot points, read no further:
- Open with detailed character information--the book opens with Ira's pov like this: I sometimes think to myself that I'm the last of my kind. He's an old man who's been in a car crash. He reflects on early lessons his dad had taught him, such as never count money in public, hold doors open for women and children, and always give a customer more than expected. These life lessons tell us a lot about the type of man who's been in a car crash. I immediately liked him.
- Remind the reader of the character's predicament--Ira is injured, cold and thirsty. He reminisces with his long-dead wife, recalling their love story. Every few paragraphs the author brings us back to the present, by injecting lines about Ira's pain, the falling snow, and the oncoming night.
- Reference a life-saving anecdote early--Ira likes to watch TheWeather Channel. He recalls a story where a man survived a crash for over 60 days by eating snow. This memory comes into play later in the book, but it makes sense because it was established early.
- Embed threads between two alternating stories--we have two parallel stories happening. Ira and Ruth. Sophia and Luke. I wondered how these two stories would connect, and paid attention to details that would finally bring them together. The author did a great job of keeping me curious, while also planting clues along the way.
- Stupid makes sense--if the character has to do something stupid, like ride an angry bull even though he doesn't want to, give him a moral reason to do it. Luke shouldn't ride bulls anymore (I won't spoil the story here) but he does it anyway. Why? Not for fame or accolades, but to help his mom.
- Eliminate short, choppy scenes--I actually got this tip from one of my beta readers for my own book. I had tied up the book with a few short scenes at the end. She suggested I pull what I needed from those scenes and write one significant scene. So I did. I was surprised by the amount of short, choppy scenes at the end of this book. It's still amazing, but that ending could've included one significant scene with the details from the short scenes.
What do you think of these writing lessons? Have you used any of them in your own fiction? Are you a Nicholas Sparks fan? Do you like stories with old/young points of view or parallel stories that merge at the end?
Wednesday, November 5, 2014
Welcome, Insecure Writer's Support Group! Not signed up with this amazing group yet? Quick! Remedy that and sign up here.
Side note: my ebook "The Boy Who Loved Fire" is free today! Clicky here to download a copy :)
Recently I was listening to a very successful person talking about failure and making mistakes. He suggested that people take this attitude: "I'm not a failure, I'm a learner."
This person had tried new things and failed. He'd tried some things and succeeded. His perspective was this: keep trying new things, even if you're scared. You will NOT fail, because even if things don't go your way, you've still learned something new. There's immeasurable value in that.
His statement really resonated with me. As a matter of fact, I'm about to do a whole lot of learning. I'm participating in NaNoWriMo again this year (my sixth!), but I'm trying something completely new. I'm using my beloved characters from my novel The Boy Who Loved Fire. Not a sequel, but more like a companion book. Plus I'm writing in dueling points of view. I've never done that before. Oh, and this will be more like a thriller. So yes, there will be plenty of failure...er...learning...going on.
I'm also studying ideas about releasing books as serials, podiobooks, and all kinds of fun stuff. One thing I've learned about this publishing business, especially indie publishing, is there are so many cool things to try.
What if something doesn't work out? I'll learn from it and move on to the next thing. And I won't consider it a failure...I'll consider it a learning experience.
Friends, what's your take on failure? Do you consider it a bad thing, or do you find value when things don't go the way you'd imagined? Are you afraid to try new things because of the fear of failure? Please share!