SomeGuy's Workshop, Session Eleven

There are no really mechanical-like things that seem to be an issue these current days. So I'm just gonna writing-blog today. Again.

Are You Really Trying To Help Me?

I don't want to be the jerk who rehashes the "how to give criticism/critiques/comments" thing. I know, "be constructive, don't be mean, yada yada yada." This is a slightly different angle, though.

The truth hurts and it always has. They always say that all aspiring writers need to be able to grow a thick skin, because all their lives they'll be taking criticism and feedback. I'm sure most of us have learned that at some point by now, huh? So we learn to not take too many things personally, to see ways to improve from past mistakes, and - above all - to keep writing. Totally easy in theory, but I can also say I've seen many a creative project roadblocked by an artist just not being inspired to try anymore.

Is their skin still too thin? Possibly. Does that mean we have free reign to be jackasses to our peers who are still thickening theirs? I should certainly hope not.

If you're good with your critiques, you know what works and what doesn't for something, that's great and all writers should be happy to be able to receive that kind of help. But when it all comes out, well... you gotta ask yourself: are you trying to help this person improve writing skills, or are you trying to tell said-person how much you disliked the work?

This isn't even an issue of being courteous or polite. Straight up, it's just a matter of what's effective in making people listen. Why would anyone care about some random stranger that rips apart a story? You don't know anything about them, they don't know anything about you: why should they care what you think? Why would they care?

Compelling writing works both ways...

Who Do You Think You're Talking To?

This site's a good example for this next bit. When you write for this site - or in particular for anyone - you're always thinking about your target audience at least a little. As you write, you're also balancing that with your own style and ideas about writing so that you're still true to yourself. For a lot of the older folks around here sometimes the worry comes up that you want to show everyone the best of you and not have to "dumb it down too much".

Well, when you're critiquing someone, the above problem is a 100% non-issue. When you're commenting on a work, you only have to worry about one person understanding you: the writer of said-work. Even if the work isn't the writer's best, it's still something he feels is good enough to warrant showing off. That alone should be enough of a hint to give you a general idea of what kind of writer, how much experience, and so on. As such, it should give a hint as to what kind of an approach you might want to consider taking with said-person.

If you're talking to 15 year old fanfic writers who don't use words with more than four syllables, don't expect to change their writing too much when you tell them how they missed a good chance for a post-modern social statement about 21st century republics. Extreme example, yes, but keep in mind who you're talking to; if they don't know what the hell you're talking about, why will they listen?

In a similar vein, if you know someone's written a lot of work on the site, more often than not demonstrates an ability to comprehend and think critically, perhaps this person might be a little more open to less-flowery talk that gets straight to the point; they'll probably appreciate the absence of minced words just as much as you, perhaps. Again, it's not an issue of politeness. In this case, it's just respect.

All It Takes Is One Word...:

I'm going to give a few example statements, identical in meaning but different in approach:

You should use more detail in describing your characters' faces.
I would have liked more detail describing your characters' faces.
If I wrote this, I would have added more detail describing your characters' faces.

Okay, so you don't think the writer describes his characters' faces well enough. Fair point. So which of the above do you think would make them go "okay, alright, I'll think about detailing my faces more next time"?

I can't say for sure, but I can sure as hell say that that last one isn't gonna do it nearly as well as the others.

This is pretty much one of the most offensive, most pretentious things you can say to a writer. If you had written it? Yeah, you didn't write it. That's the point, it's not your story. Obviously if you had written the story you would have done things your way; you don't need to take that extra step and say it outright, because people lose interest really fast after that.

It's funny, isn't it? The sentences all make the exact same point, and yet one just adds four extra little words and suddenly the whole tone seems far less inviting. Such is language. Again, the question: are you trying to help someone along or did you just want to clearly state why you didn't like their work?

Not A Job Interview, But...:

There's a saying (and possibly even studies that say) that an employer will know if he'll hire someone within the first ten seconds of a job interview. Ten seconds. That's it.

It's not just interviews, either. A new website will generally have about ten seconds to keep your interest before you hit "back"; you'll generally get a sense about whether you'll like new people within the first ten seconds of meeting them. The same is true of a review/comment.

The whole idea of "compliment sandwiches" (say something you liked, something you disliked, something you liked again) does seem a little cheesy and maybe even a little forced. But it's another one of those things, the whole "attracting more flies with honey than vinegar" deal.

Does it feel contrived? Probably. Is it going to hurt your chances of convincing someone you're worth listening to? Unlikely. People like to hear praise, that's a fact. And if you do have nice things to say about their stuff, then why not get that out of the way before getting down to business? Not only does this give you a hook into someone's interest, but it also has the added benefit of "saving the best for last".

Even if it's not the last last thing you say.

So Maybe You Do Just Want To Say What You Didn't Like?

Here's where this week's workshop gets messed up...

So say you really aren't interested in helping a person with constructive criticism. Maybe you do just want to tell them that they've written something they shouldn't have written.

...hey, sometimes it comes up. I know I've done it several times to people already.

There's really no safe way to do this one. If you absolutely feel that a writer has just gone and done something absolutely horrible, then it's fair to say why. All I can say is that as long as your words are sincere and un-exaggerated, people will listen to that. Use the words that need to be used. Don't describe things as "the worst" or "stupid". Be plain, be thorough. We all know what internet hyperbole looks like; people see it, they tune out. Avoid it, and they'll read a little closer.

Language Is A Tricky, Tricky Thing...:

I write about rhetoric a lot when I'm not writing about writing mechanics. But I've always said that any jackass can try to be clever by using sarcastic double-talk. But that kind of aggressive speech only breaks a person down. To be able to build a person up, though, now that takes talent.

Obviously this isn't an exhaustive post that covers everything - and seriously, that's not gonna happen. Hopefully what this can do is just open up some ideas. Remember, it's not a question of being polite or courteous; it's a question of using the most effective means to get things done. This is true for all forms of speech, both written and spoken, and is the question you should always ask yourself before you say things...

What are you trying to do with your words?

End