Pet peeves. We all have them. I gnash my teeth when I hear some scientist on NPR's Science Friday uttering the phrase, "The data says that..."
A slip up like that would have earned me ridicule back when I was in grad school (which wasn't quite during the dark ages). "It's 'say,' damn it. Data is a plural word!" I growl back at the radio.
Except, it isn't. According to the Oxford English Dictionary, the word can be used to refer to a mass of information in the singular, and in fact 60% of the usage panel accepts the use of "data" as a singular word. So my advisors were fighting a losing battle back in the 90s, but they managed to instill a lifetime hatred of what, to me, sounds like an ignorant and inaccurate usage by people who should know better. Even knowing that it's not incorrect usage, it would be hard for me to be objective about a manuscript where someone educated refers to "data" as a singular word.
When you hang out with writers (in both on and offline environments), you won't go very long without running into similar pet peeves that are similarly overstated. One person hates the Oxford comma and provides an impassioned screed about why it's (usually) not needed before the terminal "and" in a series. Another person rebuts with an equally vehement excoriation of anyone who creates the potential for lumping the last two words in a series together by leaving it off.
|This example is a bit silly as a defense of the O.C., IMO|
It can be amusing to share rants with our fellow writers, but it can also be demoralizing, especially for those of us who are still developing our writing chops. Just today, for instance, I learned that it's (sic) wrong to ever have someone climb down a ladder (claiming that "climb down" is a pleonasm and that pleonasms are always bad writing). I've also learned that it's bad writing to italicize a word for emphasis, because a good writer knows how to create the needed emphasis via context. I've also recently learned that metaphors or descriptions that aren't literally plausible are ludicrous. One fellow writer, for instance, said that he hates it when someone "rolls their eyes" at something (says it makes him think of eyeballs on the floor).
Occasionally, I find myself sputtering indignantly during exchanges on writing forums, as I sometimes use colloquial language in my writing (characters have even been known to sit down on occasion, which really is a pleonasm), because people say and think it that way in real life, so why can't characters in novels? And sure, I'm clever enough to think of ways to write around italicizing words I want to emphasize, but maybe I don't want to, because I'm trying to create a certain voice or tone (note how I just emphasized want in the manner so derided).
|New rule to me--all use of language must be literal.|
Another technique that is growing more popular is present-tense narratives. Some people categorically loathe the use of present tense in fiction and will not/can not read (or give a positive crit) to anything written in that tense. I read one such comment in a blog a while ago. Something along the lines of: "I don't see the point of it, and I've never seen a story in present that wouldn't work better in past. It's gimmicky, bad writing."
A few other things some writers/readers hate and denounce as bad writing that are not necessarily wrong, depending on context:
Italicized "direct" thoughts
Any use of passive voice to intentionally place the emphasis on the recipient of an action
Flashbacks to deliver backstory
Novels with multiple pov characters
Sex scenes in novels
Swearing in novels
Novels where the pov character's voice infiltrates the narrative
Contractions in narrativeNarrative with a more formal tone than the dialog
Details about characters' appearances
Tags that follow dialog and lead with said instead of the proper name ("Let's go," said Sam)
And so on. Readers and writers are human, of course, and we all have our likes and dislikes. But it's important to differentiate between something that's pushing our critical buttons because it's not being done well or feels out of place in the context of a given story, and something that's pushing our buttons because it's one of our personal pet peeves (or even something we were taught was incorrect when it isn't, like the above-mentioned use of the word "data" as a collective singular). Opinions stated as fact can have a devastating effect on brand new writers. Inexperienced writers lack the perspective to know whether the negative feedback is because it really is categorically wrong to do something, or if they're simply not doing it well enough, or whether it's simply the critiquer's pet peeve bludgeoning perfectly sound writing over the head.
And this got me to thinking. How much of the feedback we give others about their writing is not really intended to improve their writing, but to mold them into writing to our own preferences or conceits? It's a tough call to make sometimes, since our own perceptions of what is good writing is shaped by the things our own mentors have told us and by our own reading experiences. Writers tend to read more widely than most people do, but even so, when pleasure reading, we tend to gravitate towards books written in styles that lie within our comfort zones. This can affix us with literary blinders.
Neil Gaiman famously said, “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.”
I suppose this can be taken too far. If someone tells a novice writer that she's punctuating dialog incorrectly, or that he's got a problem with comma splicing, that critter may very well be right, and he or she may very well be able to tell the writer to fix it. But for issues that are more related to tone, style, and voice in writing, I think Gaiman is probably spot on in a high percentage of cases.
The take-home message for me as someone who critiques the work of other writers is to remember that I'm trying to help them find an approach that works for them in the context of their project. I should want to help them write like their best selves, not to write more like I do, or even to write more like my favorite authors. Criticism should be given with a dollop of humility, and it's a good idea to include the caveat, "This is only my opinion."
Likewise, criticism (unless it's clearly meant to be destructive or demoralizing) should be accepted graciously, even if you disagree with it. It should definitely be considered, at least, if multiple critters are offering the same feedback. But that doesn't mean you should change your approach to writing simply because someone, or even several someones, doesn't/don't like it.