Category Archives: Writing

Show Your Work: Time Travel Story

I’m trying to write a novel. Again.

Writing fiction is scary work for me. It’s hard. And I don’t think I’m very good at it. Plus there’s practically zero financial incentive.

But nobody writes books to make money.

You have to do it because you love it. Because you have a good idea inside that you can’t help but share with the world. It helps if the process of writing you occasionally find enjoyable.

I don’t know if I have a good idea or not, but it’s inside me and wants to get out. Every now and then there are times when the writing process is amazing. But especially with fiction there are long stretches when the words are wooden, the sentences flat and I wonder why I’m wasting perfectly good time that I could be doing nearly anything else.

I’ve started and stopped this latest novel a few times now. I’m trying again.

The motivation this time is that I realized the story I’m wanting to tell is a story I’d like to read to my children. I read to my kids nearly every day. We read lots of different books and now that we’re reading middle grade novels and not rhyming picture books, I really enjoy it. I love reading a book that captures my kids attention. I love reading a book that has wonderful words, spectacular phrasing and dialogue that makes me try to be a performer and not a mere reader.

I wonder if I can write that kind of book.

I probably can’t.

I’ve written three novels and have never been able to get them past a second draft to a point where I’d say they’re finished. I have a hard time following through.

It’s not that I’m lacking confidence, it’s that I’m trying to be realistic.

Yet I have this idea. It keeps working on me, spinning in the back of my head, trying to become something. It’s about a reluctant time traveler.

Festival of Faith & Writing 2014

This past week I attended the Festival of Faith and Writing at Calvin College in Grand Rapids, Mich. It’s a gathering of writers and readers interested in faith.

I first heard about this event when I was in college, but it’s never been practical to attend. It’s also held every other year, so I would tend to forget about it or only remember during off years.

This year I’d been looking for an event to attend and this seemed perfect. I’ve never been to a conference in my professional career that wasn’t in some way promotional. I was always doing work. It was never a retreat or a chance to recharge, it always involved promoting something.

This time around I was there as a writer and a reader, looking to hear from other authors and not do anything promotional.

Which makes for a glorious event. Continue reading Festival of Faith & Writing 2014

Learning How to Write Fiction Again: Point of View

Yesterday I hinted that I’ve dusted off one of my old novels for [some more] editing. I don’t do a lot of fiction writing, but I do a lot of fiction reading, and it’s helping me see what kind of edits I need to make. Sometimes the edits I need to make are painfully basic. It’s like I need an re-introduction to the elements of fiction writing.

Point of view is one of the big issues I’m dealing with.

It’s pretty important because it determines how the reader views things and decides what you’re allowed to see and what you’re allowed to know. There’s the basic first person (I say this, I do that, I jump up and get down) vs. third person (he says this, he does that, look at him jump up and get down) decision, which I managed to do OK. Yay for me.

But when you choose third person, you’ve got three options: Omniscient (you know everything), limited omniscient (you know what one character thinks) and objective (you only know what you can see). There are pros and cons to each, but you’ve got to pick one and stick with it (duh).

My story basically went with omniscient. But then I mostly followed a single character, making it feel like limited omniscient and confusing people whenever I “head jumped” to a different character. Oops.

Nathan Bransford has a good quick summary of omniscient vs. limited omniscient, and sadly it’s something I need to re-familiarize myself with.

I feel like I need a fiction primer that does more than my elementary school book on writing and defines things, but goes that step further to tell me the pros and cons, the tips on how to do it better, the pitfalls to avoid. I suppose that’s called being a writer and working on this stuff more than once a year.

The Joy of Author Readings

Last week I went to two separate author readings: Addie Zierman read from her beautiful spiritual memoir, When We Were On Fire, on Tuesday evening at Northwestern University; and Rainbow Rowell read a short bit from her 1980s teen love story, Eleanor & Park, on Wednesday at the Harriet Island Pavilion.

I love hearing from authors. It’s great to hear an author’s work in their own voice. I still remember hearing Wendell Berry read from Jayber Crow during college and just being blown away. That was a book  I had to read.

Author readings are also great events because they’re free. It’s not like you can get that deal with your favorite band. I’m not big on autographs and needing to meet authors, but that can be fun as well. And if you’re looking to meet women, apparently author events are the place to go. Maybe I’m just reading the wrong books, but the gender balance was way off. That makes sense for a teen love story, but I felt a bit like the old skeezy guy (sticking around for an autograph would not have helped that issue either). Continue reading The Joy of Author Readings

Stories Can Heal

Classic LesOne of my favorite memories from my grandpa’s funeral is sitting around his kitchen with my cousins telling stories and jokes. That little kitchen filled up with people and laughter again, which my grandpa would have enjoyed. My grandpa was old and it was his time to go, but that act of storytelling helped to heal the wound of losing him.

I finished reading Tell Me a Story by Scott McClellan this week. It’s good stuff (you can read my review for more). Something Scott talks about in the book that I resonate with is the idea that telling stories can be healing.

I’m not a particularly good storyteller—that’s probably why I’m a writer. I like to edit and rework and figure out how best to tell a story. I work better in the written word than the spoken word. But I think part of what draws me to the word is telling stories. It’s self-indulgent, but one of the things I like to write is simply telling stories about my life. In some ways, I think that’s because there’s healing happening there. The telling of stories allows me to process, to figure things out, to think things through and find meaning or comfort or grace.

That’s probably why, in my moments of greatest distress, I turn to writing. I tell the story. Some of those stories aren’t meant to be told to anyone but myself, but still I tell them.

In adoption, I think this is why it’s important that we tell the stories. It’s easy to gloss over what could be uncomfortable details and avoid those stories. But by telling those adoption stories, we give voice to them, we shine a light on any “messy” details and we find a way to embrace them. A story gives us the narrative to do that. It gives us a voice and something to cling to when we’re confused or fearful.

That’s powerful. Continue reading Stories Can Heal

Using Scrivener to Write & Publish Books

When I wrote 137 Books in One Year: How to Fall in Love With Reading I tried a new writing software. I used to stick with Microsoft Word for everything. But I’ve been increasingly annoyed with it lately and I’ve experimented with some other options. I eventually landed on Scrivener and I’m not going back.

Scrivener is designed for writing book-length projects, whether it’s a novel, script, nonfiction or something else. It allows you to rearrange chunks of text as you go. You can switch to a corkboard view with each chunk of text on an index card with a title and summary. Then just move the cards around if you want. It makes organizing the structure of your book a whole lot easier.

You can also tag and index things like crazy, so for a novel you could note which chunks of text which characters appear in and easily find all those places.

You can also keep everything related to your project in one spot, whether it’s notes, research or drafts. When I’ve done books in Microsoft Word before I’ve always had a growing pile of supporting documents—an outline, a timeline, a list of characters, a list of things I need to tweak, etc. With Scrivener you can keep it all in the same spot. You can tag things and quickly view only what you need to.

If you’ve ever had to write a project of any length you’re probably starting to see the possibilities. And I’m just scratching the surface of Scrivener’s features.

But perhaps the best part of Scrivener is when you’re done writing. It allows you to export your work to whatever format you need in a process known as compiling. This is where it rocks. You can export to vastly different formats with completely different layouts and looks, all using the same source material.

So with 137 Books in One Year I spit out a CreateSpace-ready PDF for my 5×8 print version of the book, as well as a Kindle-ready ebook file that I could upload directly to Amazon. That would require two separate files in Microsoft Word, which would mean making any further changes in two places. Lame. Nevermind that setting up those kind of files in Word will make you want to punch someone. It’s not completely perfect in Scrivener and I’m still learning, but it’s light years better.

I originally heard about Scrivener from this post on how to create a book from idea to Kindle in 29 days, but since then I’ve seen other writers talking about it, including Jeff Goins and Michael Hyatt.

Say Hello to The Stephanies

It’s only the second day of Lexi’s summer vacation and she already needs a project to keep her from being bored. OK, I need her to have a project to keep her from being bored.

A while back we wrote the outline of a book together. I asked Lexi who she wanted the characters to be, what she wanted to happen and kind of made up the rest. She drew one picture and it got filed away for another day.

Today was that day.

The Stephanies
We pulled out The Stephanies and started work on our book. I’m the writer and Lexi is the illustrator (apparently on Saturday we’re going to switch roles for her Star Wars book). I had to explain how illustrating works, how you have sketch things and draw them and redraw them and draw them again to get it just right. I explained how she had to practice drawing each Stephanie so they looked the same in each scene. I also explained how this wouldn’t be a quick project that we’d finish up today—it’d take a while. (All of which would probably make me a horrible art teacher)

So I spent the afternoon writing and Lexi spent the afternoon drawing. I have most of the story, though the ending needs some work and it needs lots of polishing (my last children’s book was Mike, The Cat, written when I was a child). Lexi has a lot of good drawings, though I think we need to pick some new colors or figure out what’s wrong with the scanner (the girls should be wearing dresses that are highlighter pink and yellow).

So that’s your preview of The Stephanies. It’s going to be awesome. I’m hoping we can release it later this summer, probably as an ebook and maybe as a full-color, printed book (I’ve been wanting to experiment with that for a while).

What About Milo?
And why isn’t Milo involved in this little project? Mainly because I insisted the kids clean their rooms on the first day of summer vacation and then keep them clean. Lexi finished after an hour or so on the first day. Milo kept procrastinating, not doing it and somehow completely avoiding it. For two days. He finally finished the half hour job tonight, so maybe I’ll have to find a role for him tomorrow.

Maybe he can be our publicist.

Lessons from a Reader: What Happens Next?

One of the most disappointing things as a reader is getting completely engrossed in a story and then it ends. You were completely into the story and following the characters and the plot finally resolves itself and it was amazing.

But then it’s over.

The elation of reading such a thrilling story is now countered by the disappointment that it’s over. So one of the greatest things an author can do is slowly pull you back out of the engrossing world of the story.

Sometimes it doesn’t require much. But the longer your story, the more it’s necessary. My all-time favorite example is the Scouring of the Shire at the end of Lord of the Rings. After following Frodo for 900 pages of walking, ring whining and orc gutting, the story can’t just end. And Tolkien gives his readers one last adventure. You know the story is over, the tension that carried you through those 900 pages is over, but you still want more. And Tolkien delivers with one last hurrah.

Ashfall by Mike Mullin delivers a more common example. It took 400 pages to reunite Alex with his family after a volcano erupts in Yellowstone and the story could have ended there. But instead we get another 50 pages that wind the story down, giving us closure (and nicely leaving room for the sequel).

These closing scenes let us emotionally process the story. After the climax, you need things to wind down a bit, to know where these characters are going to go. It doesn’t have to be long, but one last glimpse of where they’re going is gold.

PS, an epilogue is a cheap and rushed way to do it. Especially if your epilogue leaps forward in time to conveniently tie off questions like who marries who (J.K. Rowling, I’m looking at you).

Lessons from a Reader: Show the Expertise

I’ve shared a few lessons from readers and it struck me that it would also be helpful to include some positive ideas. Complaining about every book I read makes me sound like quite the jackass.

One thing I love to see in books I read is expertise. When you can tell that somebody knows what they’re talking about, when they can describe something with such detail that they’ve clearly become an expert—that rocks. It doesn’t matter if they’re actually an expert or they’re just really good at faking it. However they do it, I love it.

One example is in Ashfall by Mike Mullin. And it happens several times throughout the book. I may not believe him about the weight of ash, but he shows his expertise in other areas. The main character, Alex, knows his taekwondo. He knows how to handle a bo staff and knows how to take down a much larger opponent. And it’s presented in a realistic, I-learned-in-a-safe-class type way. He’s horrified when he accidentally kills an opponent and compares striking someone in the face to hitting the punching bag. Not only does the writing describe these skills in a way only an expert could, but he works in those details in a realistic way that’s authentic to the character (Note: Don’t work in details just to show off your research).

Later Alex encounters Darla and she knows her way around the farm. When she skins a rabbit, jury rigs a toilet, or makes a homemade smoke house, it’s completely believable.

I remember another example from Open Heart by Frederick Buechner that I read an excerpt of in college. It so perfectly captured a high school classroom that years later I had to track down the book and read it. I first read that passage more than a decade ago and I still remember it. Expertise doesn’t necessarily have to be skills, it’s the experiences that make your writing completely believable.

I could read good expertise writing all day long. It doesn’t matter if the skill is accounting or unloading a truck, if you do it right it can be mesmerizing.