My book club is reading The Time Traveler's Wife this month. I read the book a few years ago for a previous book club, but I was interested to come back to it as an aspiring writer. It is, after all, a very popular book that has done really well on the bestseller lists. Thanks to having the memory retention of a fruit fly, I only vaguely remembered the plot points of the book - he traveled through time, he had a wife - so I was coming to the story with a relatively fresh set of eyes.
Lo and behold, this book was breaking rules all OVER the place! There was a prologue, for one (I thought only J.R.R. Tolkien could get away with that). And what was the prologue about, you ask?
BACKSTORY.
The insidious, not to be trusted, never to be included, BACKSTORY. Yeah, it's an all-caps kind of thing. The whole prologue basically establishes what happens when Henry, Mr. Time Traveler, time travels. Where he goes, how he ends up there, how he feels, what happens to him when he gets there, etc. It's not tied to a specific event in any way, it's really just to give the reader a basis for understanding what kind of time traveler he is. It's classic backstory info.
So why is it in there? How did it get past the keen eyes of beta readers, agents, and editors?
I obviously can't say for certain, but I can hazard a guess. Because while it is backstory, it's not an info dump. We're not getting his whole life history - in fact, we're not really getting a history at all - we're just getting enough information for us to understand the story that's coming up. They're details that are necessary to understand how the time travel affects his life, and rather than awkwardly integrating them into a scene, the author uses the opportunity to establish the character's personality and his relationship to the time travel. It's backstory, but it's character-building backstory, and it's intriguing enough to draw us into the rest of the story. It's an atypical time traveler scenario (she describes it as a disease), so the premise is set from the beginning, as is the conflict.
The lesson I took away from this book is that a little backstory never hurt anyone, SO LONG AS it helps the story. It should be accomplishing something else at the same time - establishing the conflict, introducing character personalities and habits, setting the hook of the story, etc. It's especially useful in cases like The Time Traveler's Wife, where we need to know the technical details of something but we don't want those details bogging down an actual scene.
I know BACKSTORY is a hotly debated topic, but it's still needed. Even if you only mention certain pieces of the story, we need that info before going into a scene so we as the reader are appropriately set up to understand the tension of the scene. The trick is knowing when to stop so you don't inundate your reader with unnecessary and tension-breaking info.
What about your thoughts on BACKSTORY? Do you agree, disagree, unagree, reagree? Weigh in!
Wednesday, November 9, 2011
Monday, November 7, 2011
Officially querying
Hello gentle readers, and a "sorry it's Monday but Friday's only four days away" to you as well. While most of you are deep in the NaNo trenches, I am deep in the querying trenches. I officially started sending out query letters for my latest project last week, and have been busily updating my spreadsheet of agents as I receive responses back. It's taken me this long to determine whether or not I actually wanted to talk about querying, but it's not fight club, so Tyler Durden probably won't show up at my house in the middle of the night if I post this.
First, and most importantly, it's a hell of a lot harder than I thought it would be. I knew there would be rejection, gentle readers (a word I'm growing to hate). I had prepared myself. I knew it was an uphill battle, that I would have to fight for agents to read my query, and fight harder for them to request additional materials, and fight even harder to find the agent who would becrazy enough willing to champion my work to an editor. And I knew the difficulties didn't end there, either. I had mentally prepared myself for all of this, to receive those form rejections, to obsess over a comma in an email, to read and read and re-read my work until I couldn't remember how to spell "the" anymore.
What I didn't anticipate - and what's been kicking me in the butt for the last week and half - is how it would feel to be rejected by agents on my carefully cultivated list of submissions. It wasn't just that an agent was passing on my material, it was that I'd spent hours/days/weeks pulling together a list of agents I thought were best suited to represent my work. They were the agents that work in my genre, that rep other authors with titles similar to mine, and if anyone was going to get my weird little story they would be the ones. So getting a pass from someone like that is almost like being rejected by the genre itself. It makes me question myself and my work, which is what I was trying to avoid all along.
But before you cry for me, Argentina, you should know I'm a fairly resilient person. Acknowledging the problem is the first step on the road to recovery, and my focus going forward is to keep honing my craft and keep cultivating my list. For the most part I don't know why they pass on my work, so I can't psych myself out with imagined reasons why they don't want to represent me. All I can control is my own effort, which is much better spent improving my writing and not crying over pints of Ben and Jerry's (who should totally make a Chardonnay flavor. Two birds, one stone).
Where are you in the writing process? Are you also querying your work? How do you handle your query journey?
First, and most importantly, it's a hell of a lot harder than I thought it would be. I knew there would be rejection, gentle readers (a word I'm growing to hate). I had prepared myself. I knew it was an uphill battle, that I would have to fight for agents to read my query, and fight harder for them to request additional materials, and fight even harder to find the agent who would be
What I didn't anticipate - and what's been kicking me in the butt for the last week and half - is how it would feel to be rejected by agents on my carefully cultivated list of submissions. It wasn't just that an agent was passing on my material, it was that I'd spent hours/days/weeks pulling together a list of agents I thought were best suited to represent my work. They were the agents that work in my genre, that rep other authors with titles similar to mine, and if anyone was going to get my weird little story they would be the ones. So getting a pass from someone like that is almost like being rejected by the genre itself. It makes me question myself and my work, which is what I was trying to avoid all along.
But before you cry for me, Argentina, you should know I'm a fairly resilient person. Acknowledging the problem is the first step on the road to recovery, and my focus going forward is to keep honing my craft and keep cultivating my list. For the most part I don't know why they pass on my work, so I can't psych myself out with imagined reasons why they don't want to represent me. All I can control is my own effort, which is much better spent improving my writing and not crying over pints of Ben and Jerry's (who should totally make a Chardonnay flavor. Two birds, one stone).
Where are you in the writing process? Are you also querying your work? How do you handle your query journey?
Thursday, October 27, 2011
Even on vacay I'm working
Well, relatively speaking. I just got back from eight glorious days in New York where I ate too much Thai food, walked about a billion miles, smelled about a billion smells, and met a girl who met Anjelica Huston, which basically means I met Anjelica Huston. The weather was perfect, the coats were amazing, and Central Park was a dream.
But even amongst all this vacationing glory, gentle reader, my brain was working. How, you ask? Because my manuscript is set in New York, which means my trip wasn't just about vacation - it was reconnaissance. I stalked all the major locations, found nearby restaurants, made note of subway stops, and people watched the crap out of those places. I'd done my research beforehand - of course - but seeing it live in person was a whole new level of understanding. Instead of just imagining the jarring rides of the subway or the feel of a hundred miles of concrete under my boots, I was living those scenes. Now I have more than just Google street views of places, or second-hand knowledge from friends - I have my own memories to write against, which is a much richer experience.
Next book I write will be set in Greece. Or Italy. Oooo, or both. I'm off to plan.
Do you like to write about places you've never been, or do you stick close to home? Have you ever done your own reconnaissance on vacation?
But even amongst all this vacationing glory, gentle reader, my brain was working. How, you ask? Because my manuscript is set in New York, which means my trip wasn't just about vacation - it was reconnaissance. I stalked all the major locations, found nearby restaurants, made note of subway stops, and people watched the crap out of those places. I'd done my research beforehand - of course - but seeing it live in person was a whole new level of understanding. Instead of just imagining the jarring rides of the subway or the feel of a hundred miles of concrete under my boots, I was living those scenes. Now I have more than just Google street views of places, or second-hand knowledge from friends - I have my own memories to write against, which is a much richer experience.
Next book I write will be set in Greece. Or Italy. Oooo, or both. I'm off to plan.
Do you like to write about places you've never been, or do you stick close to home? Have you ever done your own reconnaissance on vacation?
Tuesday, October 11, 2011
Austin Teen Book Festival - part deux
So, last I left you we had sat through a swoon-worthy I Heart Love Stories panel with Simone Elkeles, Jenny Han, Cristina Garcia, Stephanie Perkins, Jennifer Ziegler, and Christina Mandelski. After a quick stop by the book sellers tables to pick up my plundered goods, I moseyed over to the Alternaworlds panel for the final event of the day.
This crowd was ENORMOUS. It could have something to do with Scott Westerfeld's presence on the panel - the Festival had a steampunk theme in honor of Leviathan - but I think it was more that they consolidated panels for the last event so that we were the only panel on the first floor of the events center. I'm terrible with numbers, but I would guess there were at least two hundred people there, filling up the chairs and crowding the sides of the space for a chance to get closer to the stage. If I'd have been a teenager, I would have done the same thing. Authors rarely get the celebrity they deserve, so I was almost a bit giddy at the feeling of so many people (young people!) at a book event.
The Alternaworlds panel included Scott Westerfeld, Maureen Johnson, Jonathan Maberry, Brian Yansky, and Rosemary Clement-Moore. Whereas the Love Stories panel was focused on love stories as a genre, this panel was much more focused on the art and craft of writing, and the craft of world building. Once again there were a lot of young authors, so the audience asked great questions about the craft of writing and I shamelessly stole their answers to share with all of you:
This crowd was ENORMOUS. It could have something to do with Scott Westerfeld's presence on the panel - the Festival had a steampunk theme in honor of Leviathan - but I think it was more that they consolidated panels for the last event so that we were the only panel on the first floor of the events center. I'm terrible with numbers, but I would guess there were at least two hundred people there, filling up the chairs and crowding the sides of the space for a chance to get closer to the stage. If I'd have been a teenager, I would have done the same thing. Authors rarely get the celebrity they deserve, so I was almost a bit giddy at the feeling of so many people (young people!) at a book event.
The Alternaworlds panel included Scott Westerfeld, Maureen Johnson, Jonathan Maberry, Brian Yansky, and Rosemary Clement-Moore. Whereas the Love Stories panel was focused on love stories as a genre, this panel was much more focused on the art and craft of writing, and the craft of world building. Once again there were a lot of young authors, so the audience asked great questions about the craft of writing and I shamelessly stole their answers to share with all of you:
- Maureen Johnson talked about chasing down the "what ifs" and even threw out some Holly Black name dropping in the process. She said that Black was the queen of asking the right questions when developing a new story idea, and it basically consisted of a relentless string of questions. What if ghosts existed? How would they integrate with society? Could everyone see them? What could they physically do? What would the government do about them? The key to asking the right questions is to step back far enough to see the full scope of the picture, and then slowly drill down until you know all of the specifics.
- Scott Westerfeld had the ultimate cure for writer's block: lock yourself in a room with nothing else to do for four hours. You'll get over that block real fast. For someone whose house suffers from enough shiny distractions to captivate a kitten, I can understand the advice.
- Jonathan Maberry talked about being realistic within the fantastic. I've gone over the same concepts with my writing partners, so it was nice to get some backup from a successful published author. Even if your world includes zombies, like his, there still has to be a realistic structure to the world and how people function within it. The closer you stay to the real world - with fantastic twists - the more your readers can connect with the characters and believe the events that transpire.
Those were the highlights of the panel for me, mainly because I let two weeks go by without writing about it :). My overall feeling about the Festival, however, was that I've been missing out on prime opportunities to learn from these authors by not going to more author events in the past.
Tuesday, October 4, 2011
Austin Teen Book Festival - part un
I had a lovely book-filled Saturday this weekend, kicked off by a book release party for one of my critique partners at Book People here in Austin. She is the illustrator of a new children's book, and it was so fun to see all of the children reacting to the story when she read aloud. It was a Halloween-themed book, so of course they had a costume contest. There was a girl that didn't even come up to my waist dressed as a witch, and she accidentally swept my feet with her straw broom at least twice. All in all, a successful morning.
Then we headed over to the Austin Teen Book Festival for the afternoon. I've actually never been to a book event outside of BEA (and that was for work, so it almost doesn't count), so I was curious to see how this one would go. I only heard about it through my critique partner, who only heard about it through a book reviewer friend of hers, so I was worried there wouldn't be much of a crowd to support the authors who would be speaking there. Scott Westerfeld was the keynote speaker, but we got there late in the afternoon so we missed the keynote. I was most excited to hear from Simone Elkeles, since I have a mad agent crush on her agent, and Jackson Pearce because I have a mad crush on anything she does.
I was happy about how many names I recognized on the panels - Simone Elkeles, Scott Westerfeld, Melissa Walker, David Levithan, Jackson Pearce, Stephanie Perkins, and a host of other fantastic authors and speakers (see them all here). The Festival also had a great idea to host all four of the panels at the same time, four times over the course of the day, so you didn't miss a panel if you wanted to see them all. We had time enough for two panels, so I picked the I Heart Love Stories panel and the Alternaworlds panel. I originally wanted the Supernatural Suspense for my Jackson Pearce lady crush, but because of sound issues they couldn't host that panel at the end of the day.
I Heart Love Stories included Cristina Garcia, Simone Elkeles, Jenny Han, Stephanie Perkins, Jennifer Ziegler, and Christina Mandelski. Simone and Stephanie were definitely the big names on the panel, and most of the questions were directed at them. I had heard of Anna and the French Kiss, but that's not typically my type of book. However, after seeing Stephanie on the panel I definitely want to pick up her books. She was cute, fashionable, young, and funny. And Simone was exactly what I expected her to be - funny, sassy, irreverent, and charming. I'd like to think she and I had a moment when I pretended that I might want a vampire boyfriend in space (don't ask).
The audience asked some great questions, so I got a lot of takeaways from this panel:
Then we headed over to the Austin Teen Book Festival for the afternoon. I've actually never been to a book event outside of BEA (and that was for work, so it almost doesn't count), so I was curious to see how this one would go. I only heard about it through my critique partner, who only heard about it through a book reviewer friend of hers, so I was worried there wouldn't be much of a crowd to support the authors who would be speaking there. Scott Westerfeld was the keynote speaker, but we got there late in the afternoon so we missed the keynote. I was most excited to hear from Simone Elkeles, since I have a mad agent crush on her agent, and Jackson Pearce because I have a mad crush on anything she does.
I was happy about how many names I recognized on the panels - Simone Elkeles, Scott Westerfeld, Melissa Walker, David Levithan, Jackson Pearce, Stephanie Perkins, and a host of other fantastic authors and speakers (see them all here). The Festival also had a great idea to host all four of the panels at the same time, four times over the course of the day, so you didn't miss a panel if you wanted to see them all. We had time enough for two panels, so I picked the I Heart Love Stories panel and the Alternaworlds panel. I originally wanted the Supernatural Suspense for my Jackson Pearce lady crush, but because of sound issues they couldn't host that panel at the end of the day.
I Heart Love Stories included Cristina Garcia, Simone Elkeles, Jenny Han, Stephanie Perkins, Jennifer Ziegler, and Christina Mandelski. Simone and Stephanie were definitely the big names on the panel, and most of the questions were directed at them. I had heard of Anna and the French Kiss, but that's not typically my type of book. However, after seeing Stephanie on the panel I definitely want to pick up her books. She was cute, fashionable, young, and funny. And Simone was exactly what I expected her to be - funny, sassy, irreverent, and charming. I'd like to think she and I had a moment when I pretended that I might want a vampire boyfriend in space (don't ask).
The audience asked some great questions, so I got a lot of takeaways from this panel:
- One girl asked how she could make her love story less predictable. Simone countered that love stories are predictable - in fact, in a romance novel it's what you rely on. You know they're going to get together. The tension comes from the obstacles they have to overcome to be together. It's about how much crap can you throw at them, how insurmountable can you make the odds? If they're good enough and believable enough, then even the expected ending is still satisfying.
- Cristina Garcia said that typically romance novels have happy endings and love stories have tragic endings (apparently this is a standard knowledge thing of which I'm only just now aware). The panel discussed at large what this meant in their writing, and most of the women agreed that a good story has a healthy blending of both. Apparently Romeo and Juliet are NOT the standard in storytelling today (and thank goodness for that).
- Another audience member asked about the reality of these overwhelming love stories. Both Stephanie and Simone said they met their husbands when they were teenagers, and that they wrote from a place of experience. I think Simone said it best: "Falling in love as a teenager was the best thing that ever happened to me. And the worst." (Cue the lady crush)
- The panel overwhelmingly agreed that you can't write to the market. You have to write the story that you want to write, and then make a market for yourself.
- There were A. LOT. of young writers there. Most of the questions came from young people - boys and girls - and were about stories they're writing. It was amazing to see hundreds of kids willing to spend a Saturday talking about books and writing. Warmed the cold, dead cockles of my heart.
The overall feeling of this panel was sweet and encouraging, and made me want to get out there and write about cute boys and school dances. The Alternaworlds panel also had some great advice, but I'll save that for another day.
What did you do this weekend? Anything fun and/or writing related?
Tuesday, September 27, 2011
Leaving a writing group
I've been in a great local writing group for almost a year now, and these fellow critters have been essential in improving my writing, calling out my faults and lazy shortcomings, and encouraging me to continue on with my writing even when it feels like I've just word vomited on the page. I am a better writer because of them, and I can't imagine my writing life without their continued support and input.
So imagine my surprise when our founding member, the critter who brought the group together in the first place, emailed over the weekend to let us know he would be stepping out of the group. (Yeah, you thought it was going to be me, didn't you?) As the person who was the driving force behind the group for so many months, it was a shock to see him bow out now. It was (what I suspect are) the usual reasons for leaving a group - balancing family time and writing time. And I can hardly blame him for his reasons, since the closest thing I have to a kid is the partner-in-crime and our trusty sidekick, The Dog.
Still, it was a big disappointment for me. He'd brought us all together, weathered the storms of our growing pains while we figured out meeting times and submission deadlines and new member rules. As the only male in the group he gave invaluable feedback on the male characters and male voices in our pieces, and helped us determine what would appeal to boys in our writing. His own writing had grown by leaps and bounds in the group, and the last piece he submitted was so many miles above the first draft that we saw that I experienced a profound sense of pride in how far he'd come, and how much the group had helped him.
While I hope he continues to write and finds other outlets for his creativity, I worry. I worry because I know how lost I would be without their feedback. I worry because I know how much I would let my self-imposed deadlines slip if there were no one else to hold me accountable. I worry because writing is a lonely enough endeavor that if you don't have an outlet to discuss it you might find yourself wondering why you're pursuing it at all. I worry because I know how much my own life gets in the way of writing, and I don't even have kids to keep up with.
I worry because I can't help but feel like we've lost another writer in the world.
It's a hard pursuit, I know that, but I think it's worth it. The stories we tell, the joy we bring, for me it's worth the late nights and the early mornings and the longing looks outside when it's beautiful and you're stuck inside with a synopsis to write. It's worth the rejection and the wait and the agonizing edits and the overwhelming fear that you might get it wrong (or you might get it right). Because I still remember what it felt like to stay up until four in the morning hiding in the bathroom finishing a book because I Just. Couldn't. Put. It. Down. And if I can inspire just one person to such nocturnal fevers, it will be worth it.
Have you ever lost a critique partner? How did you feel when they left? Was there ever a partner you wished you could have talked out of their exit?
So imagine my surprise when our founding member, the critter who brought the group together in the first place, emailed over the weekend to let us know he would be stepping out of the group. (Yeah, you thought it was going to be me, didn't you?) As the person who was the driving force behind the group for so many months, it was a shock to see him bow out now. It was (what I suspect are) the usual reasons for leaving a group - balancing family time and writing time. And I can hardly blame him for his reasons, since the closest thing I have to a kid is the partner-in-crime and our trusty sidekick, The Dog.
Still, it was a big disappointment for me. He'd brought us all together, weathered the storms of our growing pains while we figured out meeting times and submission deadlines and new member rules. As the only male in the group he gave invaluable feedback on the male characters and male voices in our pieces, and helped us determine what would appeal to boys in our writing. His own writing had grown by leaps and bounds in the group, and the last piece he submitted was so many miles above the first draft that we saw that I experienced a profound sense of pride in how far he'd come, and how much the group had helped him.
While I hope he continues to write and finds other outlets for his creativity, I worry. I worry because I know how lost I would be without their feedback. I worry because I know how much I would let my self-imposed deadlines slip if there were no one else to hold me accountable. I worry because writing is a lonely enough endeavor that if you don't have an outlet to discuss it you might find yourself wondering why you're pursuing it at all. I worry because I know how much my own life gets in the way of writing, and I don't even have kids to keep up with.
I worry because I can't help but feel like we've lost another writer in the world.
It's a hard pursuit, I know that, but I think it's worth it. The stories we tell, the joy we bring, for me it's worth the late nights and the early mornings and the longing looks outside when it's beautiful and you're stuck inside with a synopsis to write. It's worth the rejection and the wait and the agonizing edits and the overwhelming fear that you might get it wrong (or you might get it right). Because I still remember what it felt like to stay up until four in the morning hiding in the bathroom finishing a book because I Just. Couldn't. Put. It. Down. And if I can inspire just one person to such nocturnal fevers, it will be worth it.
Have you ever lost a critique partner? How did you feel when they left? Was there ever a partner you wished you could have talked out of their exit?
Tuesday, September 20, 2011
Movies vs. Books: the plot thickens
I saw the movie Drive this weekend, starring Ryan Gosling and some other people I didn't pay attention to (fine, it had a good cast, but come on. RYAN. F-ING. GOSLING. Pretty sure that's his middle name). It was a very different film from what I expected given the trailer, which made me think of the concepts of storytelling and backstory. As in, how much do you know/need to know about your characters and story, and how much do you reveal in the story itself?
I read a review of the movie after having seen it and the review pointed out one major point that I completely missed while watching the film: Ryan Gosling's character has no name. Even in the credits, they simply refer to him as "Driver." This one caught me off guard, because I've had this very conversation in many of my crit groups, and I've heard it from more than one source - you need to have character names. It's how readers identify a character, and if they can't name a character - even the narrator - they get antsy about it after a while. I know I do. But in the film, I never even noticed that his character was never named. How could they get away with such a thing under my trained nose?
Because I had a face. Ryan Gosling's face. I didn't need to know his name because his face was what identified him on the big screen. For me, it was the equivalent of giving me a name, because it was an instantly recognizable feature of that character. You can get away with it on screen, since it's a visual aspect, but giving a character description every time in lieu of a name doesn't really work. So for movies, we have faces. For books, we have names.
The second thing I noticed (which I actually did notice) was a complete absence of backstory. Gosling's character has a very specific side job (no spoilers, I promise) that is an offshoot of his day job but certainly not in the same legal category. He's a young guy with an old world feel, and being the writer-type I am, my first question was "How did he come to this line of work?" It's not something people fall into, and the backstory would have helped tremendously in my efforts to believe the character and what he knew. But we're never given a hint of backstory.
This movie is actually based on a book, so I'm curious if the book goes into his past in more detail. I would hope it does, because it drove me crazy throughout the movie. I kept expecting the explanation to trickle out along the way, to give us more depth to the character and build the anticipation of what he would do. But we never even got acknowledgement from any of the other characters that this might be a question to ask. No one, anywhere along the way, ever asked him "Where did you learn how to do that?" It left me feeling unsatisfied at the end of the film.
I would argue that this isn't something you can get away with in a book. You certainly HAVE TO KNOW your character's backstory - and not just the main character, either. Even if we never hear it, even if we never get to know all the nitty gritty details, you as the writer need to know it in order to fully realize your characters. It can be annoying and tiresome to think through it on that level, but it's essential. And for me personally, as a reader I like to know the backstory, especially if it's relevant to the details of the story you're telling. I don't need to know everything, but I like to see it sprinkled in here and there to give me context for the character I'm following. It's not an area often visited by movies - frankly they don't have the time - but it's necessary in any good story.
Have you seen any movies lately that have highlighted some conventions of storytelling specific to the written word? Have you read any books lately that felt like movies and left you wanting more?
I read a review of the movie after having seen it and the review pointed out one major point that I completely missed while watching the film: Ryan Gosling's character has no name. Even in the credits, they simply refer to him as "Driver." This one caught me off guard, because I've had this very conversation in many of my crit groups, and I've heard it from more than one source - you need to have character names. It's how readers identify a character, and if they can't name a character - even the narrator - they get antsy about it after a while. I know I do. But in the film, I never even noticed that his character was never named. How could they get away with such a thing under my trained nose?
Because I had a face. Ryan Gosling's face. I didn't need to know his name because his face was what identified him on the big screen. For me, it was the equivalent of giving me a name, because it was an instantly recognizable feature of that character. You can get away with it on screen, since it's a visual aspect, but giving a character description every time in lieu of a name doesn't really work. So for movies, we have faces. For books, we have names.
The second thing I noticed (which I actually did notice) was a complete absence of backstory. Gosling's character has a very specific side job (no spoilers, I promise) that is an offshoot of his day job but certainly not in the same legal category. He's a young guy with an old world feel, and being the writer-type I am, my first question was "How did he come to this line of work?" It's not something people fall into, and the backstory would have helped tremendously in my efforts to believe the character and what he knew. But we're never given a hint of backstory.
This movie is actually based on a book, so I'm curious if the book goes into his past in more detail. I would hope it does, because it drove me crazy throughout the movie. I kept expecting the explanation to trickle out along the way, to give us more depth to the character and build the anticipation of what he would do. But we never even got acknowledgement from any of the other characters that this might be a question to ask. No one, anywhere along the way, ever asked him "Where did you learn how to do that?" It left me feeling unsatisfied at the end of the film.
I would argue that this isn't something you can get away with in a book. You certainly HAVE TO KNOW your character's backstory - and not just the main character, either. Even if we never hear it, even if we never get to know all the nitty gritty details, you as the writer need to know it in order to fully realize your characters. It can be annoying and tiresome to think through it on that level, but it's essential. And for me personally, as a reader I like to know the backstory, especially if it's relevant to the details of the story you're telling. I don't need to know everything, but I like to see it sprinkled in here and there to give me context for the character I'm following. It's not an area often visited by movies - frankly they don't have the time - but it's necessary in any good story.
Have you seen any movies lately that have highlighted some conventions of storytelling specific to the written word? Have you read any books lately that felt like movies and left you wanting more?
Tuesday, September 6, 2011
It's all about perception
I had a funny encounter with one of my fellow critiquers last night that really brought home a big concept for me. One of the issues I struggle with during any critique is being able to look at the feedback objectively. Typically that involves setting my own biases aside to determine whether or not I think the feedback is valid.
We were discussing a character in my manuscript that had just gone through a scene of trying on clothes. In the scene, she complains because none of the clothes fit her right. The group debated what they thought she looked like - some people thought she was tall and lanky and wouldn't have felt fat, some thought she was heavier and would have, some people wanted more character description. All of that is fine and good, but as we continued the conversation one girl said something that shocked me.
"She could be curvy," she explained to the others. "Even if she were a size 8, she could still have nice curves."
Now, we're not supposed to talk during these things when we're being critiqued, but I couldn't help myself.
"I'm sorry," I interrrupted. "I have a question. Do you think size 8 is large?"
Her eyes got big. "Well, yeah."
This was a moment for me, gentle readers. Because I happen to be size 8, and I have never in my life heard anyone refer to size 8 as "large." It's pretty solidly average in my book, and I am pretty solidly average myself. I ran through all the logical scenarios I could think of in my head for a moment, and asked the first question that came to mind.
"How tall are you?"
"Five two."
Uh, yeah. Me? Not five two. Not even close to five foot two inches tall. And then it made sense, in a way. If I were about half a foot shorter and the same proportions, I would probably be considered a lot curvier than I am now. But having never been five foot two (well, at least not for a good fifteen years), it would have never occurred to me that my size could be considered large.
What's the lesson for me in this? That sometimes, no matter how much you edit or how many people weigh in on your manuscript, someone will have a bias that you'll never even think of. So as much as I'll continue to worry about making myself as clear as possible, I've also relaxed about capturing all of those butterflies with my net.
What about you? Have you run into issues of perception with beta readers? How did you choose to handle it in your manuscript?
We were discussing a character in my manuscript that had just gone through a scene of trying on clothes. In the scene, she complains because none of the clothes fit her right. The group debated what they thought she looked like - some people thought she was tall and lanky and wouldn't have felt fat, some thought she was heavier and would have, some people wanted more character description. All of that is fine and good, but as we continued the conversation one girl said something that shocked me.
"She could be curvy," she explained to the others. "Even if she were a size 8, she could still have nice curves."
Now, we're not supposed to talk during these things when we're being critiqued, but I couldn't help myself.
"I'm sorry," I interrrupted. "I have a question. Do you think size 8 is large?"
Her eyes got big. "Well, yeah."
This was a moment for me, gentle readers. Because I happen to be size 8, and I have never in my life heard anyone refer to size 8 as "large." It's pretty solidly average in my book, and I am pretty solidly average myself. I ran through all the logical scenarios I could think of in my head for a moment, and asked the first question that came to mind.
"How tall are you?"
"Five two."
Uh, yeah. Me? Not five two. Not even close to five foot two inches tall. And then it made sense, in a way. If I were about half a foot shorter and the same proportions, I would probably be considered a lot curvier than I am now. But having never been five foot two (well, at least not for a good fifteen years), it would have never occurred to me that my size could be considered large.
What's the lesson for me in this? That sometimes, no matter how much you edit or how many people weigh in on your manuscript, someone will have a bias that you'll never even think of. So as much as I'll continue to worry about making myself as clear as possible, I've also relaxed about capturing all of those butterflies with my net.
What about you? Have you run into issues of perception with beta readers? How did you choose to handle it in your manuscript?
Wednesday, August 24, 2011
Random thoughts on a...Wednesday? Really? Already?
1) I'm going to need pictures of me to start better aligning with how I see myself in my head. Read: Natalie Portman.
2) I've been stood up on three client calls this week. We don't have waiters in my office, but I imagine the same look of pity and shame when my coworkers come into the room.
3) I know it's been a rough Texas summer when I'm almost jealous of the East Coast for having a hurricane.
4) I don't usually write to music since I find it too distracting (yeah, maybe I act out music videos in my head, judgment-free zone). But I started a Pandora station for Film Scores and it's actually an awesome station to write to. Plus I've already got the movie all planned out now.
5) There are some new fall/spring shows on the big networks that look really good. Like I can already feel my productivity running down the drain good. I'll call it "character research" when I watch, but that will be a lie.
6) I can't decide if I should stop reading about the economy because it's freaking me out or if I should keep reading so I'm an informed citizen. Mostly I've resolved this by playing games on my phone and reading celebrity gossip blogs.
7) Oh, ten is so not happening today.
What's your random thought for the day?
2) I've been stood up on three client calls this week. We don't have waiters in my office, but I imagine the same look of pity and shame when my coworkers come into the room.
3) I know it's been a rough Texas summer when I'm almost jealous of the East Coast for having a hurricane.
4) I don't usually write to music since I find it too distracting (yeah, maybe I act out music videos in my head, judgment-free zone). But I started a Pandora station for Film Scores and it's actually an awesome station to write to. Plus I've already got the movie all planned out now.
5) There are some new fall/spring shows on the big networks that look really good. Like I can already feel my productivity running down the drain good. I'll call it "character research" when I watch, but that will be a lie.
6) I can't decide if I should stop reading about the economy because it's freaking me out or if I should keep reading so I'm an informed citizen. Mostly I've resolved this by playing games on my phone and reading celebrity gossip blogs.
7) Oh, ten is so not happening today.
What's your random thought for the day?
Wednesday, August 17, 2011
Picking and choosing
Not to be confused with picky or choosy. Although I can be those sometimes as well.
When I first started receiving feedback on my writing, I thought that if someone said something it must be true. Which meant it must be changed. So if someone said, "This scene is dumb, take it out," I took it out. And if someone said "I don't like this character, give her blue hair," I gave her blue hair. That's what feedback is for, right? At some point our editorial vision turns myopic and we can't see the forest for the trees, so we ask others to read our work and tell us when we've jumped the shark (maybe literally).
As you might imagine, this eventually put me in a really frustrating cycle. I'd change something for one critique partner and another would say they hated the change. I'd change it back and a third reviewer would say I should go in an entirely new direction. I had so many voices in my head that I couldn't hear my own, and my story fell apart in revisions. I actually walked away from a manuscript - probably the best thing I've written to date - because I didn't even know what I wanted it to be anymore. I'd put it through too many critiques by too many people in too many rounds. My beautiful jello mould had melted into a glob of hot mess.
I took a very different approach with critiques on my current manuscript. I restricted the number of reviewers and made sure they were a diverse enough group to catch 90% of the plotting or characterization mistakes I made. I took notes on each round of critiques (we critique a few chapters at a time) and then let them sit for several weeks. I didn't make changes, I didn't read through the notes, I went and distracted myself in other ways. Then, when the little critiques started to add up to big picture changes for me, I went back and made the changes I wanted to make.
Yeah, read that again. I'll even bold it for you. I made the changes I wanted to make.
If I didn't like the feedback? I didn't change it.
If I didn't agree with the feedback? I didn't change it.
If I got conflicting feedback? I chose the one I agreed with and made the changes.
If I could understand the point of the feedback but wanted to take the story in a different direction? I didn't change it.
This is your story at the end of the day. You have to tell the story you want to tell, which means you get to pick and choose the changes you make. You own the story, so you're responsible for the choices it makes. You ask for feedback to point out what you can't see, but that doesn't mean everything they see is right for the story you are trying to tell.
A point of clarification: I draw a distinction between feedback that you don't like but is true and feedback that you don't like because it doesn't tell the story the way you want to tell it. I've received plenty of critiques that, given enough time, I see the error of my ways. But I've also received plenty of critiques that don't jibe with the story/character for me. Sometimes I can even see where they're coming from, I just disagree. Don't give yourself permission to ignore ALL feedback - after all, you're trying to make this the best story it can be - but do give yourself permission to ignore the feedback that doesn't feel right.
So be picky. Be choosy.
When I first started receiving feedback on my writing, I thought that if someone said something it must be true. Which meant it must be changed. So if someone said, "This scene is dumb, take it out," I took it out. And if someone said "I don't like this character, give her blue hair," I gave her blue hair. That's what feedback is for, right? At some point our editorial vision turns myopic and we can't see the forest for the trees, so we ask others to read our work and tell us when we've jumped the shark (maybe literally).
As you might imagine, this eventually put me in a really frustrating cycle. I'd change something for one critique partner and another would say they hated the change. I'd change it back and a third reviewer would say I should go in an entirely new direction. I had so many voices in my head that I couldn't hear my own, and my story fell apart in revisions. I actually walked away from a manuscript - probably the best thing I've written to date - because I didn't even know what I wanted it to be anymore. I'd put it through too many critiques by too many people in too many rounds. My beautiful jello mould had melted into a glob of hot mess.
I took a very different approach with critiques on my current manuscript. I restricted the number of reviewers and made sure they were a diverse enough group to catch 90% of the plotting or characterization mistakes I made. I took notes on each round of critiques (we critique a few chapters at a time) and then let them sit for several weeks. I didn't make changes, I didn't read through the notes, I went and distracted myself in other ways. Then, when the little critiques started to add up to big picture changes for me, I went back and made the changes I wanted to make.
Yeah, read that again. I'll even bold it for you. I made the changes I wanted to make.
If I didn't like the feedback? I didn't change it.
If I didn't agree with the feedback? I didn't change it.
If I got conflicting feedback? I chose the one I agreed with and made the changes.
If I could understand the point of the feedback but wanted to take the story in a different direction? I didn't change it.
This is your story at the end of the day. You have to tell the story you want to tell, which means you get to pick and choose the changes you make. You own the story, so you're responsible for the choices it makes. You ask for feedback to point out what you can't see, but that doesn't mean everything they see is right for the story you are trying to tell.
A point of clarification: I draw a distinction between feedback that you don't like but is true and feedback that you don't like because it doesn't tell the story the way you want to tell it. I've received plenty of critiques that, given enough time, I see the error of my ways. But I've also received plenty of critiques that don't jibe with the story/character for me. Sometimes I can even see where they're coming from, I just disagree. Don't give yourself permission to ignore ALL feedback - after all, you're trying to make this the best story it can be - but do give yourself permission to ignore the feedback that doesn't feel right.
So be picky. Be choosy.
Subscribe to:
Posts (Atom)
