Most advice I’ve read about using feedback as a guide for revision assumes that every writer feels compelled to immediately change their story to comply with every suggestion, and that most of us need pep talks to remember the story is ours. There’s nothing wrong with such pep talks, but my experience has been that many writers (myself included) are more inclined to dismiss most advice, critique, and suggestions unless such feedback comes from someone we know and trust.
Be open. Don’t dismiss feedback out of hand, and resist the urge to argue or explain.
Yes, if you are attending a writing workshop taught by an author you have long admired, and bonding with your fellow students, you’re likely to take every single piece of advice to heart, even the contradictory ones, and tie yourself in knots trying to rewrite your story to address every issue. Similarly, if you have a critique group you trust, you may find yourself in a similar situation after they go over a story. In that circumstance it is important to remember the Neil Gaiman quote: “Remember: when people tell you something’s wrong or doesn’t work for them, they are almost always right. When they tell you exactly what they think is wrong and how to fix it, they are almost always wrong.”
People are making suggestions because the story isn’t working for them. Some of the suggestions are contradictory because the people offering them are misidentifying the root cause. Before discarding contradictory advice, see if you can find an intersection. For instance, one time I received feedback on a draft novel from three people whose opinion I trust. One was quite insistent that I needed to add some dream sequences or some other sort of mystical experience to more explicitly explain why the reclusive shrine-guardian was compelled to undertake a quest to save the world. Another thought I should remove several characters (including the shrine guardian) that (in their opinion) weren’t contributing to the main plot, because there were just too many things going on, and clearly the center of the action was the cursed thief. The third person wanted me to split off the shape-shifting fortuneteller (and a few other characters) into their own book.
The intersection of those comments was a fundamental issue all three readers were missing: the novel doesn’t have one protagonist, it has three protagonists whose fates are intertwined and that all come together in the end. Now the reason these readers were missing that detail was not because they were dense or didn’t appreciate the story; they were missing it because I as the author hadn’t made it clear. It was not working in the story. I needed to fix it, but the fix did not involve removing characters, or adding dream sequences, or splitting the book in two. The fix also didn’t require massive rewrites. The fix required dropping a few scenes that weren’t carrying their weight, replacing them with some that did more, and making tweaks to several others.
Look for the unobvious connection. Just because advice seems contradictory doesn’t mean it is wrong.
Sometimes the feedback you get appears to come from a different planet. I’ve mentioned before the reader who complained about my happy endings. The story that was the straw that broke the camel’s back for that reader was a tale which ends with two of the main characters saying good-bye as one is going to escort the corpses of several murder victims on their journey to their families. The story had featured some graphic violence long before getting to that scene. While the killer had been caught and was going to be facing justice, and some of the characters had survived, given how many didn’t and where I set the final scene (literally next to some coffins) I had trouble thinking of it as a happy ending.
I’m a person who fundamentally believes in hope. I’m never going to write stories that will appeal to the sort of reader who insists that happy endings never happen for anyone. That particular story had already been published, so it was a bit late to revise it. But I still found the feedback worthwhile. It was worth asking myself if I had written something earlier in the story that had led this reader—who was really looking to read something grim and dark—to think that that’s what this one was going to be. Did I raise an expectation that I failed to deliver?
Maybe I did. A lesson I took away from that was to remember to look for those unintended expectations. Everyone has heard the famous advice about the gun on the mantlepiece: if you show the reader a gun on the scene, the gun needs to figure in the plot before the story is over. The advice doesn’t just refer to guns, it means that when you draw the reader’s attention to things, people, or events that seem to signify certain dramatic possibilities, that something needs to come of it. That isn’t to say that I must write stories that meet the reader’s expectations, just to make certain that I don’t mislead the reader midway through the story. Yeah, misdirection is okay as long as you play fair (that’s a topic for an entire blog post on its own), and you don’t want to telegraph the ending to the reader, but don’t play bait-and-switch.
Don’t blame the messenger. Maybe the person giving you the weird sounding feedback is absolutely the only being in the universe who will misread your story this way, but don’t forget that where there’s smoke, there’s usually fire.
I’ve gotten feedback that left me feeling confused and conflicted about whether my story is worth telling. That might be a good time to follow the advice I read in a magazine article decades ago (and have long forgotten who wrote): sit down and write out an explanation of what is wrong with each part of the critique to don’t like. Do not ever send this to the person, repeat any of it to the person, or post it. Instead, set your reply and this story aside and go work on something else. Later, when you can look at this story objectively, pull out your explanation and go through your story. Is everything you say in the explanation in the story? Is it clear in the story? Chances are that some things you have assumed the reader will infer aren’t as obvious as you though. Sometimes you’ll discover that you never actually mentioned one very important fact for your plot. You thought you did, but it isn’t actually there. Now destroy that explanation/argument you wrote, and rewrite your story.
Argue with yourself, not the reader. Figure out what is missing, and add it in.
Many times I’ve written scenes that never wind up in the story. Sometimes I write them because I’m not certain what to do next, then later I realize that scene isn’t necessary. Sometimes I write them because I’m trying to figure out something that I plan to have happened in the past or off screen, but I need to be able to have characters who lived through the events react accordingly later. And sometimes I write a scene because I received suggestions or critiques that I either wasn’t certain I agreed with, or was quite certain I disagreed with but it kept coming up from multiple people. So I tried writing the scene that followed the suggestion. Usually what happened is not that the new scene went into my story and replaced a bunch of other stuff, but rather, in the course of writing the scene, I figured out something else about the story. Just trying to write it the way other people wanted it to go clarified where the story actually needed to go.
Give it a try. Every writer writes stuff that eventually we decide not to use or to change significantly. Don’t be afraid to spend some time giving alternatives a go.
Trust the story. Recognize that you will stumble and sometimes fall. It doesn’t matter how many times you do that, if you keep getting back up and get moving. So stop thinking about the story, and go write it!
It’s the most natural thing to do, because you know you don’t have a bigoted bone in your body, so of course you aren’t racist/sexist/homophobic/anti-semetic or whatever the person has just said. So of course you feel the need to defend yourself. But you’re wrong. That’s because what you think they mean is that you are a horrible bigot, but that isn’t what’s going on here. What the person is actually trying to communicate is this: “I felt devalued or erased by some of the content of your story.” Nothing you say can change the feelings they had when they read your book. So the first sense in which it is wrong to argue is that you see this as an attack on you, whereas they are explaining how attacks on them that society has been subjecting them to their entire lives are being unintentionally aided and abetted by your story.
The other sense in which you are wrong is the belief that you don’t have any bigotry at all. Because all of us do. It is impossible to grow up in human society without absorbing a lot of prejudice. Including prejudice aimed at ourselves. Queer people have to overcome a lot of internalized homophobia just to come out of the closet. Women learn and internalize misogyny and sexism. Ethnic minorities learn and internal racial prejudice, and so forth. So it doesn’t matter how much you feel you aren’t bigoted, there is going to be some unconscious prejudices boiling around inside. And problematic content isn’t usually about overt bigotry, but is often more subtle.
So, when someone confronts you about any unintentional bigotry in your work, you need to do three things:
It is tempting, even if you stop yourself from getting defensive, to respond to this sort of criticism as just another kind of negative review and say, “I’m sorry you didn’t enjoy it” then try to change the subject. But this is a different category of discourse entirely. And quite often the people who bring this criticism to you did enjoy most of your story. That’s why they’re taking the time to tell you about this problem. So a better response would be, “I’m sorry the book disappointed you in this way.” If you can say that sincerely, you might also say that you didn’t intend to do that, but don’t let it become an attempt to prove they’re wrong. Better to say, “I’ll try to do better.”
If the person wants to explain to you what it was in your work that made them feel this way, listen. Don’t argue, listen. If the person doesn’t want to talk in more detail about it, that’s all right. It doesn’t mean that they’re wrong or that you’ve someone won the argument. As uncomfortable as it is for you to hear that something you wrote made someone feel de-valued, it is just as uncomfortable (and riskier) for them to bring it up. Dealing with every day discrimination and microagressions means that members of marginalized communities have already had to defend themselves and explain how they are hurt by discrimination thousands of times. And they don’t have the energy to try to educate you in depth on the issue.
Which is where we get to the learning. Once it has been brought to your attention that some readers feel this way (which you never intended) while reading your work, it’s your job to decide how to do better. I love quoting the advice “Remember: when people tell you something’s wrong or doesn’t work for them, they are almost always right.” That’s part of a Neil Gaiman quote. One of the truths Gaiman is getting at is that if one reader feels a particular way about your work, many other readers will, too. The rest of Neil’s quote talks about fixing problems, and fixing it is the writer’s responsibility, not the reader’s. They’ve told you how it made them feel. If you don’t want some of your audience feeling that way, you have to decide how you’re going to fix that going forward.
I want to emphasize that I know this process isn’t easy. The first time someone told me a story I wrote had sexist bits in it I became extremely defensive and reacted like a complete jerk. I was wrong to do that. Fortunately, I also spent some time, after I acted like a jerk, re-reading the story and trying to see it from the reader’s point of view.
And she was right. There were several little things I had done just because that’s what women characters do in that situation in millions of books and television episodes and movies that we’ve all watched. And it was a simple matter to make some very minor changes to get rid of them. I didn’t become suddenly a sexism-free writer after that. I found myself a couple years later being asked by someone why after six chapters into a book I was writing, not one single female character had appeared or had a line of dialog—in a story that was set in a ordinary public school in a small modern American city. There were a number of women and girls in my imaginary world, some of whom were going to figure in the plot later, but for whatever reason, I had omitted them in the opening chapters. This, by the way, was the incident I’ve mentioned before that prompted me to re-read a whole bunch of my work applying the Bechdel–Wallace test1, and finding myself very embarrassed at how many of my stories failed it.
And even though since then, I have tried to educate myself on it, and made several changes to the way I tell some stories, I still find problems. I was editing a scene in one of my currently still-in-progress novels not that long ago when I happened upon a line of dialog that I barely remembered writing, and it was a very clichéd and sexist line. I changed it. Now not only is it not sexist, I think it’s funnier.
Again, not every such criticism is going to be spot-on. A few years ago I got a long angry letter about how a story I wrote perpetrated hate against religious people. The rant included accusations that I had been “brainwashed by the femi-nazis” so I wasn’t inclined to take it completely to heart. I asked some religious acquaintances to read the story (without mentioning the negative review) to give me feedback on the portrayal of religion and the various religious people in the story. Not that if they disagreed that proved the reviewer wrong, it was just two more perspectives from people who I trusted.
I ultimately had to make the decision about whether the story perpetuated anti-religious bigotry.
That’s all we can do: try to learn, try to see things from other perspectives, and find people we trust to check our conclusions from time to time. Members of particular marginalized groups can disagree. A few years back I and another gay male sci fi fan and writer got into a really long discussion about whether something I had written perpetuated negative stereotypes about gay men3. We never came to a complete meeting of minds on the topic.
There’s an excellent post over at Patheo by Libby Anne which makes really good reading on this topic: What to Do If Someone Calls You Sexist: A Short Primer. And it doesn’t just apply to sexism.
1. Based on a 1985 comic strip from the series Dykes to Watch For by Allison Bechdel, in which one woman asks another if she wants to go to the movie, and the second woman explains that she has a rule, she will only go to a movie if “…one, it has at least two women in it who, two, talk to each other about something other than a man.” Then she confesses that the last movie she’d been able to go to was Alien, because there is one scene where the two women on the spaceship crew talk about the monster. But only the one. Bechdel herself expressed some discomfort with people naming the test after her, since she said she got the idea for the rule from a friend, Liz Wallace, and to the writings of Virginia Woolf.2
2. If a movie or book passes the test, that doesn’t prove that said work isn’t sexist. All the Bechdel-Wallace test is assess whether women appear in the work to specific degree. That fact that so many works fail to achieve even this level of inclusion is just sad.
3. Remember, it is not a valid defense against an observation of bigotry to be a member of the marginalized group in question, any more than claiming to have a friend in the group absolves you of all culpability. Internalized homophobia can manifest in even the most woke queer person.
Everything I need to know about responding to reviews of my books I learned from my choral directors
There have been a few really notorious cases of this type. There’s the author who seemed to become obsessed by one person who had given lots of negative reviews online to a lot of books. The author tracked down the reader in real life, going to rather absurd lengths to document all the things the reader had said in her various personal profiles on different social which appeared to be false or exaggerations. It culminated in the author going to the reader’s home and confronting her. That’s not only not cool, it’s stalking under the legal definition in most states in the U.S., and could be prosecutable.
Another author tried to sue Amazon and a reviewer for libel.
Then there’s the various Anne Rice incidents: posting a link to a bad review on a book blog on her Facebook page and encouraging 740,000 plus fans to harass the reviewer in 2013; writing a scathing 1100 reply to a reader review on Amazon in 2004; issuing a petition to try to force Amazon to reveal the real names (and contact information) of customer reviewers; trying to get bad reviews reclassifyed as cyberbulling in 2015; et cetera.
I’ve seen some really good articles and at least one of those humorous flow charts about how to respond to negative reviews. And those are great. But negative reviews are only a subset of the problem. And I realized that when I shared and commented on one of the recent posts about this, that I was repeating advice that I’d received from some of my music directors back in the day. I was in orchestra, band, choir, and a small men’s ensemble in school, and then choir and small ensemble in college, and later sang in a gay & lesbian community chorus. I’ve had a lot of music directors, but it was always the choral directors who gave advice about responding to negative comments and other sorts of reviews one might receive to a concert. And what they said can apply to any creative work, so here we go:
When someone tells you they disliked your performance/your story/et cetera: Your response should always be limited to a simple and sincere, “I’m sorry you didn’t enjoy it.” As one choral director said, “Don’t give in to the temptation to try to convince the person that the concert was great. Don’t try to educate them about the significance of the piece, the history of the composer, and especially about how much hard work you put in. Just say, ‘I’m sorry you didn’t enjoy it’ and move on.” Doing anything else just makes people feel angry and defensive.
Personally, I think this response is best deployed with someone contacts you directly or tells you in person that they didn’t like your story/book/painting/what-have-you. In the case of published reviews or reviews posted online, the best response to negative reviews is to pretend you didn’t see them. Maybe talk to a close friend about any particularly badly phrased review, if you need to vent a bit, but don’t respond online or publicly in any way. Don’t send the reviewer private messages. Don’t post links to the negative review.
Arguing with someone is not going to change how they feel about it. And it may well convert them from someone who merely didn’t like this story, to someone who has a grudge and goes out of their way to bad mouth all of your other work.
Negative reviews aren’t the only kind that can be problematic:
When someone tells you they really liked it: Say, “Thank you. I’m so happy you enjoyed it.” This may really seem like a no-brainer, but I can’t count the number of times that a musician, artist, or writer I’ve known has responded to positive comments by saying something like, “But we did it wrong!” or “I hated it! Look at all of these mistakes I made!”
One choral director put it really well: “What you just said to that person is, ‘You have really bad taste in music or are really clueless because you didn’t notice the mistake.’ It’s an insult. Even if you are convinced that they are merely being polite, just say ‘Thank you. I’m glad you liked it.’”
It’s really easy when I look a something I wrote to see all the flaws. Particularly if it is something I wrote a while ago. Even if the story has prompted more than one reader to contact me to tell me they were so enthralled by my tale that they missed their train stop or their cue or stayed up way too late reading it. When I look at the story, I just think how the characterization of one of the supporting characters was inconsistent, or that I could have done a more subtle job revealing that clue, or why did I include the lyrics of the song one of my suspects was performing in that pivotal scene?
But those readers enjoyed it. They didn’t have to send me a comment. I might have never known they had even seen that story if they hadn’t gone out of their way to do so. They liked it. And that’s why I wrote it! I wanted someone to read it and like it! I shouldn’t try to talk a fan of my work into hating.
We’re socialized to be self-effacing. We’re taught that being overly proud of our work means we’re an arrogant jerk. Some of us have self-esteem issues and sincerely have trouble believing that people actually like our work. Don’t give in to either of those tendencies. Just say, ‘Thank you.’ Bank the compliment, and remember it the next time you read a negative review.
When someone asks questions about it: This one is tricky. We’re all socialized to answer questions when asked. Some of us are a bit too happy to expound at length if someone shows the slightest interest it our work.
It’s okay to answer questions. As one director put it, “It’s understandable that someone might ask why we performed a classical piece in German for an English-speaking audience, for instance. It’s perfectly reasonable to answer the question. Just make sure you simply answer it, and don’t try to pick a fight. Don’t assume that they are trying to start an argument. Tell them that the piece was originally written in German, and that you think music is beautiful in any language.” Questions about minor things in the plot of your book or character motivations which seem to be genuine confusion on the part of the reader can be answered in person or direct conversations as long as you don’t get defensive. Similarly to factual question about the publishing process—but keep it as simple as possible.
When it comes to published/online reviews as opposed to someone contacting you directly, don’t get drawn into an argument. Straightforward questions with a simple, factual answer are fine. For instance, I once saw in a review of a story that was part of a continuing series but had been picked up for reprint in another publication the comment: “I liked the story well enough, but wish I knew more about these characters.” It was simple to post a comment: “For more stories set in this universe using these characters, check out [Link to a place to buy them].” I said absolutely nothing else. Just an answer to the one question that had a simple answer.
Sometimes a person asking a question is looking to start an argument. And sometimes it’s quite obvious that they’re doing it. I once got a question about one story along the lines of, “Why did you have to give us a happy ending, again? Your stories really draw me in and get me interested in all the characters, but then you have yet another unrealistic ending. In real life things never work out like that!” If someone is doing this sort of back-handed compliment disguised as a question, you need to treat it as a negative review. “I told the story as I saw it. I’m sorry you didn’t enjoy it.”
Other questions may be less obviously a back-handed compliment, but still not have a simple factual answer, such as, “I don’t understand why the author made such an unlikeable character the hero of this story” or “Why are there so many sub-plots in this book? Why can’t we just stick to one character?” or “Why did the main character spend all that time moping and talking? He should have kicked some butt and showed them who’s boss!” There is no answer you can give to this person that will make them happy. You had your reasons for writing the story, they wanted to be reading a different story. Again, you need to treat these sorts of questions the same as a negative review. If it’s in a published or on-line review, don’t respond. If a reader is asking you directly, say as simply and sincerely as possible, “I’m sorry you didn’t enjoy it.”
You can elaborate a little bit. “That isn’t the story I was telling” or “This was the best way I could think of to tell this particular story with these characters” or something like that. It is so tempting to try to convince the person that what you did was the right thingFinally, remember that sometimes the reason you got a bad review has nothing to do with you or your story. Mark Kloos recently shared on twitter: “Don’t fret about your Amazon reviews. I just got a three-star review because my novel isn’t a 36-count package of Jimmy Dean sausages.” And he included a screen capture of the review. While technically this violates the negative review advice above, it’s clear that the reviewer wasn’t actually reviewing the book, and Kloos didn’t ask people to go harass the reviewer.
That example leads to the final piece of advice from several of my choral directors: “Once the concert is sung the only thing you can do is be proud of the parts that went well, laugh about the parts that didn’t, and start practicing for the next performance.”
I like to repeat the adage that the difference between real life and fiction is that fiction has to make sense. Storytelling is, among other things, the craft of weaving an illusion. You are attempting to evoke in the reader a dream. You want that dream to be similar to the one you’re holding in your own mind as you craft your story. It needs to feel real, while also making sense—narrative sense. In a narrative, the events that happen are always connected to each and to the overall story. Things happen for reasons that relate to the intent of the participants and the meaning of the plot. But the real world seldom makes sense narratively; real life events that take place near each other are often unconnected, for instance.
The paradox of storytelling is that you can’t achieve that sense of reality and making sense by slavishly imitating the real world.
That is especially true in dialog.
So, dialog isn’t about exactly transcribing the real way that people talk. It is about creating the illusion of the way people talk, while omitting parts that don’t move the story forward. To get back to the list that’s being shared around: it isn’t that you can’t use any of those suggestions, it is that you should not dump all of them in just because they’re on the list.
If, like me, you read a lot of fanfic and self-published fiction, you see a lot of these awkward efforts to replicate in dialogue certain quirks and eccentricities of expression that people make in real life, or that actors do as part of their delivery of lines. Unfortunately, these replications often serve as a distraction rather than characterization. For example, in dialogue you might mention that when a character responded to a question with the word “yep” that the character popped the p at the end of the word. If the reader has ever known a person who does that in certain circumstances, or seen an actor doing it in a television series, say, they get it. If they don’t, they’re just puzzled. And during that moment that the reader is trying to figure out what it means, they are no longer in your story. You’ve bounced them from the narrative. You have destroyed the illusion you were so meticulously crafting. You are inviting the reader to stop reading your tale.
And if you do more of those things, you aren’t merely inviting the reader to leave, you’re actively chasing them away!
In real life people say “uh,” “um,” and similar non-words a lot more often than we realize. It’s a pause when we’re trying to pick a word, or figure out how to respond to something or just thinking through the situation we are discussing as we’re talking. If you put those non-verbal filler sounds in as often as they happen in real life, it becomes very annoying to read. Part of the reason we don’t notice is because the tone of voice and the cadence of the sentence (and if it’s a face to face conversation, facial expressions and other body language) give those non-words meaning to the listener. But the reader isn’t getting all of that. So, when writing dialogue, we use those non-verbal sound indicators more sparingly. We deploy them when we want to indicate the speaker is at a loss for words, or is uncomfortable in the situation, or something similar.
In real life we repeat words a lot. We may put the same word in to a sentence more often than it is needed. Like, we really can, you know, say what we mean to say, like, really, you know, in a really messy way. You know? And you can write a character talking in that manner, but you’ll find it’s difficult to keep up the pattern. And again, the reader needs to know why you’re doing it. If you have a character that is supposed to be annoying your protagonist, having all of their sentences ramble and repeat can make your reader as annoyed with the character as your protagonist is. Again, the key is to choose the non-standard grammar for a narrative reason.
Then there are facial expressions and gestures. I have a really bad habit during first drafts of having my characters nod a lot. You can read through a scene I just wrote and sometimes a third or even half of the switches in dialogue begin with the character who is about to speak nodding. And it’s really annoying after a while. In real life, people nod their heads, shake their heads, tilt their heads, waggle their heads and so on while talking. But just as with “uh,” we need to use it a bit less often than it happens.
The first time someone pointed that out in a rough draft, I went through and changed all of those “so-and-so nodded” to other things. I changed each and every one to a different thing. So the first character, instead of nodding, grinned. And then the next character wiggled his hand to indicate indecision. Then the first character frowned and tilted his head. And so on. When I read the scene to myself aloud after revising it, I started laughing part way through, because it sounded as if the two of them were dancing around each other in an elaborate musical number. So I had made it worse, not better. Not every line of dialogue needs a description of what the character is doing with their body. It is perfectly okay to use “[name] said.” Multiple times.
It’s also all right, if there are only two people in the conversation, to skip the name altogether every now and then. But don’t do it more three or four lines in a row. The reader will get confused, and it is really annoying to have to go back and count, “Susan, John, Susan, John…” when you lose track. And it is super duper annoying when you do that and find it doesn’t work. You get to a line that by your count should be John, but it says ‘Susan frowned in thought. “I don’t think so,” she said.’ I have had that happen in a book published by a large publishing house. I assume that during an edit round some lines of dialogue were removed, and the author didn’t double-check that everything still flowed.
On the other hand, you can get away with a lot of things in dialogue that don’t fly in the narrative portions of the text. People talk in sentence fragments and make grammatical errors, so you can do that in the dialogue. But make sure you know why you’re doing it. And don’t over do it.
While we’re on the subject of dialogue: someone sent me a link to this excellent blog post on how to punctuate dialog. Even if you think you know how to punctuate dialog, go take a look. Everyone can use a refresher every now and then.
And then fan art for a book that seemed to be about teen wizards (but not characters I recognized) started appearing on my tumblr dashboard for a series that I’d never heard of: the Simon Snow series. Except there is no Simon Snow series. One of the novels by Ms. Rowell that I’d put on my list was entitled, Fangirl, and the blurb was that the main character, Cath, is just starting college, and that for the last few years her life has been dominated by her love for a series of urban fantasy novels. And these novels star a young man named Simon Snow.
In order to write convincingly about a fan who is very active in writing fanfic and has a number of close friends within the fandom, Rowell had to plot out a fictitious fantasy series. At least enough for the characters to talk about it as if it were a real series. Fangirl was a success, and received a lot of praise, particularly in sf/f circles, despite not being a fantasy story itself, because the portrayal of fannish culture was considered spot on.
After finishing that book, Rowell wound up writing a Simon Snow book. She didn’t write the entire series, she wrote a book that can be looked on as the next book that was published after all the books that Cath and her friends had been fans of in 2013 (when Fangirl was published). So, Carry On is not a sequel to Fangirl. Carry On is a sequel to the fictitious series which is talked about in Fangirl.
The magical world of Carry On bears a strong resemblance to the Harry Potter series, though it isn’t a parody or a satire. It also bears certain parallels to other young adult fantasy series. The plot seems straightforward, at first. Simon Snow attends a wizarding school called Watford. He was not born in the wizarding world, but he has immense power and various prophetic signs indicate that he is the person who is destined to defeat the Insidious Humdrum. The Insidious Humdrum is a mysterious being which, when it attacks, drains all of the magic out of the area, leaving what appear to be permanent dead zones where wizards and other magical creatures become powerless. Simon doesn’t know how he is going to defeat this creature, and has so far failed to master his magical powers. His powers are massive, but out of his control, and things tend to get destroyed when he tries to use them. His roommate at the school, Baz (full name, Tyrannus Basilton Grimm-Pitch) is Simon’s nemesis at school, and is assumed by everyone to be the person destined to try to kill Simon when the big battle with the Humdrum finally happens.
But the story isn’t really about the conflict between Simon and the Humdrum. It’s really about the nature of prophecy, what does it mean to be a chosen one, and how people (whether mortal politicians or master mages) twist belief and hope to fit their own agendas. It’s about identity, not just what it means to be a hero or villain (or the fact that it is seldom either/or), but there are allegories for ethnic identity issues and class identity issues. Oh, and more than a bit about sexual and romantic identity (which aren’t always the same thing).
There is a ghost story. There are several mysteries. And there is even a love story. There are battles magical, political, and personal. And it all hangs together very well. I have to admit, I think the wizarding world portrayed in Carry On makes a lot more sense than the world of Harry Potter, or a number of other fantasies of similar ilk, even though the magic part of the story isn’t the main focus of the plot.
I’m not sure that those two observations are unrelated.
I enjoyed the book a lot. I didn’t find most of the plot developments surprises. As one reviewer put it, the revelations as the story moves along feel more like confirmations of your existing suspicions than plot twists. But again, I don’t think that’s a bad thing. I think that’s part of why the story hangs together better than some other books we could name.
I enjoyed the book a lot. It didn’t end quite as I hoped it would, but it ended in a way that felt right and satisfying regardless. It did make me wish that some of the series and fantasy books had handled their characters as well as Rowell does. I hope that the next person who undertakes this sort of tale takes note.
It’s been a really long time since I wrote any book reviews, so I’m going to try to get back in the habit of writing them more often.So, let’s start with Aristotle and Dante Discover the Secrets of the Universe by Benjamin Alire Sáenz. This novel is set in the late 80s and concerned a Mexican-American teenager named Aristotle “Ari” Mendoza. Ari is the youngest child in his family, but there’s a significant age gap between him and the next oldest. The other kids were born before Ari’s dad went off to fight in Vietnam, while Ari was conceived after his father returned. Ari is troubled by at least two family secrets: his older brother was sent to prison when Ari was too young to understand what was going on, and no one in the family will talk about what happened. The other secretive thing bothering Ari is that his father never talks about his experiences in the war, and many other things which Ari thinks might be important.
Ari narrates the book, and frequently describes himself as having no friends, until one summer day when he met Dante Quintana at the city pool. Dante discovers that Ari is hanging around in the shallow end because he doesn’t know how to swim. So Dante undertakes to teach him, and soon Ari and Dante are inseparable.
Even when Dante confesses he is gay, while Ari assures Dante that he is not, their friendship remains strong.
The official summary the publisher slaps on the back cover is: “Aristotle is an angry teen with a brother in prison. Dante is a know-it-all who has an unusual way of looking at the world. When the two meet at the swimming pool, they seem to have nothing in common. But as the loners start spending time together, they discover that they share a special friendship – the kind that changes lives and lasts a lifetime. And it is through this friendship that Ari and Dante will learn the most important truths about themselves and the kind of people they want to be.”
That summary doesn’t really do the book justice. But I can’t explain much more about the plot without giving things away which I think a reader will enjoy discovering right along with Ari and Dante. Two different events that could have been tragedies happen over the course of the two summers plus that the book describes. Neither comes out of the experiences unscathed. Along the way both young men make important discoveries. And yes, by the time the book is over, they really do discover secrets of the universe.
One of the things I love about the book is that despite Ari feeling that his father is keeping part of himself distant, the relationship between each of the boys and their families is close. Each set of parents express their love and respect for their sons in different ways, but despite the secrets in Ari’s family, the relationships being shown here are not dysfunctional. That’s refreshing in itself.
The story explores lots of themes. Yes, there’s a coming of age through-line, but the novel also deals with identity (particularly intersectional identity: class, ethnicity, and sexual orientation), social expectations (what does it mean to be a man; what does it mean to be a Latino, et cetera), familial expectations, the nature of friendship, the meaning of the many kinds of love, as well as what it means to find answers. The characters feel real, their problems feel real, and nothing in the plot every requires any of the characters to be stupid. Yes, the teen-age characters (not just Dante and Ari) make foolish choices, but they are realistic foolish choices.
Unlike some books (and movies and series) I could name, none of the characters suddenly start acting idiotically so the plot can go a particular way. This kind of storytelling leaves me, at least, rooting for most of the characters—and that is not at all a bad thing!
I’m hardly the first person to notice that Aristotle and Dante Discover the Secrets of the Universe is an awesome book. It was awarded a Youth Media Award by the American Library Association, as well as a Pura Belpré Narrative Medal, the Stonewall Book Award, a Michael L. Printz Award for the best writing in teen literature, a Lambda Literary Award, and an Amelia Elizabeth Walden honorable mention. Perhaps the most interesting recommendation I have read of it was a fellow subscriber to a literary mailing list who said that when another award-winning novel had wrenched her heart, Aristotle and Dante Discover the Secrets of the Universe had restored her soul.
This all may sound like hype, but the novel really is very good. I loved it so much, that after finishing the book, I bought the audiobook (narrated by Lin-Manuel Miranda who does an incredible job), and listened to it again. (Spoiler: I cried and laughed at all the same points the second time through as I did the first).
If you want a story that will restore your faith in humanity—and restore your faith that good books are still to be had—you can’t go better than Aristotle and Dante Discover the Secrets of the Universe.
One thing I miss, now that smart phones are ubiquitous, is seeing what other people are reading on the bus. Seattle is a city of bibliophiles and other literary people, and for most of the 30+ years I’ve been riding public transports in Seattle, I could always count on seeing interesting books on my commute. Sometimes I might see someone reading a book I love, and I’d find myself grinning—hoping they were having as much fun with the book as I did. Other times I would see a title I had never heard of, and find it intriguing enough to look up more information on the book when I had a chance. Other times I would see someone reading a book that I despised, and I would wonder what sort of person would read that.
There are still people reading hard copy books on the bus, of course, just nowhere near as many as there used to be. Now instead of seeing a dozen books or so on my morning commute, there are a dozen or so people staring at their phones or iPads or Kindles.
Which still warms the cockles of my heart, because I love reading, no matter what form it takes.
And I’m certainly not going to give up reading (and some mornings writing) on my iPhone. Among the downsides of reading a hardcopy book on the bus is the time spent digging it out of my backpack, and then later needing to stop reading far enough before my stop to put the book away and get my pack zipped up and situated. There was also the need to decide whether to pull out my book or my notebook and a writing implement. And the frustration after I chose when I discovered I didn’t seem to be in the right headspace to concentrate on that book, or to write.
With the phone, I can slip it out, fire up a book, and start reading. If I want to make a note, or get another idea I want to write down, it’s just a couple of swipes and taps with my thumb to switch to a writing app, write it down, then get back to the book.
Of course, there is a bit of the paradox of choice that the phone amplifies. Occasionally I just can’t decide which of the many choices that are on the phone to read. Which of the several books (because I’m always in the middle of more than one) to pick up, or should I open one of my news apps and catch up on the world?
Having all those choices doesn’t usually paralyze me, but I do often dither for at least a few minutes. So maybe I’m only kidding myself when I say I get a bit more reading time in now that I’m not fumbling with getting the book out and putting it away again.
But I don’t think so. For one thing, with the phone, I can become obliviously lost in the book right up to my stop, then jump up, slip the phone into my pocket as I’m moving to the exit, and get off the bus.
It’s Banned Books Week, which as both a writer and a reader is very near and dear to my heart. I have been a long time member/supporter of the Comic Book Legal Defense Fund, which is one of the organizations at the forefront of fighting book banning. You can support them any time, but this week there is a special offer, Humble Bundle is offering a Pay-What-You-Want Forbidden Comics Bundle. Pay minimal amount and you can download eight comics/graphic novels and an audiobook. Pay more than the current average price and you get an additional seven-plus comics (more will be added as the week goes on). These bundles are a great way to raise some money for this good cause, and you get a look at some of the kinds of comics that have been banned or challenged in various jurisdictions.
And all the reading and thinking and mind expanding requires some mental leveling up, so it’s a good thing that today is National Coffee Day: Starbucks, Dunkin’ Donuts & More Celebrate With Free Deals!
It used to be that I had a rough measure of how busy I’d been by looking at the pile of books beside the bed. For most of my life, going back well into childhood, there has always been a pile of books beside my bed. These are books that I intend to read soon. Sometimes the ones on top are books I am in the middle of reading. I am almost always in the middle of reading several books at the same time, which complicates things. The pile shrinks as I finish books (or, occasionally, as I get far enough into a book to realize that no, I don’t want to finish this one). And it grows whenever I go to a bookstore, or a convention, or browse piles of free books, or… well, you get the picture.
Certain things about the pile have changed over the years, of course. When I was middle school aged, for instance, much of the pile was made up of library books. The pile changed out a lot quicker, back then, as well. I went through a period of a couple of years where I read at least one entire novel nearly every day. So I would take books back to the library every few days and bring home more. In high school my pace slowed down a little bit, and a much larger proportion of the pile was paperback books, usually picked up at one of the used book stores. I did a lot of trading books back in to buy more back then. I also borrowed a lot of books from friends (and loaned a bunch).
I’d also been a member of the science fiction book club for a long time. I got suckered into it when I was about 13 years old. I say suckered mostly because I didn’t really have a concept of just how difficult it was to remember to mail back in the little card that said, “No, I don’t want the automatic selection this month.” Which I had to do most of the time if for no other reason that, as a kid, I didn’t have the money to pay for the book and the shipping. I did acquire about a shelf worth of books that way, though.
But most recently the pile by the bed has become a lot more static than it used to be. Mainly because I don’t read hardcopy books nearly as much. Most of my reading is ebooks, switching between reading on my phone or iPad. The apps do a decent job of keeping track of where I left off on the other device when I switch. It’s just so much easier, when I find myself stuck in line at the bank, let’s say, to pull out the phone and open either iBooks or the Kindle app.
It didn’t happen all at once. My gateway drug, as it were, to non-paper books was the audio book—for which I usually blame my husband. He loves to listen to audiobooks, mostly sci fi and fantasy, while he plays video games. Usually listening over the stereo in the computer room. Except in the summer, because the fans make it a little hard to hear clearly, so then he switches to headphones.
I don’t know how many times I went into the computer room to do something that should have taken 5 minutes or less, only to wind up sitting in there for a half hour or more listening to the book he was listening to. Of course, often if it was a book that we also owned in hardcopy, I’d head into the other room, find the paper book, and sit down to finish it off; because of course I can read it myself much faster than the reader can read it aloud.
Though I have to admit that the real culprits are a pair of Jims. James Marsters and Jim Butcher, to be exact. But they had some accomplices.
I was in my late thirties when, somehow, I deluded myself into the idea that signing up for a book club would be a good idea, again, so I was a member of the science fiction book club, again. At least by then you could do your ordering and/or declining to order on-line, so the number of times I got books I didn’t mean to was a lot lower. I’d been mostly declining, only buying a few books a year for quite some time. I bought my first Dresden Files books because I’d had a few friends recommend the books, (generally by expressing shock when we were discussing the short-lived TV series when they found out I’d never read the books). In early late 2007 or early 2008 the book club had a deal on a four-volume set that contained the first eight books in the series. So I bought them, and then they sat in the pile by the bed for a few months. After being laid-off from the place I’d worked at for more than 20 years, one night when I was between contract jobs, I picked up the first volume and started reading. I stayed up all night reading through the first two books. Over the course of the next week or so I read through the rest of the series.
While chatting about the series with another friend, she expressed surprise, given what a big fan I was of the character of Spike from Buffy the Vampire Slayer and Angel the Series, that I’d never gotten the Dresden audio books. “I can have Spike read bedtime stories to me?” I asked, in disbelief. The original distributor of the audiobooks even offered a free download of the first four or five chapters of the first book!
One of the first purchases I made once I landed a job as a “regular employee,” was the audio version of the first Dresden book. Which began my pattern of reading the paper copy of the book first, then buying the audiobook and listening to it again and again…
I have noticed lately that my book buying habits have made another change. There are books I still buy in hardcopy. I am easily lured into used book booths at conventions, for instance, and almost always buy something. But generally speaking, I get annoyed for new books if I can’t find an e-book version. In the last year or so, there are books that I’ve just decided not to get because they are only available in hardcopy. If I really like a book once I’ve read it digitally, I may well buy a paper copy to cuddle up with for re-reads, but the e-book has become my preferred format.
I don’t think that’s necessarily a good or bad thing. Though given how much energy we’ve spent, over the years, trying to keep the book shelves in order, occasionally going through the lot and pulling out books we know we’ll never look at again to give away or attempt to sell, I have to admit that letting books pile up on the computer is a whole lot less work.
But it’s also the convenience of always having a whole bunch of books in my pocket that wins the day. So the pile by the bed changes much more slowly, now. I don’t think it will ever go away entirely, but it is no longer an indicator of how much reading I’ve been doing.
Many Waters is a sequel to that book, and it is the first one where Sandy and Denys take center stage.
Before I get into my review of Many Waters, I want to share one amusing personal incident: by the time I was in the fourth grade we had moved several times. For example, I had spent part of third grade not only in three different school districts, but each was in a different state. Part way through fourth grade we moved yet again. At the new school, we were assigned to read A Wrinkle in Time, and then give a book report. My report came back with a low grade in part because I had supposedly misspelled Murry, the last name of the family. I had to show the teacher in my own copy of the book (since the school copies had been taken back already and passed on to the other fourth grade classroom) that Murry is how it is spelled in the book. It didn’t occur to me until years later that this meant the teacher probably had never read the book himself. So on what basis was he grading everyone’s book reports?
So, what did I think of this book? … Read More…