GUMmyStuff: What is it?

I use the hashtag #GUMmyStuff on Twitter at least once a day. I’ve explained it there several times, but I’ve never done a post here. Time to fix that.

Grammar. Usage. Mechanics (which includes spelling and punctuation). Take the first letters of each, and you get “GUM.” Things about or containing gum are gummy, so: Posts or tweets about grammar, usage, or mechanics are gummy. Gummy stuff. #GUMmyStuff.

It makes more sense to me to use this than to have separate tags for grammar and usage and mechanics (splitting that into spelling and punctuation), because, let’s be frank—#GUMmyStuff is eye-catching. It makes people stop. It’s oddball (like me). It’s also accurate, because those tweets and posts are about those things, often in combination.

I’ve initiated hashtags before. The one that’s taken off is #SpellcheckCannotSaveYou, which some folks insist on writing with “WillNot” instead. Will has nothing to do with the situation. Spellcheck is incapable, unable to save your sorry butt from using the wrong word spelled correctly. It’s not that it won’t. It can’t.

That’s separate from GUMmyStuff, because it’s specific to one situation. GUMmyStuff is a catchall category into which I toss many things: grammatical voice, verb tense, subject/verb agreement, syntax issues, and more.

It’s stuff. GUMmyStuff.

Chicago Manual of Style comes to PerfectIt 5

I honestly didn’t see how PerfectIt 4 could be improved upon. I’ve been using it since it came out. And I used PerfectIt 3 before that. I love, love, love this program.

Believe me when I say that Daniel Heuman and the team at Intelligent Editing have found a way to improve upon it.

When you get PerfectIt 5, you’re not only getting the kind of proofreading/copy editing support you’ve become accustomed to in the past, but if you have a subscription to CMOS online, then you’re also getting real-time support via the site (chicagomanualofstyle.org). When PerfectIt5 highlights stylistic problem areas, it also provides you with a live link to CMOS guidance.

If it’s something you already know and are comfortable with, something you’re sure about, of course you can ignore it and keep on trucking. However, if it’s something that makes you wonder whether you know what you thought you knew (and it happens to all of us!), just click on the link and you’ll see the “chapter and verse” about the issue. For example: “The term half brother is usually open. See more from CMOS 7.89”. Clicking the “see more” line brings up the relevant text directly from the CMOS site, with the numerals in bright red bold type.

For editors who are still learning the Chicago style, I’ll say this is nigh unto invaluable. No more wondering whether you’ve gotten it right. No more second-guessing yourself. And best of all, you’ll find you’re looking up fewer issues. Even for those of us used to using the online version, this is an improvement. The information will come up when we need it, at the precise point in our document where we need it. NB: This addition does not include the entirety of the CMOS database. There will still be times you’ll need to go to the book or the online version on your own.

The usual caveats apply as they do with any “checker” program. It’s better to be cautious and check each instance individually than cavalierly “fix all.” (Only when I can see “all” right there in one place do I ever even consider doing that.)

I say all of this as an editor who works only with fiction. I don’t have to think about heading hierarchies, tables, figures, footnotes, bibliography entries, and so on. If you do, I feel safe saying you will find this a godsend. The guidance will pop up immediately, right on your screen. No hunting through a print copy, no searching the website. It’s right there, and it will expand at the click of your mouse.

Congratulations, Daniel and team! You found a way to improve something I thought was already perfect.

[Disclaimer: I received a free one-year extension to my subscription for this review.]

Grammar Is Overrated: The Director’s Cut

But seeing as the director is an editor, this won’t be so much an expanded version of the article I wrote for the Winter issue of “Tracking Changes” (the ACES house organ) as it will be a more finely tuned version. I think. Maybe. Let’s find out.

When I say grammar is overrated, I’m not saying “throw it out.” I’m not saying we don’t need it. We absolutely do, or literally couldn’t string two words together and have them make any sense at all—okay, that’s more properly syntax, but let’s not split hairs here. As editors and writers (the groups making up the bulk of my followers here and on Twitter), we definitely need grammar and syntax.

The thing is: We already know most of what we need to do our jobs. My point in that article was that it isn’t a requirement to take courses in linguistics and “deep grammar” and the like in order to be an editor. Those of us drawn to that profession already possess the basics we need. We know about nouns, verbs, adjectives, adverbs, and such (the parts of speech, as they’re called). We know about parts of a sentence (subject, predicate, predicate nominative/adjective, adverbial phrase/clause, direct/indirect object, blah blah blah). This is the stuff we were taught—perhaps not very well, admittedly—in elementary, middle, and high school. (I’m old. I got it in every grade, from first through twelfth.) And, to be honest, knowing this level of grammar/syntax is enough to be a good editor, especially when you’ve got that affinity for words. When you’re driven to find out how they function, how they work. That drive might lead you to taking classes to deepen your understanding, and that’s great! But it’s not a requirement for being an editor.

We have to be able to communicate to our clients about the problems we find in their work, in words that they’ll comprehend. Now, I work with indie authors. Some of them know grammar, some don’t. I can’t always tell a client “There’s a problem with this subordinate clause.” Their eyes will glaze over. What I can say, though, is something like “This highlighted bit here isn’t doing what you think it is.” And then I can suggest an alternative, and with any luck at all they’ll see the difference and either use my suggestion or come up with their own (Option C, as one client calls it).

I can, however, be fairly confident of telling a client “We need to work on your pronoun usage” and having them understand. Too many proper nouns and too few pronouns in a given sentence or clause is a common problem. The concept of referents (the words to which the pronouns refer) isn’t difficult, so when I say there isn’t a clear one, most of my clients get it. I also tend to leave fairly detailed comments; it’s the former teacher in me.

The point is this: We have to be able to talk to clients about their writing, using terminology they will understand, so they can improve. Throwing around terms like “fronted adverbial” (which sounds quite intimidating, until you realize it’s an adverb of some kind that comes first in the sentence) doesn’t do a lot of good. And let’s just not bother with things like “conditional past subjunctive in the third.” Only the true grammar nerds (or geeks if you prefer) will get that one. Learning the esoteric aspects of grammar and syntax is a fabulous thing, a wonderful indulgence. Just remember: If you can’t explain it to your client in terms they will understand, it isn’t of much use to them.

There are editors, and then …

… there are editors.

My initial idea for this post was quite different from what it is actually about. You see, I was surfing the internet (what else is there to do when self-isolating, aside from bingeing* shows on Netflix or some other streaming platform?) when I saw an editor say something that stopped me dead in my tracks. I won’t quote it here; I not only do not have permission, but I would not ask for it. It’s not a very flattering reason to be quoted. It was a gaffe I almost immediately attributed to the difference between a copy editor and a developmental one. The copy editor needs a grounding in grammar. The developmental one does not. In fact, it can be a hindrance; it’s much easier to do the deep reading for developmental work without the distractions of misplaced modifiers and errant commas.

I had thought I’d write about the problem in the statement, which meant a lot of deep grammar stuff that even some long-time copy editors don’t necessarily know. It’s one thing to know that something is wrong; it’s another to know precisely why, and to be able to explain why in clear, concise, and above all correct terms.

This was … not correct.

And unless the writer knows grammar, they won’t know it’s not correct.

And for me, that’s a problem.

But backing up a step: The gist of the comment was right. The wrong thing was being emphasized. The details were wrong, though. And that bothered me. It still bothers me, hours later. But I realized, as I sat being bothered, that the bigger issue is that “editing” is a very large tent, encompassing several styles, and while there is often some overlap in skills, there isn’t necessarily any. It’s a happy coincidence when there is, in my experience.

And it’s far from my place to call someone out on having spoken erroneously when they’re essentially talking to a specific person, as it was in this case, rather than to a group at large. Not my business, honestly.

I know some of you must be wondering what the error was that got under my skin. Pretty basic stuff, really, about the grammatical subject of a sentence. Except there was a predicate complement involving a subordinating preposition followed by a rather intricate clause, and that got mixed up with the grammatical subject, and it was a right mess.

The developmental editor had a good point, but they made it with utterly incorrect information. That’s what bothered me. The sentence in question needed rewriting to tighten the focus, yes. But the prepositional object was not the grammatical subject of the sentence. Nope, sorry. (And it didn’t help that the prepositions were understood/implied rather than present, but if you diagrammed the sentence you’d know they were there. English grammar, man, it’ll get you in the ass every time.)

Can the recipient of the suggestion use the information they got and improve their writing? Probably. Especially if they go to the editor and ask for clarification. Even one who doesn’t know all the grammatical terms can still explain a problem like this one in ways that a writer can take to heart and use in a later draft. Know that I’m saying that as both a copy editor who knows her grammar and as a developmental editor who learned that DEs don’t need to focus on the technical issues, but rather on the Big Picture or “30,000 feet” problems. “Put the focus on [this word] instead of [that word].” That was the heart of the statement. And it was appropriate for the situation.

But the subject wasn’t the object of the preposition.

 

*”Bingeing” is the preferred spelling given by Merriam-Webster. The E differentiates it from “binging,” as in “The computer was binging for at least 15 minutes while her cousin tried to get her attention.”

Yep, it breaks the “rule” for dropping the terminal E when adding -ing to a verb. Too fucking bad.

I’m still here.

I know, it’s been nearly three months since I last posted here. Life keeps happening.

My elderly father’s been vacillating between “aging in place” and moving to an assisted living facility. Granted, he’s 92; he can no longer drive after dark; his closest friends are moving sometime in the next year, back to California; his health isn’t awful, but he’s in slow decline, more physically than mentally.

Other family things have been going on, which I won’t discuss. Just know that, as I said up there, “life keeps happening.”

I’m still editing, albeit less than before merely by dint of other people’s lives happening to them. Nearly every slot I booked has slipped by a couple of months or more, which means I can book into the now-empty slots, but money I had roughly planned for isn’t coming for a couple of months or more. (See “slipped by.”)

However, I’m still here. I’m still reading and editing and tweeting. I’m still that opinionated one who says what she thinks. I’m not going anywhere, at least not that I’m aware of.

(This is mostly a test of the new editor at WordPress, but it’s also a chance to touch base with those of you who have subbed to my blog. I haven’t forgotten you. I promise.)

On peeververein and the burnishing of credentials

This post has been banging around in my head for a few days. I’m going to try again to get it out of my gray matter and into pixel form so I can stop thinking about it.

Perhaps I’m a bad editor, but I refuse to read the local papers’ columns by “grammar experts.” (When I say “local,” I mean local to anywhere; the tiny burg I live in has little more than a broadsheet filled with want ads, for-sale/giveaway ads, and minutes of the local school board and PTO meetings. However, the power of the internet lets me access papers from all around the country. But I digress.) Why don’t I read them? Continue reading “On peeververein and the burnishing of credentials”