- The Annotation Project: The God of Small Things
- Storyteller’s Rulebook: Cut Most of Your Adjectives and Adverbs
- Straying from the Party Line: The Abundance of Adjectives and Adverbs in “The God of Small Things”
- Storyteller’s Rulebook: Help Us Get Our Feet on the Ground (Or Don’t, If That’s What You’d Prefer)
- Storyteller’s Rulebook: Capture the Logic of Childhood
- Rulebook Casefile: The Power and Peril of the “Put a Pin in It” Scene
Podcast
Sunday, November 25, 2018
The God of Small Things: The Archive
Okay, just got done with an epic Thanksgiving week and need some time to decompress. In the meantime, here’s an archive of our ninth book. We’re starting to have a meaningful data set!
Sunday, November 18, 2018
Podcast Episode 8: The Jedi in Decline
I told you we’d be back a lot quicker this time! Well, we spiked an earlier episode about The Last Jedi, but James hijacks this one and finally gets the discussion he wanted. We start out with my belief that most stories are based on problem solving, but then James brings up the hidden back half of the hero’s journey offered by Lord Raglan, and, of course, brings it all around to a certain recent movie.
And then he claims that you caused Trump by not liking Jar-Jar Binks. Depending on your political bent, you can feel happy or guilty about that!
And then he claims that you caused Trump by not liking Jar-Jar Binks. Depending on your political bent, you can feel happy or guilty about that!
Thursday, November 15, 2018
Rulebook Casefile: The Power and Peril of the “Put a Pin in It” Scene
As I said before, Arundhati Roy begins “The God of Small Things” by jumping all around, not landing at the book’s real 1969 timeline for 40 pages or so. As we jump around, the first scene with dialogue we get is Sophie’s funeral, which comes at the end of the 1969 timeline, not the beginning. After the funeral we see Ammu take her twins to the police station to half-heatedly try to save Velutha, but we have no idea what’s going on, and Roy doesn’t tell us (Partially because Rahel, our POV character, doesn’t understand, or wants to pretend that she doesn’t understand). The police send Ammu away, and she gets on a bus where she mysteriously says to her kids, “He’s dead, I’ve killed him.” Then we move forward again two weeks to when Estha is sent away, then we move ahead to adult-Rahel’s return, then back to Estha’s earlier adult life, etc.
The brief police station is a “put a pin in it” scene. “Remember this for later, reader, because it will finally make sense to you 300 pages from now.”
This scene could make us say “Ooh, what’s going on here with the police? Who did Ammu kill? I can’t wait to read the book and find out!” but it doesn’t really have that effect. If we had immediately jumped from Ammu saying “I’ve killed him” back to a week before, then we’d have the sense of “Good, now we’ll find out what she meant!”, but since we keep jumping forward, and then jumping around in the adult timeline for a while, we strain to keep our finger on that pin, occasionally asking ourselves, “Wait, what was going on at that police station? Will any of these events we’re seeing now make that clear?”
The trick with such scenes is to keep the reader from wondering, “Wait, was I supposed to understand that?” That’s always my problem with such scenes. Instead of thinking, “Ooh, I can’t wait to find out what was happening there!”, I always find myself thinking, “I’m so dumb for not understanding that scene. It should have been obvious to me how Ammu was killing a man in that last scene.”
How do you write such scenes so they’re clearly unclear? So that the reader will say, “Obviously I wasn’t supposed to understand that yet, and now I’m excited to later find out what was going on,” rather than “I think I was supposed to understand that, but I didn’t.” I would have appreciated a little more hand-holding. Roy could have said something like, “Rahel didn’t know what she meant, and it was only many years later she would put the events together and figure it out.” That would let us know that it wasn’t clear yet but it would be clear later.
Ultimately, Roy doesn’t seem particularly concerned with this question. This is literary fiction, and the reader is supposed to bring some hustle to the game. This is a wildly successful novel, by any measure, but nevertheless, if I’d been giving her notes, I would have begged for just a tiny bit more help, making it clear that it was unclear.
The brief police station is a “put a pin in it” scene. “Remember this for later, reader, because it will finally make sense to you 300 pages from now.”
This scene could make us say “Ooh, what’s going on here with the police? Who did Ammu kill? I can’t wait to read the book and find out!” but it doesn’t really have that effect. If we had immediately jumped from Ammu saying “I’ve killed him” back to a week before, then we’d have the sense of “Good, now we’ll find out what she meant!”, but since we keep jumping forward, and then jumping around in the adult timeline for a while, we strain to keep our finger on that pin, occasionally asking ourselves, “Wait, what was going on at that police station? Will any of these events we’re seeing now make that clear?”
The trick with such scenes is to keep the reader from wondering, “Wait, was I supposed to understand that?” That’s always my problem with such scenes. Instead of thinking, “Ooh, I can’t wait to find out what was happening there!”, I always find myself thinking, “I’m so dumb for not understanding that scene. It should have been obvious to me how Ammu was killing a man in that last scene.”
How do you write such scenes so they’re clearly unclear? So that the reader will say, “Obviously I wasn’t supposed to understand that yet, and now I’m excited to later find out what was going on,” rather than “I think I was supposed to understand that, but I didn’t.” I would have appreciated a little more hand-holding. Roy could have said something like, “Rahel didn’t know what she meant, and it was only many years later she would put the events together and figure it out.” That would let us know that it wasn’t clear yet but it would be clear later.
Ultimately, Roy doesn’t seem particularly concerned with this question. This is literary fiction, and the reader is supposed to bring some hustle to the game. This is a wildly successful novel, by any measure, but nevertheless, if I’d been giving her notes, I would have begged for just a tiny bit more help, making it clear that it was unclear.
Monday, November 12, 2018
Storyteller’s Rulebook: Capture the Logic of Childhood
The major question that hangs over “The God of Small Things”, the question that adult-Rahel seems to be trying to answer for herself, is why Sophie Mol and Velutha had to die, all those years earlier. One of the reasons is that seven year olds don’t make good decisions. The twins’ bad decisions contribute to Sophie’s accidental drowning, and then they are forced to accuse Velutha, who is beaten to death by the police. Now two people are dead, but the twins never really recover either, at least not by age 31.
In order to tell this story, Roy must intimately capture the faulty logic of seven year olds, and I can say, as the father of a seven year old daughter, and a former seven year old myself, that she does a great job.
We jump around a lot at first, but the first real scene we get is Sophie’s funeral (while Velutha is dying in police custody, but we don’t know that, and young Rahel only kind of knows it). Inside Rahel’s head, Roy captures her thoughts and musings:
Young Rahel imagines that someone like Velutha might have painting the ceiling, and then imagines him falling to his death, which shows her subconscious struggling with her vague realization of Velutha’s actual mortal peril. We see her convince herself that Sophie is killed by the funeral, not the drowning, which absolves Rahel of her guilt.
But here’s the great thing about this passage: It’s almost funny. The situation could not be more serious, but Roy’s voice (which is only slightly removed from Rahel’s voice, see below*) is so true-to-life that we can’t help but smile. Morbid seven year olds are amusing, in a Wednesday Addams sort of way.
We nervously laugh at this because it’s uncomfortably intimate. We remember what it was like to look at the world through young eyes, to let our imaginations run away with us, not in a “Reading Rainbow” sort of way, but in strange, dark ways. We never thought a book would remind us of those forgotten thoughts, retrace the path of that twisted logic. People cite this as their favorite book not because they love its dark subject matter, but because they feel Roy has been in their heads, and they find that strange intimacy intoxicating.
As with our last book, it’s great to give your hero unique eyes. They should look at the world and see things only they would see. From the first page, even as an adult, Rahel has oddly overimaginative eyes. She looks at nature and sees human emotions where none exist. Nature’s clashes become petulant human squabbles. We then go back to when she was a kid and she cannot look at a corpse without bringing it to life: Sophie’s still alive, so that means she’s looking up at the ceiling, I wonder what she sees… Oh, she sees the newly painted ceiling… I wonder who painted it? Probably someone like Velutha? What if he fell? She can’t deal with the body in the coffin, but she’s happy to create one on the ground. And of course, one corpse will lead to the other in real life, but neither she nor we understand that at this point. This book rewards rereading!
* As I say above, this is all a great example of subjective 3rd person narration, which is one of the hardest ways to write. In the above paragraphs, despite the 3rd-person pronouns, we’re obviously entirely inside Rahel’s head, seeing only what she’s seeing, thinking what she’s thinking, feeling what she’s feeling. Roy will later take advantage of being in 3rd to show us scenes that Rahel doesn’t see …but crucially, they’re all scenes (like Estha’s molestation) that Rahel hears about or intuits later. They still fit under the umbrella of things grown-up-Rahel might put together to try to make sense of in modern day.
In order to tell this story, Roy must intimately capture the faulty logic of seven year olds, and I can say, as the father of a seven year old daughter, and a former seven year old myself, that she does a great job.
We jump around a lot at first, but the first real scene we get is Sophie’s funeral (while Velutha is dying in police custody, but we don’t know that, and young Rahel only kind of knows it). Inside Rahel’s head, Roy captures her thoughts and musings:
- She noticed that Sophie Mol was awake for her funeral. She showed Rahel Two Things.
- Thing One was the newly painted high dome of the yellow church that Rahel hadn’t ever looked at from the inside. It was painted blue like the sky, with drifting clouds and tiny whizzing jet planes with white trails that crisscrossed in the clouds. It’s true (and must be said) that it would have been easier to notice these things lying in a coffin looking up than standing in the pews, hemmed in by sad hips and hymnbooks.
- Rahel thought of the someone who had taken the trouble to go up there with cans of paint, white for the clouds, blue for the sky, silver for the jets, and brushes, and thinner. She imagined him up there, someone like Velutha, barebodied and shining, sitting on a plank, swinging from the scaffolding in the high dome of the church, painting silver jets in a blue church sky.
- She thought of what would happen if the rope snapped. She imagined him dropping like a dark star out of the sky that he had made. Lying broken on the hot church floor, dark blood spilling from his skull like a secret
- [later:]
- When they lowered Sophie Mol’s coffin into the ground in the little cemetery behind the church, Rahel knew that she still wasn’t dead.
- [later:]
- Inside the earth Sophie Mol screamed, and shredded satin with her teeth. But you can’t hear screams through earth and stone.
- Sophie Mol died because she couldn’t breathe.
- Her funeral killed her.
Young Rahel imagines that someone like Velutha might have painting the ceiling, and then imagines him falling to his death, which shows her subconscious struggling with her vague realization of Velutha’s actual mortal peril. We see her convince herself that Sophie is killed by the funeral, not the drowning, which absolves Rahel of her guilt.
But here’s the great thing about this passage: It’s almost funny. The situation could not be more serious, but Roy’s voice (which is only slightly removed from Rahel’s voice, see below*) is so true-to-life that we can’t help but smile. Morbid seven year olds are amusing, in a Wednesday Addams sort of way.
We nervously laugh at this because it’s uncomfortably intimate. We remember what it was like to look at the world through young eyes, to let our imaginations run away with us, not in a “Reading Rainbow” sort of way, but in strange, dark ways. We never thought a book would remind us of those forgotten thoughts, retrace the path of that twisted logic. People cite this as their favorite book not because they love its dark subject matter, but because they feel Roy has been in their heads, and they find that strange intimacy intoxicating.
As with our last book, it’s great to give your hero unique eyes. They should look at the world and see things only they would see. From the first page, even as an adult, Rahel has oddly overimaginative eyes. She looks at nature and sees human emotions where none exist. Nature’s clashes become petulant human squabbles. We then go back to when she was a kid and she cannot look at a corpse without bringing it to life: Sophie’s still alive, so that means she’s looking up at the ceiling, I wonder what she sees… Oh, she sees the newly painted ceiling… I wonder who painted it? Probably someone like Velutha? What if he fell? She can’t deal with the body in the coffin, but she’s happy to create one on the ground. And of course, one corpse will lead to the other in real life, but neither she nor we understand that at this point. This book rewards rereading!
* As I say above, this is all a great example of subjective 3rd person narration, which is one of the hardest ways to write. In the above paragraphs, despite the 3rd-person pronouns, we’re obviously entirely inside Rahel’s head, seeing only what she’s seeing, thinking what she’s thinking, feeling what she’s feeling. Roy will later take advantage of being in 3rd to show us scenes that Rahel doesn’t see …but crucially, they’re all scenes (like Estha’s molestation) that Rahel hears about or intuits later. They still fit under the umbrella of things grown-up-Rahel might put together to try to make sense of in modern day.
Sunday, November 11, 2018
Storyteller’s Rulebook: Help Us Get Our Feet on the Ground (Or Don’t, If That’s What You’d Prefer)
Last time we looked at the way Arundhati Roy accumulates reality from small, odd, vivid details, but once we piece it together “The God of Small Things” is actually a fairly plot-packed story: We get a riot, a molestation, an accidental drowning, and a police murder all happening in a weeklong-period.
So let’s talk about how authors get us to commit to a book in the first chapter, especially one where the narrator (1st or 3rd person) has some perspective on events. The traditional way to is to promise that a lot of juicy stuff is going to happen later on if you keep reading. And indeed, this book is well set-up to do that. We begin with an adult Rahel coming back to town in modern-day to reunite with her long-lost brother and deal with how the event that separated them and traumatized their lives. We will then spend most of the book reliving that eventful week.
I know how I would have written that first chapter: We meet our mysterious heroine as she gets off the train, we find out just a little bit about her, we see that she’s on a mission. She meets with someone from her past while looking for her silent brother, and obliquely references the riot, the molestation, the drowning, and the murder (Now our appetite is whetted for the shocking events to come). Then she finds her brother and tries to speak but the memories flood over her. Then we cut back to the day of the riot and we quickly get dialogue of 7-year-old Rahel in that time period. Now our two heroines (adult Rahel in 1993 and young Rahel in 1969) are established. From that point, Roy would be free to jump around to other points in time, such as the birth of the twins, the mother’s later death, Rahel’s own failed marriage, etc.
But Roy doesn’t do that. She’s all over the place and it’s hard to put your feet down anywhere for the first thirty pages or so. When I read the book, I read those thirty pages, realized I was totally lost, and decided I’d better go back and read them over again if I was going to continue. I did so, was glad I did, and then kept going until I was able to put my feet down around page 40 or so. While this whole process was going on, I was loving the book, because of the sentences, but I was struggling with committing to the plot.
Roy does foreshadow the book’s momentous events in these opening chapters, but because I didn’t have a sense of whether they were going to happen in a timeline I was going to stick to, they didn’t whet my appetite very much. What I really wanted was dialogue. Dialogue tells me to put my feet down, but the first dialogue we get is at Sophie’s funeral, which actually comes at the end of the 1969 timeline, not the beginning, so that just discombobulated me further.
Here are four consecutive paragraphs that show how Roy is jumping around
Now, obviously, this book was a huge award-winner and best seller, and Roy knows exactly what she’s doing. She isn’t trying to do what I want her to do and failing, she’s doing what she intends to do and succeeding. To a certain degree, her style is emblematic of what is referred to (somewhat problematically) as post-colonial literature (Roy would probably dispute the “post” part). One of the most famous first sentences in literature is from what is perhaps the ultimate post-colonial book, Gabriel Garcia-Marquez’s “One Hundred Years of Solitude”:
Right there in the opening sentence, we have three time periods mixed up, and the reader will have a hard time getting his or her feet on the ground after that …and yet it’s very easy to fall in love with the book.
Such writing has its pleasures. Readers do enjoy being challenged. We can admire how such writing captures the feeling of being lost and overwhelmed by the modern world, and, as we make sense of it, we can gain tools to sift through and make sense of our own jumbled lives.
Post-colonial writers have literally had the ground yanked out from underneath their feet by invaders, and now that they have reclaimed their countries, they’re trying to find their footing again. But the ground isn’t letting them. It keeps shifting. When they describe their work in interviews, many of them say that their sense of identity, both personal and national, remains fractured. The style of post-colonial literature captures and grapples with that problem.
So the question is, should non-post-colonial writers emulate this style? These are, after all, best-selling and beloved books. But it’s a lot to ask of your reader, especially if it’s not a style that you are personally deeply committed to. Unless you feel that such a style is an essential expression of your theme, you might want to put the reader’s feet on the ground a little more firmly than Roy does, just with a few uses of grounding dialogue.
So let’s talk about how authors get us to commit to a book in the first chapter, especially one where the narrator (1st or 3rd person) has some perspective on events. The traditional way to is to promise that a lot of juicy stuff is going to happen later on if you keep reading. And indeed, this book is well set-up to do that. We begin with an adult Rahel coming back to town in modern-day to reunite with her long-lost brother and deal with how the event that separated them and traumatized their lives. We will then spend most of the book reliving that eventful week.
I know how I would have written that first chapter: We meet our mysterious heroine as she gets off the train, we find out just a little bit about her, we see that she’s on a mission. She meets with someone from her past while looking for her silent brother, and obliquely references the riot, the molestation, the drowning, and the murder (Now our appetite is whetted for the shocking events to come). Then she finds her brother and tries to speak but the memories flood over her. Then we cut back to the day of the riot and we quickly get dialogue of 7-year-old Rahel in that time period. Now our two heroines (adult Rahel in 1993 and young Rahel in 1969) are established. From that point, Roy would be free to jump around to other points in time, such as the birth of the twins, the mother’s later death, Rahel’s own failed marriage, etc.
But Roy doesn’t do that. She’s all over the place and it’s hard to put your feet down anywhere for the first thirty pages or so. When I read the book, I read those thirty pages, realized I was totally lost, and decided I’d better go back and read them over again if I was going to continue. I did so, was glad I did, and then kept going until I was able to put my feet down around page 40 or so. While this whole process was going on, I was loving the book, because of the sentences, but I was struggling with committing to the plot.
Roy does foreshadow the book’s momentous events in these opening chapters, but because I didn’t have a sense of whether they were going to happen in a timeline I was going to stick to, they didn’t whet my appetite very much. What I really wanted was dialogue. Dialogue tells me to put my feet down, but the first dialogue we get is at Sophie’s funeral, which actually comes at the end of the 1969 timeline, not the beginning, so that just discombobulated me further.
Here are four consecutive paragraphs that show how Roy is jumping around
- In those early amorphous years when memory had only just begun, when life was full of Beginnings and no Ends, and Everything was Forever, Esthappen and Rahel thought of themselves together as Me, and separately, individually, as We or Us. As though they were a rare breed of Siamese twins, physically separate, but with joint identities.
- Now, these years later, Rahel has a memory of waking up one night giggling at Estha’s funny dream.
- She has other memories too that she has no right to have.
- She remembers, for instance (though she hadn’t been there), what the Orangedrink Lemondrink Man did to Estha in Abhilash Talkies. She remembers the taste of the tomato sandwiches—Estha’s sandwiches, that Estha ate—on the Madras Mail to Madras.
Now, obviously, this book was a huge award-winner and best seller, and Roy knows exactly what she’s doing. She isn’t trying to do what I want her to do and failing, she’s doing what she intends to do and succeeding. To a certain degree, her style is emblematic of what is referred to (somewhat problematically) as post-colonial literature (Roy would probably dispute the “post” part). One of the most famous first sentences in literature is from what is perhaps the ultimate post-colonial book, Gabriel Garcia-Marquez’s “One Hundred Years of Solitude”:
- Many years later, as he faced the firing squad, Colonel Aureliano Buendia was to remember that distant afternoon when his father took him to discover ice.
Right there in the opening sentence, we have three time periods mixed up, and the reader will have a hard time getting his or her feet on the ground after that …and yet it’s very easy to fall in love with the book.
Such writing has its pleasures. Readers do enjoy being challenged. We can admire how such writing captures the feeling of being lost and overwhelmed by the modern world, and, as we make sense of it, we can gain tools to sift through and make sense of our own jumbled lives.
Post-colonial writers have literally had the ground yanked out from underneath their feet by invaders, and now that they have reclaimed their countries, they’re trying to find their footing again. But the ground isn’t letting them. It keeps shifting. When they describe their work in interviews, many of them say that their sense of identity, both personal and national, remains fractured. The style of post-colonial literature captures and grapples with that problem.
So the question is, should non-post-colonial writers emulate this style? These are, after all, best-selling and beloved books. But it’s a lot to ask of your reader, especially if it’s not a style that you are personally deeply committed to. Unless you feel that such a style is an essential expression of your theme, you might want to put the reader’s feet on the ground a little more firmly than Roy does, just with a few uses of grounding dialogue.
Thursday, November 08, 2018
Straying from the Party Line: The Abundance of Adjectives and Adverbs in “The God of Small Things”
You may have noticed that in each of my annotations I’ve praised opening sentences for having no adjectives or adverbs, and in our last post I was especially critical of two adjectives together that require a comma. Well let’s look at the opening sentence of Arundhati Roy’s “The God of Small Things”:
The dreaded stumbling-block comma! Indeed this first chapter is an avalanche of adjectives, with sentences like this one to be found later:
Five adjectives in one sentence! But let’s go back and look at the rest of that opening paragraphs to figure out how Roy gets away with using so many adjectives without trying the reader’s patience:
Ten more adjectives and, what’s worse, two adverbs! Yet it’s a glorious opening paragraph, is it not? So what is she doing?
Ultimately, she will justify her non-leanness, her abundance of detail, with the book’s title. Who is the God of Small Things? It’s Roy herself. The whole idea is that tragedies can only be remembered as, and are perhaps best understood as, an accumulation of small things. Why does Sophie (and the book’s actual victim of injustice, Velutha) die? What is the one cause? There isn’t one, because there are hundreds of small things that added up to it.
This is a memory book (though the book is third-person and not entirely limited to Rahel’s firsthand memories). Rahel is trying to piece it all back together and sifting through portentous images and impressions that she accumulated that week, which she and Roy are now re-examining in great detail. Fine-grained descriptions are the whole point. Somewhere in these small things, there is a god who will tell us why these people had to die.
- May in Ayemenem is a hot, brooding month
The dreaded stumbling-block comma! Indeed this first chapter is an avalanche of adjectives, with sentences like this one to be found later:
- She heard (on Sophie Mol’s behalf) the soft sounds of the red mud and the hard sounds of the orange laterite that spoiled the shining coffin polish.
Five adjectives in one sentence! But let’s go back and look at the rest of that opening paragraphs to figure out how Roy gets away with using so many adjectives without trying the reader’s patience:
- The days are long and humid. The river shrinks and black crows gorge on bright mangoes in still, dustgreen trees. Red bananas ripen. Jackfruits burst. Dissolute bluebottles hum vacuously in the fruity air. Then they stun themselves against clear windowpanes and die, fatly baffled in the sun.
Ten more adjectives and, what’s worse, two adverbs! Yet it’s a glorious opening paragraph, is it not? So what is she doing?
- First of all, it’s intriguingly odd how she imputes human emotions to nature: “Dissolute bluebottles hum vacuously.” She’s not really describing what we would see, she’s generating a strange world we would never see if we didn’t see it through her eyes. Simply saying “bluebottles hum” wouldn’t do that job.
- She’s using fresh adjectives of her own invention: We get the first of many portmanteaus with “dustgreen”. Later we’ll get “wetgreen” and “thunderdarkness”. When the mom passes away, Roy will point out that 31 is “a viable die-able age” (Roy knows she’s got a great, pithy phrase there, and so she reuses it four times in the book!)
- Her adjectives create conflict: Black crows (death) gorge (a violent verb) on bright mangos (life). “Dustgreen” is death and life in one word. She’s not just painting a pretty tableau, she’s imbuing nature with life so that it can fight itself. Her adjectives clash.
Ultimately, she will justify her non-leanness, her abundance of detail, with the book’s title. Who is the God of Small Things? It’s Roy herself. The whole idea is that tragedies can only be remembered as, and are perhaps best understood as, an accumulation of small things. Why does Sophie (and the book’s actual victim of injustice, Velutha) die? What is the one cause? There isn’t one, because there are hundreds of small things that added up to it.
This is a memory book (though the book is third-person and not entirely limited to Rahel’s firsthand memories). Rahel is trying to piece it all back together and sifting through portentous images and impressions that she accumulated that week, which she and Roy are now re-examining in great detail. Fine-grained descriptions are the whole point. Somewhere in these small things, there is a god who will tell us why these people had to die.
Tuesday, November 06, 2018
Storyteller’s Rulebook: Cut Most of Your Adjectives and Adverbs
So I’ve got a problem: I was going to talk about how Arundhati Roy uses a lot of adjectives and adverbs, which goes against my advice, but then I realized I never actually gave that advice, because I couldn’t post the piece I wrote.
Last year, I was doing a lot of Storyteller’s Rulebook pieces based on examples from notes I’d given, but that was annoying, because I had to run them by the person I gave the notes to, to see if I could share their sentences. Well the author of these sentences asked me to hold off until the story was published. But now the story has been published (though the author has still asked not to be identified) so I’m free to post it, before I offer Roy as a counterpoint next time:
The original piece:
One of the biggest problems I see is the use of too many adjectives and adverbs. I’m certainly not the first editor to carp about this, but I’ll add my voice to the multitudes
Let’s look at a sentence from one of the authors I read: “The sky was a gray iron wall locked down thick and tight, the snow was swarming and swimming crazily around like it wanted in.” Now let’s cut “gray”, “thick and”, and “crazily.” “The sky was an iron wall locked down tight, the snow was swarming and swimming around like it wanted in.”
Never use two adjectives when one will do, and one will almost always do. One adjective usually implies the other, so the other is not needed. Iron implies gray, so you don’t need gray. Iron and tight, working together, imply thick, so cut thick. As for the adverb, “swarming and swimming” implies crazily, so cut crazily. Don’t bore us within a sentence by giving us the same information twice, first in verb form and then in adverb form.
Readers don’t want to luxuriate in your mellifluous sentences. They want to know what’s going on. They want to see it and feel it, then they want to move on to the next image as soon as possible. This is a good sentence, once the fat is trimmed out.
It doesn’t apply to this sentence, but one rule is that you should never use two adjectives that need a comma between them: Big blue ball doesn’t feel like it needs a comma between big and blue, so it’s fine. Cold, breezy day needs a comma, so you should probably cut one of the adjectives. Commas are speed-bumps, causing the reader to stumble and slowing down the reading process.
Here’s another sentence from that manuscript: “I stared at the blocks stupidly.” Adverbs almost always feel like apologies for failing to find an interesting verb, as if you’re saying, “I was staring, and I know that’s not very interesting, but what if I told you it was doing so stupidly?” Don’t apologize. Trust your verbs. Force us to be content with staring. It’s not possible to stare at blocks intelligently (unless the next line is, “and I spotted an important clue!”) Just cut the adverb, 90% of the time.
Last year, I was doing a lot of Storyteller’s Rulebook pieces based on examples from notes I’d given, but that was annoying, because I had to run them by the person I gave the notes to, to see if I could share their sentences. Well the author of these sentences asked me to hold off until the story was published. But now the story has been published (though the author has still asked not to be identified) so I’m free to post it, before I offer Roy as a counterpoint next time:
The original piece:
One of the biggest problems I see is the use of too many adjectives and adverbs. I’m certainly not the first editor to carp about this, but I’ll add my voice to the multitudes
Let’s look at a sentence from one of the authors I read: “The sky was a gray iron wall locked down thick and tight, the snow was swarming and swimming crazily around like it wanted in.” Now let’s cut “gray”, “thick and”, and “crazily.” “The sky was an iron wall locked down tight, the snow was swarming and swimming around like it wanted in.”
Never use two adjectives when one will do, and one will almost always do. One adjective usually implies the other, so the other is not needed. Iron implies gray, so you don’t need gray. Iron and tight, working together, imply thick, so cut thick. As for the adverb, “swarming and swimming” implies crazily, so cut crazily. Don’t bore us within a sentence by giving us the same information twice, first in verb form and then in adverb form.
Readers don’t want to luxuriate in your mellifluous sentences. They want to know what’s going on. They want to see it and feel it, then they want to move on to the next image as soon as possible. This is a good sentence, once the fat is trimmed out.
It doesn’t apply to this sentence, but one rule is that you should never use two adjectives that need a comma between them: Big blue ball doesn’t feel like it needs a comma between big and blue, so it’s fine. Cold, breezy day needs a comma, so you should probably cut one of the adjectives. Commas are speed-bumps, causing the reader to stumble and slowing down the reading process.
Here’s another sentence from that manuscript: “I stared at the blocks stupidly.” Adverbs almost always feel like apologies for failing to find an interesting verb, as if you’re saying, “I was staring, and I know that’s not very interesting, but what if I told you it was doing so stupidly?” Don’t apologize. Trust your verbs. Force us to be content with staring. It’s not possible to stare at blocks intelligently (unless the next line is, “and I spotted an important clue!”) Just cut the adverb, 90% of the time.
Sunday, November 04, 2018
The Annotation Project: The God of Small Things
Another bestselling novel from 1997! I know what you’re thinking: “Um, isn’t this a big jump from Lee Child?” But is it? Both Jack Reacher and Rahel Ipa have amazing eyes that note many small things that others miss, which we’ll discuss more soon... (Here’s the doc.)
Thursday, November 01, 2018
Killing Floor: The Archive
On Sunday, we’ll do a radically different novel, but first let’s wrap up Reacher:
- The Annotation Project: Killing Floor
- Why Do They Only Want Fifteen Pages?
- Straying from the Party Line: The Big Motivation Hole (And Big Coincidence) in “Killing Floor”
- Rulebook Casefile: News You Can Use in "Killing Floor"
- How To Plot a Mystery: How to Get Your Hero Into and Out of Trouble
- So Why Do David Remnick and Malcolm Gladwell Like Jack Reacher So Much?
Subscribe to:
Posts (Atom)