I'm going to assume that everyone else's first of the year is just as busy as mine, if for no other reason than to excuse myself for not having posted the last few weeks. I've been buried under mountains of work, and will continue to be buried for the next couple of weeks. But I promise to return with all kinds of fun posts about stuff I haven't even thought of yet. That's how prepared I am.
Hope your January is going well!
Wednesday, January 25, 2012
Friday, January 6, 2012
This could be the last 2012 EVAR
It's a new year, gentle readers, according to my calendar. I'm having a private detective follow up on these claims that it's January, as I'm highly suspicious, but until they come back with proof that October 2011 never actually happened (because SERIOUSLY), I have no choice but to believe it.
Mayan calendars aside, I'm looking forward to 2012. I learned some valuable lessons in 2011 about myself, my writing, and my amazing capacity for eating Mexican food. I plan to learn more, share more, explore more, and for sure eat more. I'm not really a New Year's Resolutions kind of girl, but I am a fresh starts kind of girl. So every January 1st is a chance at a fresh start, a renewed vigor for capturing the goals we set for ourselves the year before.
What are your goals for 2012? What are you proud of accomplishing in 2011? Do you also share my intense love of beans that have been fried TWICE!?!
Mayan calendars aside, I'm looking forward to 2012. I learned some valuable lessons in 2011 about myself, my writing, and my amazing capacity for eating Mexican food. I plan to learn more, share more, explore more, and for sure eat more. I'm not really a New Year's Resolutions kind of girl, but I am a fresh starts kind of girl. So every January 1st is a chance at a fresh start, a renewed vigor for capturing the goals we set for ourselves the year before.
What are your goals for 2012? What are you proud of accomplishing in 2011? Do you also share my intense love of beans that have been fried TWICE!?!
Friday, December 16, 2011
I really just used this sentence
"The egregious breaches of grammar protocol are fun!"
Happy Friday, gentle readers.
Happy Friday, gentle readers.
Wednesday, December 14, 2011
Dream a little dream
Or conversely, The Importance of Being Dreamist. I should warn you, this is a long rambling post with lots of parenthetical statements (as I am wont to do), so maybe grab a cup of coffee before you start in on it.
I get a little soft-eyed around the holidays, with the weather turning grayer and the fireplace more inviting, and the end of yet another year looming fast. You really only get six days to think about the impending new year after Christmas, which isn't much time to pack in those end of year specials the networks love. So I start my own personal JEMiniscing (see what I did there?) a little early.
This year, I've discovered that trying to be an author is HARD. Plotting a book is hard, finding the right words to convey your story is hard, sharing that story with others is hard, editing is hard, querying is hard, and I'm sure it's just as hard to try and get that book published and loved by the general audience. I hope to find out some day. But the hardest part of all of this, at least for me, is keeping my spirits up during this whole process. When taken as a whole it seems an insurmountable task to actually write and publish a book that people will love. And standing at the beginning of a new story, starting all over, is kind of like trying to love again after a failed marriage. You're not even sure you're ready to trust someone new, and SNIs have a funny way of luring you in and then betraying you after 60,000 words.
I've run up against this mountain of a molehill a lot this year. I finished a manuscript that I hoped was ready for querying, and have spent the better part of this year editing, writing queries, revising said queries, sending my work out to everyone I could trust/bother to tell me how to make it better, and sending out queries. I didn't have a spare moment for any new stories, and when I tried writing them they floundered after a couple hundred words. I needed all of my energy for the book I wanted to query.
But I found out soon enough that the energy wasn't there. Every query felt like a hundred ton weight around my neck. The research, the personalizing, the endless editing, only to get a form rejection after 30 minutes (or never hearing back again). I knew this was part of the process, and I haven't given up, but it took a lot of the fun out of the story, and I found myself questioning every decision I ever made (should she really have eaten chicken soup?!?). I consider myself a pretty strong person, but I started questioning why I thought writing was the path for me in the first place.
I took a step back from the whole process a couple of weeks ago to collect myself and my thoughts and devise a new game plan. And what I discovered is that I need dreams. All day, all night, staring out the window type dreams. I need stories that fill my head with people who seem more real to me than my own best friends. Stories that whisk me away from gloomy days to even gloomier days with dark and stormy nights and tall handsome strangers. I need to be a princess, a warrior, a gypsy, a thief, maybe even a tramp. My poor little grinch heart feeds on dreams, and I was starving myself.
I started writing again. I started at page one, word one, and let myself dream. And now, even though the querying is still hard and the plotting trips me up (but how do I get them OUT of the cave?), I'm happy. I'm entertained, and I'm renewed in my efforts to fight for these characters to share their story somehow, some way. I've unstoppered the bottle and let the genie out, and he's running amok with my imagination. I think they're planning a timeshare in the Poconos.
So my advice to you, no matter where you are in the journey, is to keep dreaming. Dream all day, dream all night, ignore your emails and celebrity gossip sites and laundry and just dream. And if that doesn't work, just dance.
Monday, December 5, 2011
Overprotecting your characters
I have a tendency to overprotect my MCs. They are my little cacti - I spend so much time nurturing them, pruning them into the perfect shape with just enough soil and a cute decorated pot, that I don't want to mess them up. I'm not going to put my delicate little cacti out in the desert, do you know what lives out there? Lizards and cow bones, if I believe every western movie I've ever seen. And it's hot, and animals eat their delicious buds. No no no, not for my little cacti.
The problem with that mentality is that cacti are supposed to live in the desert. They are supposed to survive the heat and get their little buds eaten and hang out with cow bones. And literary characters are supposed to get in trouble. They're supposed to struggle and fail and get threatened by evil villains. That's what makes them interesting to follow for 300+ pages.
But when we get so attached to our characters, we sometimes do them (and the story) a disservice by protecting them from bad things. My critique group recently discussed a YA piece in which the MC struggles with being in love with her best friend. She has such a history with the guy that it breaks her heart to see him go out with other girls. The problem with the story is that we didn't get any of that history, so as a reader I didn't understand how he was breaking her heart. I knew they had a history, but without seeing it I couldn't experience the MC's pain.
Turns out, my critique partner was so concerned with protecting her MC from that hurt that she didn't allow the MC to show us that pain. She shielded the MC from reliving the past hurts, which meant we as the readers didn't get to see them, either. The writer knew them perfectly, but didn't share. As a reader, I needed to live through those moments with the character, I needed to hurt with her. It was the only way I was going to feel as shaky and defensive against him in the present as the MC does.
I'm not innocent in this whole scenario, either. In one of my earlier manuscripts, a beta reader of mine gave me some of the most helpful feedback that I've ever received, and that I've tried to carry through my future work: he told me that he always knew my character was safe. Even when she was in the most dire of situations - and believe me, they were dire - he knew she would get free. Something about the way I wrote the scenes, the way I overempowered her, broke the tension of scene. Sure, she's trapped, but we know she's going to get free. There wasn't any urgency to it.
So now I fight that need to save my character. They're supposed to be in trouble, that's why I'm writing about them. And even if I am going to save them, it shouldn't be obvious how. And they might not escape without a few scrapes or a broken heart. Oooor, they might not escape at all...
Do you overprotect your characters? Or do you enjoy torturing them even more?
The problem with that mentality is that cacti are supposed to live in the desert. They are supposed to survive the heat and get their little buds eaten and hang out with cow bones. And literary characters are supposed to get in trouble. They're supposed to struggle and fail and get threatened by evil villains. That's what makes them interesting to follow for 300+ pages.
But when we get so attached to our characters, we sometimes do them (and the story) a disservice by protecting them from bad things. My critique group recently discussed a YA piece in which the MC struggles with being in love with her best friend. She has such a history with the guy that it breaks her heart to see him go out with other girls. The problem with the story is that we didn't get any of that history, so as a reader I didn't understand how he was breaking her heart. I knew they had a history, but without seeing it I couldn't experience the MC's pain.
Turns out, my critique partner was so concerned with protecting her MC from that hurt that she didn't allow the MC to show us that pain. She shielded the MC from reliving the past hurts, which meant we as the readers didn't get to see them, either. The writer knew them perfectly, but didn't share. As a reader, I needed to live through those moments with the character, I needed to hurt with her. It was the only way I was going to feel as shaky and defensive against him in the present as the MC does.
I'm not innocent in this whole scenario, either. In one of my earlier manuscripts, a beta reader of mine gave me some of the most helpful feedback that I've ever received, and that I've tried to carry through my future work: he told me that he always knew my character was safe. Even when she was in the most dire of situations - and believe me, they were dire - he knew she would get free. Something about the way I wrote the scenes, the way I overempowered her, broke the tension of scene. Sure, she's trapped, but we know she's going to get free. There wasn't any urgency to it.
So now I fight that need to save my character. They're supposed to be in trouble, that's why I'm writing about them. And even if I am going to save them, it shouldn't be obvious how. And they might not escape without a few scrapes or a broken heart. Oooor, they might not escape at all...
Do you overprotect your characters? Or do you enjoy torturing them even more?
Monday, November 21, 2011
Confession session
Okay, I can't beat Usher's confessions (she's got a what on the way?!), but still. I've got some things to get off my chest.
1) I see peanuts at the grocery store in the unsalted and lightly salted varieties and I want to know where the heavily salted option is. I like my legumes with a flavor of high blood pressure.
2) I like to collect random skillsets. I've worked as a barista learning coffee craftsmanship, I'm preparing for a black belt test in Taekwondo, I've flown a plane, I'm handy with ProTools recording software, and I can find my way around any subway system in the world. Next I've got my eye on glass blowing and archery.
3) Thank you, Facebook, for allowing me to spy on high school acquaintances without the awkward name tags and fruit punch of a reunion. Also, thanks for giving me enough info about my high school crushes to know how much I don't regret the past.
4) I love Disney movies. And I'm not talking about the classics - although I love those - I'm talking about Disney Channel movies. Avalon High, High School Musical, The Even Stephens Movie, Cadet Kelly - I've seen them, and I love them. And I also think I could do a better job of writing them. Which is probably a lie.
5) A coworker of mine brought in some satsumas for the entire office and I've eaten at least 70% of them. I also took a bag home with me. I should feel shame, but I don't.
Happy Thanksgiving!
1) I see peanuts at the grocery store in the unsalted and lightly salted varieties and I want to know where the heavily salted option is. I like my legumes with a flavor of high blood pressure.
2) I like to collect random skillsets. I've worked as a barista learning coffee craftsmanship, I'm preparing for a black belt test in Taekwondo, I've flown a plane, I'm handy with ProTools recording software, and I can find my way around any subway system in the world. Next I've got my eye on glass blowing and archery.
3) Thank you, Facebook, for allowing me to spy on high school acquaintances without the awkward name tags and fruit punch of a reunion. Also, thanks for giving me enough info about my high school crushes to know how much I don't regret the past.
4) I love Disney movies. And I'm not talking about the classics - although I love those - I'm talking about Disney Channel movies. Avalon High, High School Musical, The Even Stephens Movie, Cadet Kelly - I've seen them, and I love them. And I also think I could do a better job of writing them. Which is probably a lie.
5) A coworker of mine brought in some satsumas for the entire office and I've eaten at least 70% of them. I also took a bag home with me. I should feel shame, but I don't.
Happy Thanksgiving!
Wednesday, November 9, 2011
Sometimes we need a little backstory
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!
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!
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.
Subscribe to:
Posts (Atom)
