RSS

Arguing One’s Work

14 Jan

(repost from February 2008)

(No names are being given, in order to protect no one in particular.)

I’ve been on both sides of the argument when it comes to defending a piece of writing. This week, the argument came again, this time from a published writer whose submission to an online magazine was not bad but definitely not his best work. After I, a slush reader, offered my comments and suggested a rewrite, the author composed a long and well-thought e-mail response essentially stating that his work should remain as it is, that any changes to it would alter his message.

Although I can understand what he was attempting to do with his short story, his message did not come through in the final product; thus the request for a rewrite. Defending one’s work without considering the possibility that a change could improve it is (dare I say it?) arrogant. Very few of us in this world — regardless of our publishing statistics, adoring audiences, or innate talents — can produce work so near perfection that it cannot use a bit of polish to smooth the rough edges.

Several years ago, an older and wiser writer once told me that if I needed to explain what I wrote, I needed to rewrite it.

Excellent advice. If I expend too much prose trying to tell the reader something, maybe I’m not sure of what I’m saying. Maybe I’m over-explaining — and almost any explaining can be eliminated if the story is being told in clean, clear words. Maybe I’m skipping necessary information or, in an attempt to be literary or mysterious, I’m being too vague or am jerking the reader too quickly or awkwardly along the path toward story’s end.

I have a duty to the reader. Why should he follow my lead if I keep losing him in a coy attempt to be clever? Why should he lag behind when he can skip ahead of all the chunky, clunky prose and find a clearer path ahead? And why should he stick around for the end if getting there is too much work, or if he’s always being jerked off the path?

Recently, I had a small debate regarding a short story of mine published in December. In that case, I was the one presenting a defense of my work — not to an editor who asked for a rewrite, which had been requested and promptly given, but to a fellow writer who wasn’t all that impressed with the end result. That’s okay. Anyone who’s ever hired me to edit a romance novel knows how much it takes to impress me. I’ve seen my fill of cliched westerns, unmysterious mysteries, and boring thrillers. But that’s why I nudge, and sometimes prod, my fellow writers toward something better.

We can’t please everyone, nor can we please every taste. All we can do is present our best work and maintain enough humility to realize there are only a few perfect pieces of writing in this world — and ours are very likely not among them.

Advertisements
 
 

Tags: , , , , , , ,

2 responses to “Arguing One’s Work

  1. Melinda Friesen

    January 18, 2013 at 4:49 am

    Completely agree. I’ve learned to hate hearing my work is good. Don’t tell me that. I want to improve, I want to be better. It can always be better and unless I’m told where I need to improve, I never will.

     
  2. Keanan

    January 18, 2013 at 10:18 pm

    Yeah, that nebulous reply, “It’s good,” or “I like it,” while nice to hear at first, covers a multitude of things: “I didn’t really read it,” or “I don’t want to hurt your feelings,” or “I was bored,” and so on. I much prefer specific feedback, positive or negative, because that lets me know what works (what I can leave alone) and what needs help (where I need to concentrate my effort).

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: