Title: Graceling
Author: Kristin Cashore
Genre: YA Fantasy
Published: 2008
Content Rating: R for sex (this surprised me actually; though it's written in such a way that if you didn't know much about sex, you might have no idea that's what they were doing)
Graced with an unnatural ability to kill, Katsa has been her royal uncle's thug and assassin since she was little. Over the years, she has grown to regret what she has become and begun to work against some of her uncle's bullying. On one such mission, she meets a Graced fighter named Po, and gets drawn into a rescue on the far side of the world, against a man with a more frightening power than any the world has known.
At first, I was a little jaded by this book. Katsa seemed a lot like Katniss from that other book I read -- both of them killers who don't want to be killers. Both of them beautiful, but totally oblivious to their beauty. (I realize this comparison is totally unfair, as these two books came out within a month of each other, but you have to admit their names are really similar). Where it got interesting for me was when Katsa started spending time with Po, and they began learning more about each other's powers.
The climax was less...explosive than I expected, but that doesn't mean I didn't like it. In contrast, the resolution felt long, but it was exactly what I wanted, plus a twist. (Maybe what I wanted was a book about Po?).
But my favorite, favorite thing about this book was the dialog. I laughed out loud so many times at the dry, clever humor of Katsa, Raffin, Oll, and Po. I'd read a whole book with nothing but Katsa's secret missions, just to hear the four of them take jabs at each other.
Overall, I thought this was a good fantasy adventure with a well-developed (if small) world and clever characters. I'd buy a sequel (or maybe the prequel).
Books I Read: Graceling
—
June 25, 2010
(5
comments)
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
books I read,
fantasy,
YA
Flashbacks (and Cunning Folk Excerpts!)
—
June 23, 2010
(8
comments)
Flashbacks are hard. Why? Because they're about the past and are, therefore, backstory infodump. On top of that, they're really easy to screw up. So here are some tips I've learned to keep from giving the reader flashback whiplash.
Keep it relevant. This is the same as the rule for infodumps. Only tell them what they need to know to understand this part of the story. This is especially true in beginnings, when we don't know the characters or their conflicts yet. The last thing we want to do is jump back into the past and get to know even more characters and conflicts.
Keep it short. Or rather, only make it as long as it needs to be (really, this is just an extension of the first tip). For example, the flashback below (in italics) is only 10 words long:
Don't be heavy-handed. When I first started writing, I thought I had to make the flashback obvious. Like this:
Can you hear the Wayne's World flashback sound? Don't do this. As long as the reader can tell you're going into a flashback, you can just jump right in: "Five minutes to curtain, and Steve was nervous. The first time he played on stage..."
Same with when the flashback ends. Don't toss in a handful of sentences about Steve looking at the guitar and "remembering where he was." Jump right in. Have a stagehand or something (who was not in the flashback) say, "Steve? It's time," and then Steve goes on stage to his legions of fans. So long as the present is sufficiently different from the past, the reader will have no problem keeping up.
Don't worry about tense. I mean, do worry about tense, cuz you're a writer. But don't feel like it has to be perfect. Technically, when you're writing about the past of the past, you're supposed to use "had" a lot (past perfect tense, for you grammarians). "Steve's first time on stage, he had tripped over his bellbottoms." But in practice, doing this for every single verb is annoying.
Instead, use "had" near the beginning of the flashback as a clue to the reader, but then don't be afraid to back off. Mostly, you only need "had" when the reader might be confused as to when the action took place (i.e. in the present, or in the flashback). "Steve's first time on stage, he tripped over his bellbottoms." See? No confusion.
Okay, for those of you still with me, I have a (multi-paragraph) excerpt from my current work-in-progress. It's a flashback that uses all of these tips...hopefully. If I screwed it up, acting like a better writer than I am, I'm really, really sorry.
Keep it relevant. This is the same as the rule for infodumps. Only tell them what they need to know to understand this part of the story. This is especially true in beginnings, when we don't know the characters or their conflicts yet. The last thing we want to do is jump back into the past and get to know even more characters and conflicts.
Keep it short. Or rather, only make it as long as it needs to be (really, this is just an extension of the first tip). For example, the flashback below (in italics) is only 10 words long:
(from Cunning Folk)How could Suriya lose control like that? Aunt Pern had told her how, as a baby, Suriya’s fire kept them warm at night, but that was a long time ago. For as long as she could remember, Suriya had been able to control her power, even in her sleep – to the point where releasing was difficult simply because she never did it.
Don't be heavy-handed. When I first started writing, I thought I had to make the flashback obvious. Like this:
Five minutes to curtain, and Steve was nervous. He stared at the guitar in his hand--the same guitar he'd played with for ten years. It reminded him of the first time he played on stage...
Can you hear the Wayne's World flashback sound? Don't do this. As long as the reader can tell you're going into a flashback, you can just jump right in: "Five minutes to curtain, and Steve was nervous. The first time he played on stage..."
Same with when the flashback ends. Don't toss in a handful of sentences about Steve looking at the guitar and "remembering where he was." Jump right in. Have a stagehand or something (who was not in the flashback) say, "Steve? It's time," and then Steve goes on stage to his legions of fans. So long as the present is sufficiently different from the past, the reader will have no problem keeping up.
Don't worry about tense. I mean, do worry about tense, cuz you're a writer. But don't feel like it has to be perfect. Technically, when you're writing about the past of the past, you're supposed to use "had" a lot (past perfect tense, for you grammarians). "Steve's first time on stage, he had tripped over his bellbottoms." But in practice, doing this for every single verb is annoying.
Instead, use "had" near the beginning of the flashback as a clue to the reader, but then don't be afraid to back off. Mostly, you only need "had" when the reader might be confused as to when the action took place (i.e. in the present, or in the flashback). "Steve's first time on stage, he tripped over his bellbottoms." See? No confusion.
Okay, for those of you still with me, I have a (multi-paragraph) excerpt from my current work-in-progress. It's a flashback that uses all of these tips...hopefully. If I screwed it up, acting like a better writer than I am, I'm really, really sorry.
(SETUP: It's Suriya's first morning after losing her Aunt Pern and after being chased by bounty hunters through the streets of Chiang Mai.)
No dreams. Thank God.
When Suriya was very little, they had lived in a village where people knew what she was and for a while even liked her. Because of her dreams.
The village was called Umong. Suriya couldn't have been more than six years old at the time – old enough to realize her dreams meant something, too young to keep them to herself. It started when she saved an old man's life. She dreamed he had been crushed by a falling tree. Later that day, when Suriya saw her dream was about to happen, she cried out.
The tree missed the old man by a hand's width.
He had thanked her. The whole village had thanked her. They gave her gifts and roasted pigs in her honor.
Then they wanted their own dreams. Almost every morning, they came to ask what she had seen in the night. She told them with the innocence of a child.
Some nights she had no dreams, and the villagers' reactions frightened her. Sometimes she even lied about her dreams just to make people happy.
Other nights she didn't dream enough. She had seen one man – she still remembered his name was Danilay – lying dead on the ground, but she didn't know where or how. Danilay got mad. He shook her and slapped her until Aunt Pern had intervened.
They left Umong that night. She never found out how or even if her dream came true. And she never told her dreams again to anyone, except Aunt Pern.
Aunt Pern. Oh, God.
Suriya jerked upright. She was still in the strange guesthouse. A soft light filtered through the curtains. Anna sat on the stool watching the morning news.
“Good morning,” Anna's voice came into her mind. She didn't turn away from the TV.
When Suriya was very little, they had lived in a village where people knew what she was and for a while even liked her. Because of her dreams.
The village was called Umong. Suriya couldn't have been more than six years old at the time – old enough to realize her dreams meant something, too young to keep them to herself. It started when she saved an old man's life. She dreamed he had been crushed by a falling tree. Later that day, when Suriya saw her dream was about to happen, she cried out.
The tree missed the old man by a hand's width.
He had thanked her. The whole village had thanked her. They gave her gifts and roasted pigs in her honor.
Then they wanted their own dreams. Almost every morning, they came to ask what she had seen in the night. She told them with the innocence of a child.
Some nights she had no dreams, and the villagers' reactions frightened her. Sometimes she even lied about her dreams just to make people happy.
Other nights she didn't dream enough. She had seen one man – she still remembered his name was Danilay – lying dead on the ground, but she didn't know where or how. Danilay got mad. He shook her and slapped her until Aunt Pern had intervened.
They left Umong that night. She never found out how or even if her dream came true. And she never told her dreams again to anyone, except Aunt Pern.
Aunt Pern. Oh, God.
Suriya jerked upright. She was still in the strange guesthouse. A soft light filtered through the curtains. Anna sat on the stool watching the morning news.
“Good morning,” Anna's voice came into her mind. She didn't turn away from the TV.
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
Cunning Folk,
writing samples,
writing tips
¡Viva la Revolución!
—
June 21, 2010
(8
comments)
(This post brought to you by the inspiration and revolutionary cake of L. T. Host, the Jokerman font, and That Thing Where I DrawPhotoshop)
I'm seeing a pattern. My first novel generated no requests. My second novel is getting partial requests, but no fulls (so far). I fear my third novel will generate fulls but no offers--those will come with my fourth novel.
And then what? Will I have to write yet another novel before I get a book deal? To that I say: NO!
Down with our (imaginary) oppressors! We will not have to write three more novels. THIS is the novel that will be published.
No more slush pile! Representation for everyone!
VIVA LA REVOLUCIÓN!!
* CARPE EDITIO: Seize the book deal (or, if you want to be literal, "the publishing of a book.").
I'm seeing a pattern. My first novel generated no requests. My second novel is getting partial requests, but no fulls (so far). I fear my third novel will generate fulls but no offers--those will come with my fourth novel.
And then what? Will I have to write yet another novel before I get a book deal? To that I say: NO!
Down with our (imaginary) oppressors! We will not have to write three more novels. THIS is the novel that will be published.
No more slush pile! Representation for everyone!
VIVA LA REVOLUCIÓN!!
* CARPE EDITIO: Seize the book deal (or, if you want to be literal, "the publishing of a book.").
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
business of writing,
fun,
temporary insanity
Boy Books on Ink Spells
—
June 18, 2010
(12
comments)
From Blue Like Jazz, by Donald Miller:
I talk about boy books over at Susan Quinn's place. Check it out.
I understand you can learn a great deal about girldom by reading Pride and Prejudice, and I own a copy, but I have never read it. I tried. It was given to me by a girl with a little note inside that read: What is in this book is the heart of a woman.
I am sure the heart of a woman is pure and lovely, but the first chapter of said heart is hopelessly boring. Nobody dies at all.
I talk about boy books over at Susan Quinn's place. Check it out.
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
books I read,
boy books,
YA
Books I Read: Jonathan Strange and Mr. Norrell
—
June 16, 2010
(10
comments)
Title: Jonathan Strange & Mr. Norrell
Author: Susanna Clarke
Genre: Fantasy
Published: 2004
Content Rating: PG (there are a couple mildly freakish bits, like a woman's finger in a box, or dead men brought back to life, but nothing I wouldn't let my (older) kids read)
In early 19th-century England, the great magic of Merlin and the Raven King has disappeared. The only magicians left are merely theoretical -- men who call themselves magicians, but are more akin to historians than anything -- until Mr. Norrell. He's a stuffy, controlling, arrogant little man, but also a practical magician. And he desperately wants to restore magic to England. He is moderately successful when Jonathan Strange applies to be his pupil. Where Norrell is academic, Strange is showy and charismatic, and where Norrell fears the most powerful kinds of magic -- that of the faeries -- Strange believes that is who they should learn from most.
My friend who gave this to me characterized it as "Sense and Sensibility and Sorcery". What shines about this book are the two main characters and their relationship, both as friends and enemies. The story is as funny and charming as Strange, and as stuffy and academic as Norrell. By the latter, I mean that the story frequently tangents into vignettes of English magical history. For example, Norrell and Strange will be arguing about whether the Raven King is really gone forever, and Strange will say something like, "There are stories of people having seen him. What about the conquistador, the farmer in Yorkshire, or the girl in Manchester," and each of those will have a (sometimes very long) footnote relating the story he refers to.
These infodumps are very much part of the style of the book. They are very enjoyable, and they made the alternate history that much more believable, but there were times when I was tempted to skip them and continue with the story. (Oh, but you can't skip them. That's the secret.) This is not a thriller or a fast read (though it has a few exciting and frightening bits). This is a book to live in for a while, and to believe sometimes that maybe magic is real.
Author: Susanna Clarke
Genre: Fantasy
Published: 2004
Content Rating: PG (there are a couple mildly freakish bits, like a woman's finger in a box, or dead men brought back to life, but nothing I wouldn't let my (older) kids read)
In early 19th-century England, the great magic of Merlin and the Raven King has disappeared. The only magicians left are merely theoretical -- men who call themselves magicians, but are more akin to historians than anything -- until Mr. Norrell. He's a stuffy, controlling, arrogant little man, but also a practical magician. And he desperately wants to restore magic to England. He is moderately successful when Jonathan Strange applies to be his pupil. Where Norrell is academic, Strange is showy and charismatic, and where Norrell fears the most powerful kinds of magic -- that of the faeries -- Strange believes that is who they should learn from most.
My friend who gave this to me characterized it as "Sense and Sensibility and Sorcery". What shines about this book are the two main characters and their relationship, both as friends and enemies. The story is as funny and charming as Strange, and as stuffy and academic as Norrell. By the latter, I mean that the story frequently tangents into vignettes of English magical history. For example, Norrell and Strange will be arguing about whether the Raven King is really gone forever, and Strange will say something like, "There are stories of people having seen him. What about the conquistador, the farmer in Yorkshire, or the girl in Manchester," and each of those will have a (sometimes very long) footnote relating the story he refers to.
These infodumps are very much part of the style of the book. They are very enjoyable, and they made the alternate history that much more believable, but there were times when I was tempted to skip them and continue with the story. (Oh, but you can't skip them. That's the secret.) This is not a thriller or a fast read (though it has a few exciting and frightening bits). This is a book to live in for a while, and to believe sometimes that maybe magic is real.
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
books I read,
fantasy
Good Cause Giveaway and Last Minute Questions
—
June 14, 2010
(3
comments)
First, the questions. Then the giveaway. Asea asks: What's something you really love about living in Thailand?
A lot, actually. Except for the polluted hot season, it's beautiful. I love the rain, so the hundred million inches we get in the rainy season are actually pretty cool. The food is good. Everything is cheap. And there's not this underlying cultural pressure to PRODUCE, PRODUCE, PRODUCE! (That last one probably contributes to Thailand's weaker economy, but whatever).
Is reverse culture shock hard? (I struggle with it a lot.)
Sometimes it's hard, though it's probably made easier by the fact that I know I (most likely) won't be living there again. I don't know how to be more specific without sounding like I'm complaining about America. I like America, but sometimes it can be a bit overbearing about safety or how kids are raised, while at the same time not caring so much about what gets shown on TV (though that last one's not very fair; TV drives me batty in general).
TRANSITION!
Our friends, Aaron and Carrien Blue, are helping an orphanage near the Burmese border. The kids there are refugee orphans, whose parents have been lost or killed as a result of the genocide and fighting that has been going on in Burma for decades.
They have about 40 kids, but no truck. The kids have to walk to school everyday, about 3-4 miles on a fairly large street. If someone gets sick or hurt, they have to hire a truck to take them to the hospital, spending money which could be better spent on things like food, water, or medical bills.
So the Blues are trying to raise $6000 by the end of this week, so that when Aaron comes to visit he can buy them a truck as well. To that end, Carrien is giving away a bunch of cool stuff on her blog to anyone who donates or spreads the word.
Last I heard, they were at $3,280, which is AWESOME, but they still have a long way to go. This is a really great cause, guys. These kids are at risk in all kinds of ways, but giving them a home and education reduces that risk significantly. And a truck is a big help to that end.
So get over there. Any donation, any word spreading, will help these kids.
UPDATE: They're up to $4,519 now, and Carrien has added additional prizes to the giveaway. If you've already entered, you're eligible for these new prizes as well. If not, what the heck are you doing, get over there!
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
contests,
questions/answers,
Thailand
Why You Don't Write (and What To Do About It)
—
June 11, 2010
(16
comments)
Carrie* says: I'm relatively new to your website. I'm curious to hear on what are your thoughts in regards to writer's block.
* Who, I'm obligated to point out, is not Carrie Kei Heim Binas.
I hate it. But I think I know how to deal with it.
For the purposes of this post, writer's block is any time you should be writing, but aren't (i.e. you set aside the time, opened your Word Doc, sent out an #amwriting tweet... but zero words are coming out). Take, for example, my word count spreadsheet from a month ago:
It says I was "planning" chapter 7, but that was not my intention. Even when I do plan a chapter, it's rare I don't write anything. So what happened? In this case, I was trying to get from Plot Point A to Plot Point B, but every method I thought of was weak, lame, or contrived. I couldn't find anything worth writing.
If I may generalize millions of writers into tiny boxes, I think there are two kinds of writer's block. The first is where you don't know what to write. Common causes are plot holes, poor planning, weak character development, characters stuck in impossible situations, or just a plain lack of ideas.
Everyone's different, but the way I deal with this is to GET OUT. I might talk to someone about the story, but usually I just need to do something different. Something non-creative. Walking, swimming, cleaning, yard work...whatever works (of course my wife is wondering why she doesn't see me "getting over writer's block" more often, but we won't talk about that here).
It might help to even take some time off writing, but don't do it for more than a week or two. Maybe a month in extreme cases. If you need more than that, you might have a different problem. Or you might have the second kind of writer's block: you don't really want to write.
Maybe it's laziness, lack of self-discipline, poor time management... Don't feel bad. Every writer struggles with this stuff.** Writing is a lot like exercise--it's hard to do, but you feel great once it's done. The solution to this type of block is the opposite of the first: SIT DOWN AND WRITE. Even if it's full of plot holes, contrived situations, and weak characters, getting it written down is better than not.
What about you? Do you ever get blocked? How do you get over it?
** In the 3 weeks I had in the States--a lot of which came with free babysitting--I only squeezed out 8 hours of writing. Few of them productive.
* Who, I'm obligated to point out, is not Carrie Kei Heim Binas.
I hate it. But I think I know how to deal with it.
For the purposes of this post, writer's block is any time you should be writing, but aren't (i.e. you set aside the time, opened your Word Doc, sent out an #amwriting tweet... but zero words are coming out). Take, for example, my word count spreadsheet from a month ago:
It says I was "planning" chapter 7, but that was not my intention. Even when I do plan a chapter, it's rare I don't write anything. So what happened? In this case, I was trying to get from Plot Point A to Plot Point B, but every method I thought of was weak, lame, or contrived. I couldn't find anything worth writing.
If I may generalize millions of writers into tiny boxes, I think there are two kinds of writer's block. The first is where you don't know what to write. Common causes are plot holes, poor planning, weak character development, characters stuck in impossible situations, or just a plain lack of ideas.
Everyone's different, but the way I deal with this is to GET OUT. I might talk to someone about the story, but usually I just need to do something different. Something non-creative. Walking, swimming, cleaning, yard work...whatever works (of course my wife is wondering why she doesn't see me "getting over writer's block" more often, but we won't talk about that here).
It might help to even take some time off writing, but don't do it for more than a week or two. Maybe a month in extreme cases. If you need more than that, you might have a different problem. Or you might have the second kind of writer's block: you don't really want to write.
Maybe it's laziness, lack of self-discipline, poor time management... Don't feel bad. Every writer struggles with this stuff.** Writing is a lot like exercise--it's hard to do, but you feel great once it's done. The solution to this type of block is the opposite of the first: SIT DOWN AND WRITE. Even if it's full of plot holes, contrived situations, and weak characters, getting it written down is better than not.
What about you? Do you ever get blocked? How do you get over it?
** In the 3 weeks I had in the States--a lot of which came with free babysitting--I only squeezed out 8 hours of writing. Few of them productive.
Enjoyed this post? Stay caught up on future posts by subscribing here.
Filed under:
questions/answers,
writing process,
writing tips
Subscribe to:
Posts (Atom)