I have to admit, when I first heard this was a book about a doll made out of the bones of a murdered girl, I wasn't interested. I believe I shuddered, actually. But curiosity, the fact that this is done for a MG audience, and Newbery buzz combined to make me pick it up. And I'm glad I did.
Zach, Poppy, and Alice have been friends forever, and even though they are now twelve, they continue to role-play with action figures to the point that their fantasy storyline has gotten very elaborate and absorbing. They are not just misfit kids who have no other friends, though. Zach, the POV character, is also an up-and-coming basketball player, growing up into a handsome kid (though he doesn't see this himself), and loves the sense of belonging he gets from his teammates. Zach's dad, who is suffering hurts of his own, decides that the time has come for Zach to put away childish things, and since Zach isn't inclined, he'll do it for him: He throws out all Zach's action figures. Zach, angry, embarrassed, and suspecting maybe he should be ashamed, refuses to tell the girls what happened. Instead, he turns his anger on them and tells them he can't play anymore. That's it. The end. Finis. It's when Poppy gets The Queen -- her mother's antique doll made of bone china -- out of its glass case in a dramatic attempt to get Zach to change his mind that ghostly things begin to happen. In short, the doll convinces the kids, particularly the loud and dramatic Poppy, that she is the bones and ash of a murdered girl, and unless they take her to her grave, where the rest of her remains are buried, she will make their lives miserable.
From there, they go on a road trip in an effort to accomplish the quest. I'm not going to detail the plot much more, to avoid spoilers, but this book is at heart a friendship story. Where the novel really shines is in its delineation of the relationships between all three kids and how each one is changing and fears change in the others. The adventurous plot is a wonderful vehicle for this exploration, and there are some great quotes such as the one by Zach's dad when they reconcile: "I thought you needed to be tougher. But I've been thinking that protecting somebody by hurting them before someone else gets the chance isn't the kind of protecting that anybody wants." I'm also fascinated by the history of bone china, which is touched on and may or may not have been the impetus for this story.
I had a couple of minor quibbles with the book. It absolutely turns on the fact that Zach wouldn't explain to his friends why he wouldn't play the game anymore, and I wasn't fully convinced he would keep that secret for as long as he did. And, for me, the quest portion bogged down a bit until it suddenly got irresistibly exciting. In fact, I came this close to putting the book down, but I'm really glad I didn't. A very good novel, worthy of its Newbery Honor.
Thursday, February 6, 2014
Thursday, January 30, 2014
Soapbox Series #8 (or Reading, 'Riting, Ranting) -- Write What You Love, Even if it's a Vampire Werewolf Dystopian Love Triangle?
My goodness, I haven't ranted in a while. Let me rectify this oversight! :)
I have seen the following question asked in a couple of different places. It goes something like this: "I'm working on a novel, and (a) it's in a genre everybody knows is overcrowded but I love this idea, or (b) I just found out that two books very much like it are coming out next year. Should I write it anyway, or should I shelve this book even though I love it?"
It probably comes as no surprise that the usual, very passionate, advice is "Write what you love!"
And I couldn't agree more! What troubles me, though, is the implied corollary: "If you love it, you must write it. If you love it, that's justification enough." I dunno. I wonder if it wouldn't be more accurate to say "Love what you write!" As in, yes, I will commit to a project only if I love it. Only if I think it's "mine" to write. Only if it really taps into my heart. But does it follow that if I feel this way about a project, I must write it, even if there are reasons to consider not doing so?
No. In the first place, most writers are already in a position where they will never write all the ideas they love: There are too many for one lifetime. So while love is necessary, it's not enough to assure that any particular idea moves from the "great ideas" file to the "finished manuscripts" file. To wax mathematical for a moment, love for an idea or story is a necessary but not sufficient condition.
Unless you know you are writing a practice novel, I don't see how "Never mind the market and just go for it!" is the best advice. In days of yore, after selling a MG series written in third person, I started a mystery series in first person. The MC decided she was going to speak for herself, thank you very much. "No," my editor on the first series said. "We don't do first person." Period. Even if I loved the project, or had done it well, it still wasn't marketable to that house. Fortunately, I was able to sell it elsewhere, but that doesn't change the fact that love doesn't conquer all. It's a necessary, but not sufficient, condition.
More recently, I caught "the last train out of the station" with a certain genre. I wasn't thinking about what was popular or unpopular in the market. I'd just found a great idea and dove into passionate work on it. I was about 3/4 done with the book when I started hearing that this genre was saturated. What's more, I found out that two other books on my specific subject within that genre were scheduled to come out within the following year to year-and-a-half. No, those agents were not going to take on what was essentially a competing book, nor were those publishers. My book's competition was too direct, and there wasn't room for another, especially since it was a latecomer. My love for the project could not change that.
Many would encourage the writer to stick with a project by saying, "Your book will be completely different from the other book because you are a different writer!" Well, maybe it will and maybe it won't. No one can blithely promise you that your book will be completely different. There can be uncanny resemblances between your work and somebody else's. And some topics in themselves are too specific to stand much competition.
I think "Write what you love/write what will sell" is a false dichotomy. I insist that the twain shall meet. I want to write salable work, and I'm willing to tweak both the love and the market aspects so that I'm writing something I love and that isn't market-handicapped. It just seems to me that since I love a lot of different books, there's always a new idea to love, and in the end I can have my story and (hopefully) sell it, too.
I have seen the following question asked in a couple of different places. It goes something like this: "I'm working on a novel, and (a) it's in a genre everybody knows is overcrowded but I love this idea, or (b) I just found out that two books very much like it are coming out next year. Should I write it anyway, or should I shelve this book even though I love it?"
It probably comes as no surprise that the usual, very passionate, advice is "Write what you love!"
And I couldn't agree more! What troubles me, though, is the implied corollary: "If you love it, you must write it. If you love it, that's justification enough." I dunno. I wonder if it wouldn't be more accurate to say "Love what you write!" As in, yes, I will commit to a project only if I love it. Only if I think it's "mine" to write. Only if it really taps into my heart. But does it follow that if I feel this way about a project, I must write it, even if there are reasons to consider not doing so?
No. In the first place, most writers are already in a position where they will never write all the ideas they love: There are too many for one lifetime. So while love is necessary, it's not enough to assure that any particular idea moves from the "great ideas" file to the "finished manuscripts" file. To wax mathematical for a moment, love for an idea or story is a necessary but not sufficient condition.
Unless you know you are writing a practice novel, I don't see how "Never mind the market and just go for it!" is the best advice. In days of yore, after selling a MG series written in third person, I started a mystery series in first person. The MC decided she was going to speak for herself, thank you very much. "No," my editor on the first series said. "We don't do first person." Period. Even if I loved the project, or had done it well, it still wasn't marketable to that house. Fortunately, I was able to sell it elsewhere, but that doesn't change the fact that love doesn't conquer all. It's a necessary, but not sufficient, condition.
More recently, I caught "the last train out of the station" with a certain genre. I wasn't thinking about what was popular or unpopular in the market. I'd just found a great idea and dove into passionate work on it. I was about 3/4 done with the book when I started hearing that this genre was saturated. What's more, I found out that two other books on my specific subject within that genre were scheduled to come out within the following year to year-and-a-half. No, those agents were not going to take on what was essentially a competing book, nor were those publishers. My book's competition was too direct, and there wasn't room for another, especially since it was a latecomer. My love for the project could not change that.
Many would encourage the writer to stick with a project by saying, "Your book will be completely different from the other book because you are a different writer!" Well, maybe it will and maybe it won't. No one can blithely promise you that your book will be completely different. There can be uncanny resemblances between your work and somebody else's. And some topics in themselves are too specific to stand much competition.
I think "Write what you love/write what will sell" is a false dichotomy. I insist that the twain shall meet. I want to write salable work, and I'm willing to tweak both the love and the market aspects so that I'm writing something I love and that isn't market-handicapped. It just seems to me that since I love a lot of different books, there's always a new idea to love, and in the end I can have my story and (hopefully) sell it, too.
Thursday, January 23, 2014
Writer Marathon Soup
Too busy writing to cook? Need sustenance during your writing retreat that you can "just grab" and that's also healthy? Try my Writer Marathon Soup. Amounts here are approximate, and you can make any substitutions or omissions you like. On the eve of a two- or three-day "writer immersion" event, spend about 40 minutes putting this soup together, and it can feed two or three people for the duration.
Writer Marathon Soup
4 boneless, skinless chicken breasts
1-2 cartons chicken broth
1 can kidney beans
1 can white beans
1 can black beans
1 can green beans
1 can petite diced tomatoes
1-2 chopped onions
1/2 lb. baby carrots, cut if desired
2-3 ribs chopped celery
1/2 bag frozen veggies such as peas, corn, or green beans
water
basil
garlic powder
lemon pepper
Italian seasoning
1. Place chicken breasts in microwave-safe casserole. Cover and microwave 20 minutes on high for frozen. Fresh will be somewhat less.
2. Meanwhile, plug in or set on stovetop a large Dutch oven. Add to it the broth and canned items. Set heat to medium or medium low.
3. Prepare the onions, carrots, and celery, and put them plus any frozen veggies you're using in a microwave-safe casserole or bowl big enough to accommodate them. Add a little water.
4. When your chicken is done, take it out of the microwave and put the dish of veggies in. Cover the veggies and microwave on high till done, about 7-8 minutes or done to your liking. While the veggies are cooking, cube chicken and add to Dutch oven. Using a colander or strainer, you may want to add any chicken broth from the casserole to the pot as well.
5. When the veggies are done, add them plus the water from their cooking dish to the soup pot.
6. Add enough water to make your pot as full as practicable.
7. Add your seasonings in any amounts you wish.
You can now heat this soup through and serve, or refrigerate for later. I also do the dishes as I go, so by the time the pot's in the fridge, or within minutes after, they're all stacked in the dish drainer. You can vary this basic recipe and method so freely that the soup can be different each time you make it. Perfect for these cold winter days! :)
Writer Marathon Soup
4 boneless, skinless chicken breasts
1-2 cartons chicken broth
1 can kidney beans
1 can white beans
1 can black beans
1 can green beans
1 can petite diced tomatoes
1-2 chopped onions
1/2 lb. baby carrots, cut if desired
2-3 ribs chopped celery
1/2 bag frozen veggies such as peas, corn, or green beans
water
basil
garlic powder
lemon pepper
Italian seasoning
1. Place chicken breasts in microwave-safe casserole. Cover and microwave 20 minutes on high for frozen. Fresh will be somewhat less.
2. Meanwhile, plug in or set on stovetop a large Dutch oven. Add to it the broth and canned items. Set heat to medium or medium low.
3. Prepare the onions, carrots, and celery, and put them plus any frozen veggies you're using in a microwave-safe casserole or bowl big enough to accommodate them. Add a little water.
4. When your chicken is done, take it out of the microwave and put the dish of veggies in. Cover the veggies and microwave on high till done, about 7-8 minutes or done to your liking. While the veggies are cooking, cube chicken and add to Dutch oven. Using a colander or strainer, you may want to add any chicken broth from the casserole to the pot as well.
5. When the veggies are done, add them plus the water from their cooking dish to the soup pot.
6. Add enough water to make your pot as full as practicable.
7. Add your seasonings in any amounts you wish.
You can now heat this soup through and serve, or refrigerate for later. I also do the dishes as I go, so by the time the pot's in the fridge, or within minutes after, they're all stacked in the dish drainer. You can vary this basic recipe and method so freely that the soup can be different each time you make it. Perfect for these cold winter days! :)
Subscribe to:
Posts (Atom)
