BARBELITH underground
 

Subcultural engagement for the 21st Century...
Barbelith is a new kind of community (find out more)...
You can login or register.


How do you criticise people's writing?

 
 
All Acting Regiment
10:15 / 09.09.06
...and what the hell does "supercillious" mean, anyway?

So, I'd like to learn how to be a better critic of poetry and prose- I want to be able to give helpful advice, and I'm always willing to read people's drafts, yet I feel as though there's something I'm doing wrong.

Once upon a time I used to do the worst thing ever which is re-writing shit for people. As Jack F says, that's bollocks- no-one's asking for that. The only time I can think of that being remotely acceptable would be if someone was writing a specific poetic form- a sonnet, say- and they had a word in the "wrong" place ("wrong" being a fluid concept most of the time but slightly more relevant when strict forms are involved). Even this seems dodgy, though.

What I often find myself doing is reading a piece of prose and then responding with, "You know, there's a really good writer called Nabokov who..." or saying, "You know who's good at creating characters? Graham Greene...", which I would imagine is also the wrong thing to do. I mean, my subject can't be expected to just buzz off and read these books because I feel they have a vague "something" to learn from them, can they? Although frequently, and I don't like this, but the only thing I can think of to say is, "read more books", or indeed, "stop only reading Kerouac"...

What I've been doing recently is what my tutors have done for me, which is to highlight a section and say "Why did you choose to tell it like this?", or, "Can you tell me what this means?", "What made you decide to use this word?"- but I feel this is very oblique and perhaps unhelpful coming from me. My tutors seemed to be able to say those things in a way that was enlightening.

I also wonder what gives me the right to criticse- so far the only thing I've had published was when I was ten years old. Does one need to be an officially "good writer" before one criticises another's work? That sounds silly, but still...

How do you criticise?
 
 
Jack Fear
12:59 / 09.09.06
No, you don't have to be a good writer—or indeed, a writer at all—to be a reader-of-works-in-progress. You only have to be a reader.

Stop thinking of yourself as a "critic," first of all. Criticism is something that happens to finished works, wherein the critic analyzes and interprets the work, sometimes judging whether or not it succeeds or fails on its own terms. To use a kind of clunky software-based analogy, a critic is a sort of superuser to the writer's coder. The typical reader who's going to look at the finished story—the audience—are the users.

You? You're the beta-tester. Your job is to beat on the software—the story—observe how it works, note the responses—and see where it breaks. Your job is not to fix it; your only job is to point out where it's broken. The onlyt difference between you and the end-user/audience is that you get to tralk to the writer afterwards.

So read the work as an end-user. Take the thing as a finished object—a sculpture, not a lump of clay. Get it out of your head that you are in any way responsible for the creation or repair of this piece. Read as a reader.

Read it as you would read any other finished work, and pay attention to your own responses as you read: I'm bored here. I don't buy this. I'm not sure what "it" refers to in this sentence. I'm confused here. This sory is about_______________. Be honest. Not brutal: honest.

The only problem with this approach is that you've got to take a hard line with your writer afterwards; because the writer's job in dealing with a beta reader is difficuklt, too«s/he has to shut up, smile, and nod.

S/he may try to "explain" to you the parts of the story that you missed: cut hir off—the story must explain itself. After all, you're a stand-in for the audience, and the writer will not have the opportunity to explain the work to the audience after the fact.

S/he may ask you, "How do I fix this?" You must shrug and say, "Not my job."

You are a reader. You give your responses. You're not a co-writer. You're not an editor. Just a reader.

It may not sound like much, but in fact it's incredibly valuable.
 
 
All Acting Regiment
18:36 / 09.09.06
Aye, aye. Worlds of possibility are opening up...
 
 
Kiltartan Cross
23:32 / 09.09.06
S/he may try to "explain" to you the parts of the story that you missed: cut hir off—the story must explain itself. After all, you're a stand-in for the audience, and the writer will not have the opportunity to explain the work to the audience after the fact.

Hmm... there's an awful lot of books I haven't "got" - partly or even completely - the first time around. Sometimes that's been accident, sometimes by the author's design, and many times because in the interval between reading the book first and second I've learned something new. I wouldn't say that those books were necessarily failing to explain themself, but that I as a reader wasn't appreciating them as much as I later have. Ach, I guess all I mean to say is that if the reader doesn't understand straight away it's not always a failing on the part of the story itself.
 
 
All Acting Regiment
23:50 / 09.09.06
Maybe not, but if at least one person doesn't "get" it, and flags it, it'll make the author consider the part in question, and if not "wrong", maybe it still needs to be "considered". I certainly wouldn't take offence if someone said they "didn't get" something of mine (although I did when I was younger, yerk the memories).

If it was an intentional subtltey/ambiguity of the story, I'd ask them to read it again. If it was a reference to something, I might see about making it more informative...having read the aforementioned Greene, I've started to think that readability, "accesability" (though this is a problematic term) is a primary thing to aim for. Not the only thing, no, but still. Burgess: "Ullyses is, at heart, good fiction."
 
  
Add Your Reply