Ah yes, that loaded question most writers simultansously appreciate and dread. People are interested and curious about our work, yet we have no answers to give them. And if you're like me, no matter how much you hear that this "not knowing" stage of writing is typical, or that most writers go through it often, this is the point at which you panic. Because all of a sudden, you believe you have no story. You have no talent. You have no voice. You will probably not write anything ever again - and if you do, no one will read it. Because you have nothing to say. Hell, how can you have anything to say when you don't even know what you are writing about? You suck and now everyone knows. Way to go.
After all, isn't the first rule of writing to "know your story"? Or at least your purpose for writing the story? Absolutely without a doubt yes. I'm not a huge fan of intentionally obtuse writers who indulge in abstraction when I hold their book in my hands and ask "What is this about?" I don't want to hear that it is about love or death or immorality. As overaeching themes, those are fine. But where is the meaning and what is the substance of a book? That is the question that I, the reader, want answered and it is the question that I, the writer, want to be able to answer. Even so, as I think about the "know your story" rule, I can't help but think about the "shitty first (and second, and third) draft" rule, too. I think that one is pretty self-explanatory.Of course I always want to know what I am writing about when I sit down at my computer, at my scheduled writing time, for my pre-planned number of hours devoted to a specific part of a specific piece. During this third semester of my MFA, my monthly submissions to my mentor include at least twenty pages of new work, twenty or so pages of revised/older work, and several substantial pieces of what will end up becoming a twenty-ish page craft essay. So I have decided to schedule myself into an artless corner in order to accomplish everything on time. And schedules are great - I certainly won't knock the very tools by which I live - but schedules also leave very little room for low-inspiration days and muse-less moments. Sure, I have sprinkled fact checking and research sessions throughout my weeks, but I can only rely on those for so long before I actually have to attach them to something substantial. Something from my own head. And there are days when a "Wednesday, 6-9PM: Get inspired" schedule simply isn't going to happen.
I say all this because I recently shared a piece I wrote for last semester's food course with a friend of mine. This friend is not a writer, and she hasn't even read a whole lot of my work. But after I showed her the piece I wrote about my first taste of authentic Montreal Poutine, she emailed a one-sentence response: "Wow! Powerful 9/11 story!"
Since September 11, 2001 formed a sort of backdrop for this piece, I wasn't surprised that she mentioned it. But I had never thought to define this as a "9/11 story." In fact, I have always insisted that, unlike so many of my friends who were personally impacted by 9/11, I didn't really have a 9/11 story. But apparently, at least to one reader, I do. I sat with this story again and read it, reread it, and have now put it away for awhile, at least mentally, so I can come back to it in a few weeks, with fresh eyes and a clear mind. The piece is titled "Ca va faire une maudite poutine," and I am posting it on my workspace page (tab at top right of screen) as an example of how it is possible to start with an idea - my first and last experience eating Poutine - and end up telling a multi-layered story about events that simply cannot be separated and that truly serve to enhance one another. Maybe I wouldn't have had the courage to try Poutine had I not recently seen such real tragedy on a global scale. Even so, 9/11 wrote its way into a story that I thought was about food - and only food. Goes to show what I know. A food piece is never just about food.
~~ Until next time, keep writing





