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.”
So in the old days I would have piles of books around my typewriter, some with note paper stuck in them to hold a place2, others with multiple bookmarks7 stuck in them so I could find multiple facts scattered over multiple pages, and so forth. The internet has only changed the amount of physical exercise that is necessary to run down rabbit holes on the research front, at least for me.
Tools and implements is another class of thing8 that can be either a help or a procrastination trap. But tools are important. So while it is possible for procrastination to latch onto the exploration of new tools as a means to keep you from writing, talking about good tools can also be a help in the writing process. Therefore, here is a list of my current favorites:
- Scrivener 2 – the absolute best writing project managing tool/word processor available for Windows, macOS, or iOS, bar none. For all the features it packs, it’s also incredibly affordable! It’s multi-platform. I use it on both of my Macs and my iPad, and they make it easy to move back and forth. If you don’t have an iPad but do need to work on other platforms, you can use the Sync to External Folder feature in conjunction with Dropbox or Copy or Box to edit files in application that can open Rich Text Files when you’re on the go, then sync back to Scrivener on your Windows or macOS box later. I’ve used this latter feature before the iOS version was available, and it worked well. Not as cool as having all of the features of the full product on my iPad or iPhone works now, but… .
- Scapple – by the same people who make Scrivener, this is a brainstorming/outlining tool. I’ve used it for charting plots and subplots that had gotten out of hand. It’s also really good at family trees and charting out character relationships.
- iA Writer – a full featured word processor available for macOS and iOS. I use it when I need to format something I made in Scrivener, or just to type out notes for later. I’m particularly enamored with the iOS version’s built-in “share as PDF” because I’m often working on large projects in Scrivener on the iPad, and just need to send a single chapter or some other small bit to someone for comments, et cetera.
- Honorable Mentions: There are some products that I used to use a lot more than I do. Particularly before the advent of Scrivener of iOS.
- Textilus – iPad text/rtf editor. This is a good word processor for working from iPads and integrating with Dropbox and similar cloud sharing services.
- SimpleNote – this is a good multiplatform Note taking program that is useful for getting down something quickly, that will automatically be available on all of your devices so you can copy into a main writing program later.
- Pages – Apple’s free word processor that works on macOS, iOS, and iCloud. I liked the mac version of the program a lot before they decided to unify the features in all versions. It’s still a good program and they keep updating it. Just not quite as good as it used to be.
- Scrivo Pro – A Scrivener-like word processor for iOS when Scrivener’s official word processor that could read Scrivener projects in their native format if you saved them to Dropbox. It was pretty good. I used if for several months until Scrivener for iOS became available.
- WriteRoom – If you need a good, simple distraction-free writing program on the Mac, I highly recommend WriteRoom for macOS. I originally bought the iOS version to write on the bus and other places when I was away from my computer back in the days before I had an iPhone or iPad (it ran on my iPod Touch just fine). The software maker has stopped supporting the iOS version, as it wasn’t generating enough income to justify the work. Since it hasn’t been updated for a long time, it will still work if you already have it installed on your phone, but it’s clear that iOS is going to stop supporting it, so I finally have stopped using it on the phone.
- RhymeGenie – I use this for poems and song writing… and for composing prophecies14.
- AffinityDesigner – has become my replacement for Adobe Illustrator for many illustration tasks, including drawning maps for my fantasy stories.
- iTunes – I often listen to music while I’m writing. Not just random music; I make special playlists for certain characters or projects. My oldest playlist, called uncreatively enough “Writing”15 was created in 2003, when iTunes first became available for Windows18. That’s right, I used iTunes for three years before I owned my first iPod.
- Leuchtturm 1917 – These notebooks are awesome and are available in a lot of cool colors. Occasionally I like to write on paper. Certain types of thinking process just work better for me that way. But I know it doesn’t work for everyone.
- Goulet Pens – I love a good medium- or broad-tip fountain pen for fun colored inks. Again, when I’m in one of those moods where I need to write it needs to be a good pen or…
- a 0.9mm or 2mm mechanical pencil – my very favorite pencil is a tigerwood mechanical pencil that was handmade by Pandora House Crafts. If I don’t happen to have that specific pencil with me, any mechanical pencil with at least a 0.9mm lead will do.
- And of course, 20+ paper dictionaries at home – I use the paper dictionaries often, because they tend to have more information than the affordable software versions. But the software ones don’t usually require me to stand up, so I often go to them first:
- Shorter Oxford – I have this version of the Oxford English Dictionary20 installed on my Mac, iPad, and iPhone.
- Merriam-Webster Dictionary & Thesaurus21 – I have more than one electronic version of this dictionary on all my devices.
- The Chambers Dictionary22 – I keep this on my Mac, iPad, and iPhone.
- Chambers Thesaurus – Companion to the Chambers Dictionary.
- WordBook Universal English Dictionary and Thesaurus – another one that I’m not sure why I have it on iPad and Mac, but not the phone.
- SPQR – a Latin dictionary app on my iPad and iPhone, very useful when I need to make up incantations for one of my wizards or sorceresses.
- American Heritage Dictionary23 – I have this one on the iPad only.
Anyway, so that’s my current set of favorite tools. Though the truth is that my real tools are sentences. I can compose those with word processors, typewriters, pen & paper, or pencil, or technically anything I can scratch symbols into a medium with. The important thing is to start writing.
Neil Gaiman24 is fond of saying that the only secret of writing is to just keep putting one word after the other. That advice is true and succinct. It is also extremely difficult to do, while sounding quite simple. We have to make ourselves sit down and write. That’s what makes a writer.
1. This might be less true for people who didn’t have multiple encylopedia sets in their houses.
2. And with notes written3 on said pages related to things I wanted to do with the information in said book.
3. Well, most often scribbled. Have I mentioned that my handwriting is atrocious4?
4. Part of the problem is that I learned how to type on a mechanical typewriter when I was ten, for reasons. And so I stopped doing the work at school where they were taught us cursive writing. So I only ever formally learned how to print5
5. If pressed, I can produce by hat writing in cursive, but I have to visualize what the letters look like, and then draw them individually. I just don’t have the muscle memory to write. It’s is painstakingly slow and frustrating6.
6. But I still consider learning to write that way as an archaic and obsolete waste of time. Learning how to read it is much, much easier than writing it.
7. Another thing that has changed a lot in my life the last decade or so: I no longer go to great lengths to save and collect bookmarks. It used to be extremely important to have physical bookmarks I could stick in books. I still am usually reading multiple books at the same time, but more than half of them are e-books, so I don’t need physical bookmarks any longer. And it’s kind of sad.
8. thing Old English, noun 7. That which exists individually; that which is or may be an abstract object of perception, knowledge, or thought; a being, an impersonal entity of any kind; a specimen or type of something. Also, an attribute or property of a being or entityThat which exists individually; that which is or may be an abstract object of perception, knowledge, or thought; a being, an impersonal entity of any kind; a specimen or type of something. Also, an attribute or property of a being or entity9.
9. Please note that this is the seventh sense of the word to be defined in the Oxford dictionary, while it is closest to what I think most people would say is the primary definition. The first definition in Oxford is “A meeting, an assembly; a court, a council.” which happens to be the oldest known meaning of the word, but only seems to be known among most modern speakers of English who are also into the history of England and Northern Europe. I used this particular meaning in a draft scene in my fantasy novel series without thinking, and of the people in my Writers’ group, only my husband10 understood the meaning I was going from when I used it. So I switched to on Old Norse derived word instead, folkmoot.
10. My husband who has been described by more than one of our friends as “the most capable man I know” and his areas of expertise include computers, repairing computers and other electronics, bartending, history, obscure languages, science fiction and fantasy, science, electrical engineering, farm equipment repair and maintenance, quantum mechanics, chemistry, and cooking11
11. The latter is an understatement. The state he lived in at the time allowed children as young as 14 to work as prep cooks12, and that’s one of the two jobs he held down at that age. I have commented many times that if you want to be amazed just hand my husband and nice sharp knife and a box of vegetables and ask him to assemble a veggie tray. He will chop up all of the veggies you give him, no matter what they are, into exactly uniform slices, in a time frame that will make you suspect that he is actually super powered. I am not exaggerating in the least13.
12. Most state in the U.S. don’t allow children under the ages of 15 or 16 to work around commercial kitchen equipment, because limbs can be chopped off, basically. Although the are often exceptions carved out for children working in family businesses, which is how my Great-grandmother and a Great-uncle got away with teaching me how to drive a truck when I was about 12 years old.
13. When people who have only interacted with him in certain social situations have scoffed at this, I have smirked, because I’ve seen his school records, which include IQ tests, and most of the scoffers are nowhere near as smart ass he is13.
13. No, I really don’t know why he settles for such a jerk as me. I really don’t.
14. I have a lot of characters in my fantasy universe who can see the future: the Oracle, Madame Valentina, Brother Ishmael…
15. Followed by “Writing II,” then “Laying Out an Issue of the Fanzine” then “Writing Faust and “Writing III.”16
16. I have since become slightly more creative with playlist names17. The playlists I’ve been using while working on my latest novel have names such as “Dead Witch,” “Ballad of a Lost Soul,” “Only the Wicked,” “Ballad of a Would Be Dark Lord,” “Zombie vs Dragon,” “Ballad of the Unrepentant,” “Night of the Monkey’s Uncle,” or “Ballad of Dueling Masterminds.”
17. I previously thought that I had hundreds of playlists, but since I recently merged together two previously separate iTunes libraries18, I now really I have nearly 4000 playlists.
18. Remember that I started using iTunes many years before owning on iPod (and later an iPhone). So my main iTunes library started on my old Windows 98/Windows 2000 machine, was imported to my early 2009 model Mac Pro Tower, and was updated over the years as I bought music and finished importing the rest of my old physical CD library. Meanwhile, the machine that slowly took over my day-to-day computer was on old white plastic Macbook, which was built from an import of one of on old Windows laptop that only had a subset of the Windows desktop, and then was augmented and updated to a Macbook Pro, then updated to a newer Macbook Pro, and then for a bit over five years I tried to maintain to similar libraries: one on the old Mac Tower which contained six-and-a-half terrabytes of internal storage, and my Macbook Pro laptop that only had a a 512 gigabyte drive, and therefore not enough room for my entire music, video, and film library plus all my story files and so forth.
19: I have a lot of characters in my primary fantasy series who can see the future in various ways: the Oracle of the Church of the Great Shepherdess, Madame Valentina (a.k.a. Alicia), Brother Jude, the Zombie Lord, Brother Ishmael, Mother Sirena, Brother Theodore, Mother Bedlam…
20. The platinum standard of English language dictionaries. In hard copy I have the Oxford American Dictionary and Thesaurus, a pocket version, as well as the single volume version of the unabridged that you need to have a good magnifying glass in order to read.
21. Genuine Merriam-Webster dictionary is the gold standard of U.S. desk dictionaries. I have a couple different editions of the Collegiate version in hard cover, a pocket version, and a hard cover of the giant unabridged Third International.
22. Chambers was the dictionary most commonly found on bookshelves and desks in the U.K. for years, much as the original Merriam-Webster was in the U.S.
23. The American Heritage Dictionary has a very interesting history. A publisher and dictionary enthusiast was angry when the Merriam-Webster Third Edition shifted to a more descriptive philosophy, and so set out to make a competing dictionary. Then he hit on an interesting marketing scheme. They published a huge unabridged version which they offered for sale at less than cost to public libraries and schools, along with a discounted pedestal or lectern that ensured the dictionaries were prominently displayed in libraries. Then after getting these dictionaries in hundreds of libraries and school for a few years, they released a subset of the dictionary as a desk edition, which made the desk edition an immediate best seller.
24. Winner of the Newberry Medal, numerous Hugo Awards, Locus Awards, Nebula Awards, the Bram Stoker Awards, the Carnegie Medal, Eisner Awards, British Fantasy Awards, Shirley Jackson Awards, a World Fantasy Award, a Harvey Award… I could go on and on.
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.
Which is exactly what homophobes have been sniggering and making fag jokes about with Le Fou since Disney released the animated version of the movie. Gaston is a parody of hetero hypermasculinity, and Le Fou is is craven, clownish sidekick willing to do anything at all to get the slightest bit of attention from Gaston. Le Fou’s lack of manliness in the animated film could be rationalized as being there to throw Gaston’s exaggerated masculinity into sharp contrast. Okay. Except that is exactly what the Hollywood sissy/coded gay sidekick has always been: he’s the example of what a “real man” isn’t. His whole point it to prove that unmanly men are jokes, at best. Not real people, but punchlines.
So they are taking the implicit hateful characterization and making it an explicitly hateful characterization. Thanks, but no thanks.There will be people who insist that we shouldn’t judge it until we see it, but they’ve given me enough information that I already know they have messed this up. The fact that they decided to announce it, for one. Just as if a person begins a statement with, “I’m not a bigot, but…” we all know that pure bigotry is going to follow, if you feel the need to announce you’re enlightened and inclusive, you don’t know what those words mean. The director has described the classic negative stereotype (confused, obsessed with a straight man) is what they’re going for. Worse, they’ve referred to it more than once as a moment. Just a moment. You know why it’s a moment? Because they are already making plans to edit that moment out of the international release, because they knew as soon as word got out that countries would start threatening to ban the film. Heck, Alabama is already up in arms about it!
That means that it’s a tacked on joke. It’s not part of the plot. It’s not a meaningful part of Le Fou’s characterization.
Even if they do something with it. Let’s say that at the end of the film they have a moment that implies maybe Gaston is ready to return his feelings? What message does that send? It tells us that hating women (Gaston’s exaggerated masculinity includes a lot of misogyny in the animated feature, just sayin’) or being rejected by women is what makes men gay. And, oh, isn’t that great inclusion?I mentioned that the Beauty and the Beast revelation was the second time this has happened this year. Previously it was Snagglepuss. Yes, DC Comics/Warner Brothers announced that the Hanna-Barbera cartoon character, Snagglepuss, was going to be reimagined in a new comic book series as “a gay Southern Gothic playwright.” Literally my reaction on twitter a nanosecond after I saw the first person retweeting the headline was, “reimagined? But that’s what he already was!”
Snagglepuss was a version of the sassy gay friend from the beginning. He was protagonist of his cartoon series, which wasn’t typical for the sassy gay friend (who is more typically a sidekick to one of the lead characters), but Snagglepuss broke the fourth wall constantly, addressing the viewer with his arch asides and sardonic observations. He was the viewer’s sassy gay friend, in other words. And he was cheerful and optimistic and always trying (but usually failing) to improve his life in some way. Despite the many setbacks, he remained cheerful and upbeat.
So the DC Comic (besides being drawn by an artist who has apparently never seen an athropomorphic character before—seriously, go hit that link above and tell me if that isn’t the worst comic book artwork you’ve ever seen!) takes the happy, upbeat fey lion and turns him into a bitter old queen. Again, thanks but, no thanks!
Coded queer characters have been appearing in pop culture for decades. Their portrayal as comic relief or as villains (and sometimes both) sent a clear message that they were not normal people. They are never the heroes. They can be loathed as villains, or tolerated and laughed at as sidekicks, but they will be lonely and unloved in either case. Neither of these supposedly inclusive announcements changes that homophobic message. It’s not, contrary to what certain evangelical hatemongers are saying, indoctrinating kids to be accepting of gays. It’s instead reinforcing the same old bigotry: we don’t matter, we are jokes, we are never the heroes, we are never loved.
Just another means of erasing the truth of our existence. No thanks!
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.
Whether you write your story in order or more free form, there is usually some form of modularity within the story. A very short story may consist of a single scene, but longer stories are usually broken up into multiple scenes, groups of which may be gathered into chapters (or acts), and so on.
These modules of narrative provide a means of packaging bits of your story into digestible chunks. How you structure them controls the rhythm of the story, providing a sense of movement through time and or space.
And they can be tricky.
Unfortunately, the way I do a lot of my own writing is intuitive, now. I’ve been writing fiction since grade school, and I started reading articles in magazines such as The Writer and Writer’s Digest also during grade school, so I’ve internalized a lot of processes to an extent that I do them without a lot of conscious thought. My honest first answer to the question, “How do you decide where a chapter ends?” is, “It ends when you get to the end.”
So let’s start with some definitions. These aren’t necessarily authoritative definitions. You’ll find a lot of writers with similar but still different definitions of these things.
A scene is a building block of the story. You can think of it as a single brick in a wall, or the next pearl on a necklace. A scene usually happens at a single location and for a short, continuous period of time. Every scene in your story should fulfill a purpose. Ideally they should serve several purposes. The sorts of purposes scenes can serve are:
- Advance the plot
- Introduce a new character, theme, or problem
- Create suspense
- Establish or develop the setting, a character, or a problem
- Provide information the reader will need later to understand the action
- Foreshadow coming events
- Create atmosphere
These aren’t the only purposes scenes can fulfill. It can be argued that some of the purposes I have listed are subsets of others. Creating atmosphere could be thought of as a specific type of establishing the setting and problems facing the characters in it. I’ve seen other lists of possible purposes for scenes include as separate items things with which, to me, are simply subsets of the ones above. For instance, a lot of people list building sympathy or antipathy for a character as a separate purpose, whereas I think of that as just one type of establishing or developing the character. But those are quibbling details.
The important thing to remember is: a scene shouldn’t be in your story if it doesn’t serve one of the purposes for furthering the story.
I like to write scenes from a particular viewpoint character. Most of my stories are written in third-person subjective. That means I look at the scene from a particular character’s perspective. I’ll tell you what that person sees, hears, and feels, but without getting into the head of any of the other characters in that scene. So that means that if I need to get into another character’s head, I need to have a separate scene for the character.
So you can think of a scene as a single incident in the chain of your story. For instance, “When the lieutenant asked the maid about the abbey,” or “When the young noble spoke to his imprisoned mother,” or “When the princess argued with her husband about a family visit.”
A chapter is harder to define. Chapters are, largely, the result of tradition, rather than having a clearly defined purpose in a story. The usual explanation is that chapters were invented when scrolls were replaced by books. A single bound book would contain stories, records, or other information that had been in a scroll. The pages which represented a single scroll would be demarked as a chapter. During the 19th century, when many novels were serialized in magazines before being gathered into a book (if at all), chapters were often the monthly or weekly installment of the story. So, one answer to why books have chapters is because people expect books to have chapters. They don’t always, of course. Terry Pratchett’s Discworld books, for instance, seldom have chapters. There are breaks between scenes, but no marked chapters.
If a book has chapters, one of the purposes they fill is to break the story into bite-sized chunks. They can provide breaking points where your reader knows she can set the story down and come back easily. Of course, one of the secrets of an enthralling book is chapter endings that entice the reader to keep going, so you don’t want the break to feel like a finale.
Chapters can help organize the story in ways other than “this happened, then this, then this…” If your characters aren’t all in the same place, you can use a chapter to gather all of the scenes which happen at the same (or nearly the same) time but with different characters. Or you can gather a bunch of scenes which have some thematic parallels (though if they are happening at very different times, you may have to take extra pains to communicate to the reader when each scene occurs).
I like to think of chapters as episodes in a serial story. If my book were a television show, for instance, with each season having an overarching plot, each chapter would represent a single episode of the series. So each scene is an incident, then each chapter is a collection of related incidents.
For me, a chapter needs to convey something that feels like a satisfying episode. Which doesn’t necessarily mean it tells a complete story, but when the reader reaches the end of a chapter, it should feel as if they have completely an important step in the journey, with a clear feeling that there is more journey ahead.
People often, therefore, recommend ending chapters on cliffhangers. And I agree with the sentiment, but dislike the terminology. Don’t get me wrong, I end plenty of chapters on cliffhangers. But the term cliffhanger is often interpreted to mean that one or more of your characters are in physical peril, and not everyone’s story has a lot of moments where characters finds themselves looking down the barrel of an unexpected gun. Cliffhanger can be any form of unresolved character tension. If one of your characters is being question by the police, most of the scene can be revealing the character’s personality while revealing various details about the situation, and a perfectly acceptable cliffhanger is for the interrogator to reveal a piece of damning evidence that ties the character to the scene of a crime. Even better if the character thought they were being questioned about a robbery, and the revelation is that there is also a dead body at the scene–you’ve raised the stakes to murder! Any situation that makes the reader asked, “Oh, no! How’s he/she going to deal with this?” can be your chapter ending.
You don’t have to end the chapter at each moment that evokes that curiosity, of course. Sometimes I have a bunch of cliffhangers within a single chapter. In a fantasy novel I’m working on right now, there’s a battle in which a dragon and her ally (a witch) attack a carriage carrying three monks and a runaway prince. I depict the battle in a number of scenes, each from the point of view of a different person involved in the battle. Each scene in the story ends at a moment where the viewpoint character has just tried to do something, or finds themself confronted with something unexpected. Then I move to a different character and show what’s happening from that viewpoint. You can do this with the other sorts of cliffhangers, too. If your chapter is a collection of scenes happening at nearly the same to characters who are in different locations, you might end each scene with that character making a discovery or realization that gives them pause.
I tend to be a seat of my pants writer in so far as I seldom write up a formal outline until I’m in a revision stage. But I usually have an idea when I start a new chapter which incidents I want the cover next. I also tend to make the chapters close to the same length. So sometimes if I notice the word count is getting higher than I thought in a scene, I’ll decide to move one of the scenes into the next chapter… which means I’ll have to think about how to make the scenes that share the next chapter feel as if they belong together.
I don’t always make chapters exactly the same length. In one of my current projects, for various dramatic reasons, I have one chapter that is a single sentence, and another that is only eight sentences.
This is a rather long rambly way to get back to my original answer: I end chapters when they end.
A lot of people think that writers are obsessed with rules of grammar. They also think that good writing requires an extensive vocabulary of obscure words. Similarly they assume that anyone who has ever had the job title of editor is perfect at spelling and is even more obsessed with grammar. Those are copyeditor skills, which is different.
Don’t get me wrong, understanding how language works and having a facility with words are important skills for a writer, but words aren’t like gears and pulleys and cogwheels, and writing isn’t like assembling a machine. Words aren’t even the fundamental tool of a writer.
It is true that I am fascinated by dictionaries and have quite a collection of them. But open up a good dictionary and skim down the page and you will notice that just about every word has multiple definitions. Words have meaning, yes, but they have lots of meanings, and not always terribly precise ones at that. For example, let’s take the word “bear,” and imagine for a moment that you were explaining our language to an alien. If you told this alien that the word refers to a large omnivorous mammal with thick fur and plantigrade feet, what would that alien make of these sentences:
- The petitioner will bear the cost of the investigation.
- My manager is a real bear.
- Before accepting the offer, bear in mind the responsibilities that come with it.
- And then the bear flashed his lights, and I knew I was going to get a ticket.
That’s only four of the six definitions of “bear” that are listed in one of my dictionaries. Now at least one of those uses is metaphorical, but the verb “bear” meaning to carry something is spelled and sounds exactly like the noun “bear” which refers to an animal. The only way you can know which meaning of the word is meant is to hear it in a sentence.
The fundamental unit of a story isn’t the word, it’s the sentence. Yes, to understand a sentence you need to know the various meanings of the words in the sentence, but not necessarily all of them. You can often understand a sentence which uses a word you never heard before. Lewis Carroll composed a poem, “Jabberwocky,” in which nearly every sentence contained at lease one nonsense word he made up for the purpose:
One, two! One, two! And through and through
The vorpal blade went snicker-snack!
He left it dead, and with its head
He went galumphing back.
Nobody knew what galumphing meant when Carroll wrote the poem, but everyone who read or heard it at the time inferred that it meant to move or run in some manner, perhaps similar to a gallop or maybe more of a loud blundering through the woods. In any case, an image of the triumphant hero making haste toward home carrying the head of the defeated creature was conjured by the sentence with the nonsense word. Never mind that vorpal was also a word that Carroll made up. Most nerds know exactly what it is: a magically sharp sword, right?
Anyway, being a writer isn’t about making text pretty. Nor is it about mastering the rules of grammar to somehow hypnotize readers with the mystic powers of predicates, prepositions, and pronouns. It’s about telling a story. In my day job I may be telling the story of what problems a particular software product solves. In my fiction writing I may be telling the story of how a thief with a cursed artifact will save the world. And here on the blog I may be telling the story of why marginalized people try to find hints of themselves in cultural events. Humans tell stories–we construct narratives–to give things meaning.
You can’t tell a story if you’re obsessing over the proper placement of a comma (the rules of which are infinitely less restrictive than you think). You can’t tell a story if you’re arguing with yourself about which synonym for brown best describes the color of your protagonist’s eyes. You can’t tell a story if you’re writing, deleting, and re-writing the opening sentence of your tale, each time changing just one adjective. Neither can you tell a story if you’re beating yourself up about the fact that you haven’t been able to finish it when you want to. It’s as useful as crying over spilled milk.
Which is about as useful as arguing about so-called rules of grammar. The final test is whether a reader understands it, and whether they care enough to get to the end. If they do, you wrote correctly.
Now, bring me a coffee, pour yourself your favorite beverage, and let’s see what kind of tales we will tell!