Showing posts with label writing conventions. Show all posts
Showing posts with label writing conventions. Show all posts

Thursday, August 30, 2012

If It's Broke

At Children's Book Insider, Laura Backes offers common problems in stories for children, which are common problems in all narrative writing (thin plot, bad plot, flat characters, and bland, obnoxious, or otherwise unappealing voice), and concludes with a reminder about the importance of a solid command of mechanics:
When submitting to an editor, grammatical errors can distract from an otherwise strong book. When self-publishing, they're the kiss of death. If you know you have problems with punctuation, spelling, subject/verb agreement, formatting dialogue, etc., hire a good copy editor to clean up your manuscript. There are people out there who live to fix these problems. Use them.
If these be the common problems, what are the solutions? Backes says exactly what I say to writers who ask me how to improve their writing: Read. Read a lot.

Find writers you like and read everything they wrote. If you skipped out on the great books in high school and college, consider taking another crack at them: Great Expectations, Pride and Prejudice, Anna Karenina--there are lists all over the place if you need ideas on what to read:
  • 100 Novels everyone should read here.
  • Information Is Beautiful on the books everyone must read here.
The reason people like them is that they are great stories beautifully written. A lot of them. I couldn't stand Herzog, but it always ends up on someone's list. In matters of taste there is no argument.

By the way, if anyone is ever looking for an editor, I know a few whom I highly recommend, whose work is so good and evidence of such knowledge and skill that I am dazzled. It may surprise you that one might be dazzled by the skillful wielding of grammar and punctuation, but thorough competence always does dazzle.

Words for the day:
No man but a blockhead ever wrote except for money.
Samuel Johnson hadn't seen the Occupational Outlook Handbook when he said that.


Saturday, August 18, 2012

What the World Needs Now

It may be unnecessary to say that in talking about what's wrong, I don't mean to pick on anybody in particular. Even if it is one person making specific mistakes, I tend to see this as a systemic ill, as previously discussed, rather than an opportunity to dogpile on an unwitting offender.

A systemic ill that is particularly pernicious in the test publishing industry. How can we expect kids to do well on tests when the tests themselves are riddled with error?

The safeguards are so simple:
1. provide adequate training (again, as previously discussed)
2. follow some kind of standard process for detecting and repairing error
3. use the information from #2 to supplement #1

These safeguards cost time and money, which explains why so many companies have gradually let them fall by the wayside. 

Training takes time and attention. I can't believe how fortunate I was to have received the training I did. In my first year as an associate editor, I probably had more training opportunities than editors now receive in a decade. It was a different era. The Great Big Huge Test Publishing Company at which I worked had an army of style editors, proofreaders, and QA personnel.

Over the last dozen years, I've seen companies completely dismantle their style editing departments and outsource the work to freelance editors. Now style editors (copy editors) are held in such low regard that if any Bright Young Thing with a talent for grammar and language conventions tells me she'd like to give this work a try, I steer her away from style editing and into content.  I hate doing it. I myself hold style editors in high esteem, maybe because often their job seems to be to keep me from making a fool of myself. What the world needs now--no disrespect intended to Dionne Warwick and Burt Bacharach--is more style editing.

Many companies have also dismantled their content development departments.

So there's no real continuity for item writers and content editors. They work on a project for one company and then skip to a project for another. The content development people who remain at the companies are overwhelmed and certainly don't have the time to provide training to freelancers; editors accept or reject items, which means they're likely to fix mistakes themselves, and so the item writer never hears of his mistakes and is free to repeat those mistakes forever in a state of unfortunate ignorant complacence.

Right now, I'm thinking of all this in terms of language conventions items, because I was reviewing a set this morning, but I'm sure this applies to all domains and content areas.

Right now, I offer some specific observations about language items:
1. When language items accompany an editing passage that contains embedded error, the content of each item must be mutually exclusive. A sentence from the passage should contain only one error, and should be used only for one item in a set.
2. "Syntax" has to do with grammatical rules; "diction" has to do with the writer's choice of words.
3. An item should clearly target only one type of error, and should not mix types of errors. For example, a punctuation item shouldn't include distractors that contain errors in verb tense.

More previously discussed here.

As an aside, it's interesting how you can learn a lot about a person by reviewing his or her work, and how this body of knowledge grows over time. It's like how my mechanic told me that he knows more about his customers from the condition of their cars than he does from talking with them. He can tell who drives erratically, who slams on the brakes, who grinds the gears, and he can tell who doesn't. Everything is everything. You can develop a similar personality profile simply by reviewing a writer's work.

I can't tell you how many times I've finished working on a manuscript, items or reading passage, don't make no difference, and felt a deep and tender affection for the writer because his or her work demonstrated care, attention, and conscientiousness. 

UPDATE: Forgot to mention. I started writing about all this because I saw this book mentioned in the Common Core Standards and immediately ordered it. 

Thursday, August 16, 2012

Jobs, Money, and Love for All

Good grammar and spelling skills make your life better.

From Education Week, a teacher's blog post about an employer who screens job candidates to weed out those with poor English grammar skills:

In a fiery post for the Harvard Business Review, Wiens says he flat out won't hire people who are careless with grammar. And to ensure that no offenders slip through, both of his companies—Wiens is also the founder of the documentation-software maker Dozuki—have instituted mandatory grammar tests as part of the hiring process.
Before I read the source post by Kyle Wiens for Harvard Business Review, I had mixed feelings. Is this really necessary for candidates who aren't writers? I know so many smart, capable people who use--oh, let's call it "nonstandard grammar." They're not writers, and so I switch off the inner critic before I read their email messages.

But Wiens makes a compelling argument:
Grammar signifies more than just a person's ability to remember high school English. I've found that people who make fewer mistakes on a grammar test also make fewer mistakes when they are doing something completely unrelated to writing — like stocking shelves or labeling parts. 
In the same vein, programmers who pay attention to how they construct written language also tend to pay a lot more attention to how they code. You see, at its core, code is prose. Great programmers are more than just code monkeys; according to Stanford programming legend Donald Knuth they are "essayists who work with traditional aesthetic and literary forms." The point: programming should be easily understood by real human beings — not just computers. 
And just like good writing and good grammar, when it comes to programming, the devil's in the details. In fact, when it comes to my whole business, details are everything. 
He's right that details matter.

You can even put a price on details. According to a 2004 article in The New York Times, one spelling mistake can cost as much as $198:
Mr. Green once bought a box of gers for $2. They were gears for pocket watches, which he cleaned up and put back on the auction block with the right spelling. They sold for $200. 
An article published by BBC News in 2011 calculates the cumulative costs:
An online entrepreneur says that poor spelling is costing the UK millions of pounds in lost revenue for Internet businesses.
Wayne State University assistant professor Fred Vultee, who conducted a study sponsored by the American Copy Editors' Society, found that not only can readers distinguish edited from unedited text, but they notice and are troubled by errors (more here). Said Vultee, "Editing makes a difference. It's across the board, it's not imaginary, and it's reasonably big."

And if that weren't enough, errors in spelling and grammar can also inhibit romance: "In a survey of more than 5,000 Match.com members asking about the most common profile mistakes, 51% complained about profiles with poor spelling or grammar...."

Over the last almost twenty years, I've worked with writers whose English language skills range from impeccable to not. When I say "not," I don't mean to pick on anyone who makes an occasional typo or some other minor mistake. It's very difficult to proof one's own work; the brain insists on making the text appear as you know it should appear. I use "not" for those whose work displays not just a repeated pattern of error, but sometimes repeated patterns of different types of errors, even after those same types of errors have been pointed out to the writer previously.

Is it prejudice to expect that people whose trade is writing should have strong language skills? Maybe. For me, it's work avoidance; writers who make lots of mistakes cause me lots of extra work. Which means I can verify that mistakes have a cost, because if I need writers, my first calls are to the ones whose writing causes me the least work in terms of content and style.

I don't fault anyone for not knowing something; we all of us stumble on our ignorance sometimes. And yet, it works against us to cling to that ignorance once we become aware of it.

Toward the goal of jobs, money, and love for all, I offer the following resources:
Grammar & Style: Grammar Guides, Style Guides, APA, MLA--LibrarySpot.com
Grammar.net
HyperGrammar at the University of Ottawa
On Writing Well by William Zinsser
Pam Nelson: Grammar Guide
The Elements of Style, Fourth Edition by William Strunk, E.B. White, and Roger Angell
The Purdue Online Writing Lab
Top Ten Resources on Spelling and Word Study