Notes from an editor

A newsroom colleague asked me once why I would want to run a newspaper. “To make it better,” I said. He nodded respectfully.

I’m not much interested in running newspapers these days (though I do still write for them on occasion), but I think my answer still applies to editing in general. Why be an editor? To make something better.

I’ve been editing professionally for a long time—copy editing, proofreading, and now moving into developmental editing. I’ve edited breaking news on deadline, fiction and nonfiction manuscripts, movie reviews, and obituaries. I get equally annoyed by typos in books, on restaurant menus, on shoebox packaging, and in TV news crawls. (Every single news channel has typos. This is a bipartisan aggravation.) I analyze while reading. It’s a habit.

I’ve worked with a lot of writers, and in my experience, these are the elements crucial to the success of the writer-editor relationship.

Trust. Though that trust can be unnerving. Frequently I’d tell a reporter I’d tweaked parts of their article and offer to show them the changes, and they’d just shrug and say, “I trust you.” Then I’d neurotically wonder whether I should make them read the tweaks anyway.

They trusted me because they knew I wanted to help them produce their best work. They knew I wasn’t going to change things that didn’t need changing or throw in words they would never use (every writer has a “stable” of words they use most often; if you add words that don’t blend with the rest because they’re too flowery or esoteric, you’ve muddied the voice). They knew I was keeping their viewpoint in mind. And they knew I was neurotic enough to make them read the changes.

Understanding. It’s not just doing your job well—it’s understanding how the other person does their job. When editing a newspaper or magazine article, I knew the reporter had spent hours, sometimes days, collecting enough research to put an article together, and even more hours figuring out the puzzle of arranging the article. When I’ve beta read or critiqued fiction, I’ve kept in mind how much work went into planning out the elements of plot, character, voice, and theme. I respect what it took for the writer to complete their work, and I respect that changing that work might not be easy.

At the same time, the best writers I’ve worked with understood that it took time for me to do my job and that I couldn’t just skim something, run spell check, and call it done.

Knowledge. If I’m not familiar with the writer’s subject matter, I’ll take the time to get familiar, because I think research is fun. (Yes, I’m nerdy. And?) I know what it feels like when the person editing or critiquing your work hasn’t done their homework. During a writers conference held at my college, the critiquer admitted that he wasn’t familiar with science fiction, and proceeded to mumble his way through some vague commentary on my short story. Was my story any good? Probably not. But the critiquer didn’t offer any suggestions for making it better, and I felt out of place for even asking.

I don’t think there’s any shame in looking up something you don’t know, whether it’s about a specific subject or about the conventions of a particular genre. If I don’t have that knowledge, I can’t help the writer.

Ultimately, the writer needs to remember that the editor is looking out for their best interests, and the editor needs to remember the writer is the one whose name is on the story. Egos need to stay out of the process. If the writer and editor work together, they will make the work better.

In research mode

I like research. Geeky to say but true. I like having perpetually new reasons to learn more about the world around me. Sometimes that means a trip to the library, and sometimes it means a road trip.

For my day job recently, I wrote a magazine article about historic buildings saved from demolition when they were repurposed as performance venues — good for historic preservation and the local arts scene. (You can read it here.) My research was a combination of interviews and in-person visits, so I could get a sense of what these sites were like. In other words, multiple road trips to parts of the state I don’t often visit. Two things about New Jersey you probably didn’t know: It has a number of centuries-old buildings (one of the original 13 colonies, after all), and most of the state is much prettier than whatever you saw while stuck in traffic on the Turnpike or while hustling through Newark Airport. Lovely scenery plus learning about historic architecture equals a win.

Meanwhile, I am doing research for a novel-in-progress involving abandoned amusement parks and rereadings of “Beowulf.” It will all make sense in the final draft (theoretically), though reading “Beowulf” is a pleasure in its own right for the beautiful language.

Inevitably, I overdo it; I have more knowledge than I could possibly need for whatever I’m working on. But that’s a good thing. Better to thoroughly know your subject than to patchwork-guess your way through. You never know when that newfound knowledge will be useful in a different setting.

I don’t know what I’ll be researching next, but I can’t wait to find out.

Hurry up and wait

So here is where my day job conflicts with my fiction writing.

My day job currently consists of writing news and features articles, and editing pieces for various companies. I’ve done the newbie-reporter gig of covering municipal meetings and county fairs, and logged a number of years as a newspaper copy editor. The copydesk edits all articles in the paper, writes the headlines, fine-tunes (or fully creates) the page layout and clears everything to go to press. What does all this have in common? It needs to be done right now. Or ten minutes ago, if you can swing it. Deadline waits for no one. Missing deadline and making the paper late invites capital punishment. Think I’m kidding? Here is the original definition of the word “deadline.”

When I started seriously writing fiction and researching the kidlit industry, imagine my surprise to discover right now is not how it works. Agents and editors don’t want you to rush. They want you to put the story down, give it time, then pick it back up with new eyes so you can revise it properly; if you send them a revision too quickly, they’re liable to decide you took too little time on it and reject it. I was at first baffled by this, then slightly tearing-my-hair-out about it. “But don’t you want it to be done? Isn’t it done now? How long should I be taking to make it done? Arrrrrrgggghhhhhhh.”

It’s taken some practice. But I’ve been getting better at allowing time for breathing room, and letting the story be done when it’s ready to be done. So, don’t make my newbie mistake. Put it down. Give it time. Breathe.

(But if you’ve got a firm deadline, please, don’t blow it.)