On Sunday night Mighty Reader and I (along with 800 or so other Seattle folks) went to Town Hall where Neil Gaiman read from and was interviewed about his latest release, the 10th Anniversary edition of American Gods. It's the "author's preferred text," which means that Mr Gaiman's publisher gave him the opportunity to add in all the stuff his original editor made him cut a decade ago, plus make whatever other changes he wanted to. The current edition, if I understand Mr Gaiman correctly, now clocks in at better than 200,000 words.
I'll come clean right up front and say that I am not a huge fan of Mr Gaiman's writing, though I enjoyed Neverwhere and I've read all the Sandman comics and I follow Mr Gaiman's blog. He's very charming and funny and he seems like a Really Nice Guy and I wanted to go last night because a) Mighty Reader is a NG fan and she bought the tickets, and b) Mr Gaiman has attained nearly legendary status as a fabulous reader and I wanted to see what that was all about. Plus, you know, he's funny.
It was well worth attending, and my advice to you is that if you ever get the chance to see Mr Gaiman in person, go see him. He reads aloud, frankly, beautifully. The biggest lesson to learn from Mr Gaiman's reading? Read Slowly And Distinctly. When he began I thought, "Gosh, he's moving at a snail's pace" but after a minute you fall into his rhythm and maybe it's his dreamy English accent or the dreamlike mood of the piece he read, but time really did stand still. The second bit he read was more dialogue-heavy and he did American accents for the characters and he also read slowly to great effect. I should note that these were pretty long excerpts he read, too. He could have skipped the interview and the questions from the audience and just read all night and that would've been fine with Mighty Reader and me.
Except, of course, Mr Gaiman's reading all night would've deprived us of his "advice to a novice fantasy writer." That was good stuff, and I'll paraphrase for you. First, his general advice to writers: "Write. Finish what you write." More specifically, his advice to genre writers: "Write. Stop reading your genre; read everything else and become influenced by the whole world of fiction. If you are interested in a specific mythology/religion/time period/alternate reality, then read primary sources, not other genre fiction about it. Read the Book of Kells or the Vedas or Homer or Dante or the stuff that Bram Stoker read when he was researching Dracula. Don't be one of those people who fall in love with Lord of the Rings and then decide to write Lord of the Rings, because Lord of the Rings has already been written, a lot better than you could ever write it. Tell the stories only you can tell." There was more, and it was all funnier than I relate it, but in sum Mr Gaiman gives good advice. Write a lot. Finish what you write. Read widely. Rinse and repeat.
Mr Gaiman, Amanda Palmer and singer/accordionist/pudding fan Jason Webley are apparently going to be together in Seattle, back at Town Hall, on 11/11/11 for a Big Event of some kind. Mr Gaiman and his wife, pop chanteuse Amanda Palmer (of the Dresden Dolls) are maybe going to do some kind of tag-team tour up the west coast between Halloween and November 11th, so for those of you who live along the Pacific Ocean, there'll likely be another chance to hear Neil Gaiman read aloud. You should go.
Showing posts with label Writers. Show all posts
Showing posts with label Writers. Show all posts
Tuesday, June 28, 2011
Reading and Writing With Neil Gaiman
Labels:
Reading,
Scott G. F. Bailey,
Writers,
Writing Rules
Monday, May 23, 2011
"Mrs Dalloway" by Virginia Woolf
I am reading Mrs Dalloway, Virginia Woolf's 1925 stream-of-consciousness novel. Clarissa Dalloway (aged 52, London socialite, married to a high-ranking government official and mother of a daughter, Elizabeth) is planning a party. On the morning of the party her household whirs along like a well-oiled machine, servants polishing silver and arranging furniture and laying in supplies. Things are looking pretty good for Mrs Dalloway. On her return from a brief walk (during which traffic has stopped as a limousine carrying--perhaps--the Queen of England passes down the street) Mrs Dalloway receives two shocks: first, she learns that her husband has been asked to lunch--alone--by a witty and popular noblewoman and second, she is visited by Peter Walsh, who was her beau some 33 years ago and has come to tell Clarissa that he's in love. The story continues from there.
The narrative is almost entirely made up of internal dialogue; there is very little in the way of descriptive prose or dramatized scenes. Clarissa goes for a walk. A couple sits in the park. Clarissa is visited by Peter Walsh. Peter goes and naps in the park. That's the first half of the book and it sounds pretty dull if you just relate it in terms of events. And if you were to ask what the central conflict is, what the story question is ("Will X manage to do Y before Z happens?"), I'd have to say that there really isn't one.
And yet this book is constantly moving, sucking me in and carrying me along and I'm reading it really quickly to see what comes next. It's all, as I say, taking place in the minds of the characters, and that's precisely what gives life to the events. The reaction of a neighborhood to the possibility that the Queen is being driven past them, within arm's reach even, and what it means to be a Londoner in 1923 is far more interesting than the action of the Queen being driven past. More sly on Woolf's part is how the attention of the patriotic crowd is drawn from the Queen (if it's her in the limousine) to a plane sky-writing an advertisement for toffee. The marketing is more immediately interesting than the confused emotions surrounding patriotism and nationalism and nobody is even looking when the royal car finally drives through the gates of Buckingham Palace. Peter Walsh, when he's walking to the park after having visited Clarissa, gets distracted by a pretty girl and he follows her discretely for some blocks, building up an elaborate fantasy life between him and the girl and then she goes into her house and it's all over and Walsh mourns that he's had such an adventure but couldn't possibly share it with anyone because it's all made up and a bit sordid, you know. And on like that and all of it's absolutely true to the life of the mind and fascinating.
It's all telling, too, not showing. This novel, in fact, violates many of the Rules that are widely promulgated about writing. I might go so far as to say that it proves the rules wrong:
You do not need to have a clear central conflict.
You do not need to have a "story question."
You do not need to have a single point-of-view per scene.
You do not need to avoid flashbacks.
You do not need to delay supplying backstory until after a conflict is established.
I will say, of course, that in order to get away with all of the rule-breaking listed above, you need to have absolute control over your form, you need to have a sophisticated and honest understanding of the human heart, you must be a brave writer and you must write absolutely beautiful prose. Then again, you should have all of those qualities anyway as a writer.
The narrative is almost entirely made up of internal dialogue; there is very little in the way of descriptive prose or dramatized scenes. Clarissa goes for a walk. A couple sits in the park. Clarissa is visited by Peter Walsh. Peter goes and naps in the park. That's the first half of the book and it sounds pretty dull if you just relate it in terms of events. And if you were to ask what the central conflict is, what the story question is ("Will X manage to do Y before Z happens?"), I'd have to say that there really isn't one.
And yet this book is constantly moving, sucking me in and carrying me along and I'm reading it really quickly to see what comes next. It's all, as I say, taking place in the minds of the characters, and that's precisely what gives life to the events. The reaction of a neighborhood to the possibility that the Queen is being driven past them, within arm's reach even, and what it means to be a Londoner in 1923 is far more interesting than the action of the Queen being driven past. More sly on Woolf's part is how the attention of the patriotic crowd is drawn from the Queen (if it's her in the limousine) to a plane sky-writing an advertisement for toffee. The marketing is more immediately interesting than the confused emotions surrounding patriotism and nationalism and nobody is even looking when the royal car finally drives through the gates of Buckingham Palace. Peter Walsh, when he's walking to the park after having visited Clarissa, gets distracted by a pretty girl and he follows her discretely for some blocks, building up an elaborate fantasy life between him and the girl and then she goes into her house and it's all over and Walsh mourns that he's had such an adventure but couldn't possibly share it with anyone because it's all made up and a bit sordid, you know. And on like that and all of it's absolutely true to the life of the mind and fascinating.
It's all telling, too, not showing. This novel, in fact, violates many of the Rules that are widely promulgated about writing. I might go so far as to say that it proves the rules wrong:
You do not need to have a clear central conflict.
You do not need to have a "story question."
You do not need to have a single point-of-view per scene.
You do not need to avoid flashbacks.
You do not need to delay supplying backstory until after a conflict is established.
I will say, of course, that in order to get away with all of the rule-breaking listed above, you need to have absolute control over your form, you need to have a sophisticated and honest understanding of the human heart, you must be a brave writer and you must write absolutely beautiful prose. Then again, you should have all of those qualities anyway as a writer.
Labels:
Influential Writers,
Virginia Woolf,
Writers,
Writing Rules
Tuesday, August 24, 2010
What I Wish I Had Written
I am sort of continuing a series of writerly explorations with this post, a series I began weeks ago with questions about "moral fiction" and continued with the questions about portrayals of minority-status characters and characters who are not part of our own social groups. Today it's less social and more personal, and I am wondering about our early experiences with writing. Specifically, I'd love it if you could all think for a minute and then in the comments tell me what was the first book you ever read that you wish you had written.
Maybe I'm alone in this experience, but there was a moment in time when I had finished a book and I imagined myself as the author of that specific book because it seemed like it had been written just for me and it seemed like something I myself could have written. Granted, when I was very young, in maybe 5th or 6th grade, my brothers and I would make up little comic books (they call them "chapbooks" these days) that were just folded sheets of paper with a staple in the spine and write our names on the front covers and pretend we were authors.
But those moments didn't have as large an impact on me as did the time I read Flannery O'Connor's Wise Blood. "This is a great book," I said to myself. "I understand what she was doing, and how she did it, and I get it and gosh, but I could have written it!" And, sad to say, when I began to write my first novel about six months later, I was writing very much a rip-off of Wise Blood. Still. The moment pushed me past the "it would be cool to be a novelist" stage into the "I could write a novel" stage. Which stage I haven't left.
Anybody have a similar story they wish to share? Because I want to hear it.
Maybe I'm alone in this experience, but there was a moment in time when I had finished a book and I imagined myself as the author of that specific book because it seemed like it had been written just for me and it seemed like something I myself could have written. Granted, when I was very young, in maybe 5th or 6th grade, my brothers and I would make up little comic books (they call them "chapbooks" these days) that were just folded sheets of paper with a staple in the spine and write our names on the front covers and pretend we were authors.
But those moments didn't have as large an impact on me as did the time I read Flannery O'Connor's Wise Blood. "This is a great book," I said to myself. "I understand what she was doing, and how she did it, and I get it and gosh, but I could have written it!" And, sad to say, when I began to write my first novel about six months later, I was writing very much a rip-off of Wise Blood. Still. The moment pushed me past the "it would be cool to be a novelist" stage into the "I could write a novel" stage. Which stage I haven't left.
Anybody have a similar story they wish to share? Because I want to hear it.
Labels:
Scott G. F. Bailey,
Writers,
Writing Influences
Wednesday, September 23, 2009
Forward and Backward Revisions
A couple of weeks ago, my friend/writer/teacher, Ellen Slezak, met with me for lunch. She had read the latest draft of my book, and she was kind enough to give me a few tips to finish it off. One of the things she suggested I do was to read through the book one more time and make sure that all of the sentences were flowing. This seems like common sense, right? But, I realized that this was a step in my revision process that I had neglected until now.
I thought about how I had been revising my book. For the most part, my last few drafts involved me reading through sections, identifying problems and then going back to fix those problems. Sometimes, I'd also scan through random sections and cut out words or details that weren't really contributing to the story I was trying to tell.
To me, this revision strategy is a backward movement. I don't mean backward in a bad way, but this revision involves hindsight--reading a section, and then going back into it to fix the problems. There is nothing wrong with backward revision. In fact, I'd argue that much of the time it is essential. But, something that I had been ignoring was the opposite strategy: forward revisions.
Forward revisions involves starting from the beginning of the story, or at the beginning of a long section of the story, and moving through it forwards, fixing things on the fly as you go along. This is what I did in my latest draft, and it really helped me fix the problem Ellen had identified. I started from page 1, and I read through the book quickly, all the way to the end. If something caught me--and awkward sentence or strange grammar--I fixed it quickly, backstepped a good ways, and then continued to race through the book forwards again.
My book was about 65,000 words long when I gave it to Ellen. I felt that it was focused, coherent, and told the story I wanted to tell. I thought is was pretty much done. However, after my forward revision, which did little aside from adding extra words here and there to make transitions work, my book ended up being over 67,000 words. As a result of these extra words, I find that my prose flows much more smoothly from one scene to the next. I also think my voice comes through more clearly.
The key to forward revisions is to go through the book quickly. I think this is an effective way to get natural sentence rhythms flowing again, and it allows you to see the book more as a whole than when you move slowly and dissect each scene. In a similar way that an outline gives you a quick overview of the structure of your story, racing through the prose quickly gives you an overview of the prose style of your story. It's an important last step, one that I had neglected because I was focusing so much on bigger elements of my book. AND, for those of us who fear that we may have lost the original spontaneity of the story by overworking it, I think this forward revision can bring some of that back.
Questions: Do all of you do this sort of fast, forward revision? Do you think it's important? If you don't do this, is there another approach you use for getting those final touches done on your manuscript?
Additional Question: Why didn't I get a MacArthur Genius Grant?
Monday, May 4, 2009
How Flexible Are Your Sentences?
Have you ever gotten an “I infection”?
It can happen to the best of us.
I came home to a ringing telephone. I picked it up. I heard my uncle’s urgent voice on the other end of the line. I knew immediately that something was wrong.
Sometimes we get into a particular sentence pattern that can make our prose sound robotic. Of course it doesn’t always have to be the first person pronoun. Any sentence pattern, when used over and over again, can make for boring reading.
There are easy ways of preventing repetitive sentence structure. You can use compound sentences to combine similar thoughts. You can start some sentences with prepositional phrases. In a pinch, you could even use the dreaded passive voice!
But sometimes these tactics can still make prose feel too elementary. To show off sentence flexibility, you have to understand that every thought we want to write down can be expressed in hundreds of different ways. Instead of always starting a sentence with the character who’s being discussed or one of the common prepositional phrases, try starting the sentence with a word or phrase you wouldn’t normally think to use.
“Call me Ishmael,” from Moby Dick is an outstanding example. That’s a pretty unconventional sentence that’s amazing because it immediately gives us a sense of the narrator’s voice, and it’s a command to the reader, something we rarely see in prose. Melville could just as easily have started the story with, “There was a man named Ishmael,” but that makes for a much less colorful opening.
A Story From A to Z
Here’s an exercise that demonstrates how flexible sentence structure can be. Write a story using 26 sentences. Start each sentence with a different letter of the alphabet, using A for the first sentence, B for the second sentence, C for the third sentence, et cetera. Even though it might feel a little challenging at first, you’ll realize that you can still create a logical sequence of events, even with this strict rule in place. The language and sentence patterns you’ll end up using will have much more variety.
For a great example of how having sentence flexibility can make a story richer, take a look at the book The Gargoyle by Andrew Davidson. If you take the first letter of each chapter, you’ll find that it spells out a message. (The last letter of each chapter may also be illuminating!)
~DM
Labels:
Davin Malasarn,
Exercises,
Writers,
Writing Technique
Subscribe to:
Posts (Atom)