Tag Archives: Shane

Lessons from writing my memoir . . .

Five years ago I began writing a memoir about my experiences farming in Appalachian Ohio. My official start was September 1, as I recall, but I was gearing up at this time of year, in late August, when the common Midwestern wildflowers are blooming. Right now, you can see flowering together in fertile meadows and damp unkempt roadsides: purple ironweed, saffron goldenrod, yellow daisies, and, above it all, the airy mauve bursts of Joe Pye weed. Shade trees look dusty and faded; their heavy foliage sags, their branches storm-wracked. The other day, looking out my window at the parched lawn, I saw a spatter of yellow leaves twirling above the grass. It was elegiac. I know we’re supposed to love the back-to-school frenzy, but I don’t. And I’ve always hated the end of summer. I couldn’t help but reflect.

Years ago, an author of many books said to me during an interview, “It’s not that I’m talented or hard working, but I can sit there hour after hour. A lot of people can’t do it. They’re smart, talented but just can’t.” I learned to my relief that I could do that, sit there, usually five days a week though often six and sometimes seven. Longer breaks are dangerous: for each day away it takes a day to get back in—vacations can derail a book. My optimum keyboard stint seems to be three hours. If writing is going well, my brains are mush after three; if the writing is hard, I’ve suffered enough. I yearn to be a four-hour man, though. I treasure the memory of one inspired day when I put in eleven hours (I’ve since cut that chapter). I also discovered how much I enjoy solitude. And how, if I did have a whole day, I could pass it happily writing, reading, editing. Such productive bliss is addicting. The day passes in a blur. But, on a really hard day, three hours takes an eternity. Better to switch to editing.

Early on, about that first November, there came a day when I hit a problem I hadn’t faced and didn’t understand—now I see it was dramatizing a particular event, bringing it to life, when I had some memories but some gaps and too few images. I had a little meltdown. I thought I couldn’t write the book, and sent Kathy a despairing email, which she wisely ignored. Then, later in the winter, I ran to my desk each morning to write another chapter. So the average day during initial composition was pretty good. I learned that my page-production speed was about one sheet an hour. Three pages for three hours. Getting four pages a day was, and would be, heaven. But, as someone pointed out, if you faithfully write only a page a day, in a year you’ve piled up 365 pages—a book.

It took me a year and a half to finish, but my first manuscript draft was 500 pages. My goal had been 300; it took work to pare it down. Which reminds me of a rule of thumb I learned in book publishing for estimating the length of a book from its typed or printed-out manuscript pages: Take the number of printed pages and multiply them by .887. So 300 pages x .887 = a 263-page book, which is a nice, optimum-upper length for most publishers. This formula is based on a book with a 6 x 9 size and typical design format.

Five years. If I had a manuscript three and a half years ago, what gives? Well, I’ve rewritten, polished, and cut every sentence, paragraph, and passage many times. And now I’m on my fourth whole-book rewrite. Not to be defensive, but I like Annie Dillard’s rule of thumb: for someone not a genius, it takes two to ten years to write a publishable book. That’s an average of six years, which is what I’m on track for, with luck. I know people who have done it in much less, but if they write more than one book I suspect Dillard’s average will apply. A screenwriter I know said he was almost ruined for life by his first play, which poured out of him right after he got his MFA; it won an award and was produced in London; it’s never gone that way again. And a full-time writer of popular young adult novels told me that after she’d been writing for years a “gift” book just flowed out of her. She said it would have destroyed her if it had been her first book because the others aren’t ever that easy.

I could have shaved years off my process if I only knew then what I know now. I was fifty when I started, and although I’d been an “award-winning journalist,” as they say, and a magazine writer, gardening columnist, occasional essayist, book reviewer, and book publisher, I hadn’t written a book. It’s true that the only thing that teaches you how to write a book is to write one. Reading helps, but mostly the reading you do while you are writing. On the plus side, I had desire, a pretty good story, notes and ideas, and a strong voice. But I didn’t fully understand dramatic structures, especially classical three-act structure. Trying to figure out how to cut my monster by 200 pages, I read Philip Gerard’s useful Writing a Book that Makes a Difference, which indicates that after your second-act climax, a dramatic narrative should wrap up quickly because its audience is dying to find out what happens in the final act.

I happened to watch the 1953 western Shane that summer and saw it was a beautiful example of classical three-act structure. A mysterious stranger, Shane, played by Alan Ladd, gets hired by a sodbuster, and the bad guys, cattlemen, immediately show up to threaten them—first act climax. In the long second act, Shane befriends the sodbuster’s son and demonstrates his shooting prowess, and when the thugs kill a hapless farmer Shane pummels the sodbuster to prevent his trying to seek revenge, then heads off to fight them himself—boom, big second act climax. In the short third act, Shane rides into town for the showdown, kills the hired gunslinger, played with reptilian menance by Jack Palance, is wounded himself and fades into the hills, to die or to rise again. The climaxes flow from each other, and with a certain rhythm.

I saw that after my second act climax—I get badly injured on the farm—essentially I started the story over again and took my sweet time getting to that third act resolution. As if Shane, instead of going after the gunslinger who’d just murdered, had dawdled and diddled around on the farm, perfecting his plowing.

My next major lesson was realizing that I didn’t grasp the importance and the power of dramatized presentation—scenes—to convey experience. Like many a rookie writer, I leaned too hard on summary—and, let me tell you, scenes are infinitely more powerful, and much harder to write. Yep, show don’t tell. Also I wasn’t driving enough narrative threads through the entire book; I did that with the development of the protagonist, me, and with the book’s villain, but not with many other themes. I tended to write each chapter almost as a stand-alone essay. In Chapter Ten, say, I’d introduce a character and dispose of him in a big event, when the reader should have met him in Chapter Two. It’s amazing how readers love you for having them remember what you told them. They’ve seen a character in action, made their own judgment about him, and then, hey, here he is again! Like life. But now I sometimes feel I’m planting little timed-release land mines for readers, and that’s difficult when the first mentions feel thin, as if they’re just being done to set up a payoff. I sit and stare, trying to figure out what’s interesting in a first meeting or a minor event and where it might fit just so in the narrative chronology. Finally, if I can’t solve the puzzle, the subconscious will pitch in to help—after I’ve sufficiently suffered.

In addition to nailing down the balance between scene and summary, the memoirist must reflect. This has been another late and more subtle tweak, this differentiating between the writer now, at his desk, who’s telling the story and sometimes musing on it, versus the character in the story—the narrator’s earlier self—who doesn’t know what’s going to happen or even, sometimes, what is happening. Not wanting to kill narrative drama, I had too little reflection. Memoirs vary widely in their balance among scene, summary, and reflection, but especially in the amount and the nature of the writer’s reflecting upon meaning.

Five years. I tell myself that I must learn to love process because, like life, writing a book is process. I’d never have believed when I started that I could rework for four or five years what took me a year and a half to write. “That’s the fun part,” a writer said, implying ease. It’s true that the raw material is mostly now available, but I’ve found the last two rewrites hard work. Seemingly harder than initial creation—my ignorance was indeed bliss—but it’s getting difficult to remember. I’m more aware of narrative techniques, and more in command of them, but more challenged. Such strong, humble tools still twist in my clumsy hands. I now fully subscribe to the truism that writing is rewriting, though I think an experienced book writer could have done it in half the time or less, in three drafts.

But oh, my sentences! After two years they were better, more fluent and varied. Yet I’ve discovered that I desire them lyrical, every one poetic, and sustaining lyricism has been impossible for me in this long narrative. And to strain for it risks purple prose. So I feel at some level a plodding failure. Sometimes I go to an admired book just to see how plain most of the sentences are—not what I remembered at all—but then I notice their rhythm, their flow. Thankfully I’ve also learned how much I love making, and remaking, sentences. How much difference one or two sentences more, or less, can make in a paragraph. How you see that a passage wasn’t as clunky as you’d feared, but that another wasn’t as soaring. How in time you can hardly tell inspiration apart from perseverance.

15 Comments

Filed under braids, threads, design, Dillard—Saint Annie, discovery, editing, film/photography, flow, memoir, MY LIFE, scene, structure, syntax, working method