briarwood | Thoughts of the role of the Beta

Something moljn posted recently got me thinking. Her post is here, but I'll quote a part of it:

Do you have that thing where, sometimes, you start reading a fanfiction story and within five minutes it's clear that it's really bad fanfic? I mean, train wreck levels of bad, especially in the way you can't. stop. reading. [snipped] And then you check the story notes, because it might be their first fic, and it isn't, and then they thank their beta reader? And you can't believe the story had a beta reader? (honestly, it's the part with the beta reader that disturbs me the most)

I don't know what fic inspired the post, but my immediate response was: Well...yeah. But how bad do you think it was before the beta got hold of it?

Almost every time I've had someone I didn't already know well beta one of my fics, that person has either confined herself to proof-reading or has replied with something along the lines of "This is really good!" That's not being a beta. A beta is not a proof-reader: sure, stories need proof reading but anyone can do that, including - shock - the author herself. And uncritical praise, while a pleasant ego-boost, isn't very helpful either.

Did the beta of that badfic fall into one of those categories? Could be.

On the other hand, it's not a beta's job to tell a writer "This sucks, you should just delete it."

I know that some of us would be happy to take that kind of criticism from a trusted beta. I know that most writers want a beta to be that kind of honest about their fic. But really, that's not a beta's job, nor her place.

If my instant reaction on reading a fic is this sucks, that's fine. I know where my back button is. But if I read it because I agreed to beta, then I need to go further than that. Because this sucks all too often means not that it's terrible, only that it's not to my taste.

Does it suck because of poor spelling and grammar? Bad punctuation? All of the above? Right - those I can fix. Copy, correct, then read the corrected version. Huh. Still sucks.

Now why does it suck? For me a big dealbreaker is consistency with canon. If I read a fic in which Jim Ellison can fly - you know, just like Superman - it darn well better be an AU, and to really work, it needs some kind of internal logic to explain why Jim can fly. Many readers who are not me won't give a rat's ass why he can fly, as long as the story in which he's flying is entertaining. So as a beta, I need to ask myself not is this story bad because I know Jim can't fly, but what is the author hoping to achieve by breaking with canon in this way? If necessary, I might want to ask the author that question.

Hey, friend, I read your fic. But before I send you my thoughts I want to ask you about one part of the story that I found confusing. It's where Jim flies over the building to chase the bad guys. It's just...well, in canon Jim can't do that, but up until that point I didn't find anything in the fic that told me it was going to be an AU. I'm wondering if I'm being really dense and I missed something. Could you clue me in?

Something like that. And maybe she'll write back that the cape and tights in the first paragraph should have given it away...or maybe she'll take on board that a little world-building would be a good idea and make her story better.

But maybe canon isn't the problem. Maybe it's characterisation. Suppose Cordelia comes home from a long day's shopping to find Angel standing over a bloody corpse. She screams and runs away, leaving her new clothes and shoeboxes in a heap behind her.

As a reader, I'm gonna quit - hit the back button - at that point. As a beta, I am not going to tell the writer Look, Cordy wouldn't do that, it's terrible characterisation, you suck! First I'm going to look at that moment in the context of the whole fic, see if I can figure out why the writer had Codelia behave so out of character. Maybe in this case it was so she would run smack into...oh, I don't know, let's say Gunn, who will save her like a macho man and carry her off for an afternoon of hot sex. So, okay, I can kinda see what the writer is thinking, even though she's gone about it badly.

Hey, friend, I read your fic. Really hot sex! *fans self* But I think the intro could use a little work. I'm not clear on what's going through Cordy's mind when she walks in on Angel. Does she believe he's turned evil? Has he turned evil? I don't think she'd be so quick to go off with Gunn if she thought her friend was in trouble. I mean, Cordy's selfish, sure, but she does care about Angel. Wouldn't she try to find out what's going on? I think the questions that scene brings up detract from the sex/romance part. I'd suggest maybe have her run into Gunn in a different way - perhaps he could save her from a mugger? Or even some random vamp - just not Angel.

See what I'm doing there?

Sometimes, there's the question you don't think to ask. I don't like to beta (or read) incomplete stories, because for me, the journey is about the desination. I can't critique something unless I know where it's going. But I've broken my "rule" a couple of times.

One time a friend asked me to look over an unfinished fic. The chapter I read described a character observing the scene of a murder and then acting to cover it up. I assumed this meant that character had committed the murder. My assumption seemed (to me) consistent with the canon character and, as I didn't have the full context of the story, it didn't occur to me I might be wrong. So many of my comments on the chapter came from that assumption...and were useless to the writer because, to her, the whole point was that someone else had done the deed.

Now, she took on board that she needed to change the first few paragraphs to make it clearer that X wasn't the killer. In that sense, I had done my job as beta. But had I known that from the beginning there were other questions I would have raised, starting with why was he covering it up? These questions aren't faults in the fic, they are part of the mystery the writer was creating. They are where my attention should have been, as a beta, but because I assumed too much at the beginning, those questions went right over my head.

It is not a beta's job to re-write a fic to her own satisfaction. It is a beta's job to understand what the writer is trying to achieve and help her to achieve it. Seriously, I can't stress that strongly enough. If you can't get behind a writer's vision, or you find the story utterly incomprehensible, it's okay to gently withdraw, apologise and say you're just not the right person to beta this particular work. But don't dismiss it as crap, even if it is. Even the worst of badfic has something in it worth nurturing.

Many years ago, I made a terrible mistake when a friend asked me to beta a fic. The story was written in a style that I found very difficult to read, but I believed this could be fixed easily. I was, shall we say, less than subtle in getting my point across. My friend never posted the story. My mistake was twofold; first I made no attempt to understand why she had chosen that particular style of writing and second, I was a bitch in telling her what I thought was wrong. In my defence, she had asked me to be honest. Still, there's honest and there's blunt. I was a bad beta to that particular friend and I'm damn lucky we are still friends.

No matter how bad a fic is, it is someone's vision, someone's creation. You know that scene in Firefly where Kaylee and Inara are talking about the cheap sculpture in a frontier store?

INARA: Does it seem every supply store on every border planet has the same five rag dolls and the same wood carvings of... What is this? A duck?

KAYLEE: That's a swan. And I like it.

INARA: You do?

KAYLEE: It looks like it was made with, you know... longing. Made by a person really longed to see a swan.

Isn't a lot of fanfic like that? Everyone has to start somewhere, and every writer, no matter how long she's been writing, still has more to learn about the craft. Isn't it better to understand that it's a swan, and show her how to make it a better swan, than to dismiss it as a duck...and a bad duck at that?

Seems to me that if we aren't willing to make that effort, we shouldn't be offering beta services in the first place.

Flat | Top-Level Comments Only

Perfect timing! I've been thinking about what a beta is these days since I read something last night that claimed to have a beta, yet suddenly switched tense halfway through the fic. It had been quite good up till then, quite hot, but that threw me and the standard overall went down to the extent I felt like the fic had been written by two different people!

I think we need some sort of beta education day *g*

I think we need some sort of beta education day *g*

There are loads of LJ communities dedicated to writing, and helping writers. I don't know of any to support the craft of beta reading. (Which isn't to say they don't exist, but they're certainly less prominent.)

It's really not easy to beta well...a beta how-to guide of some kind would be a good idea!

.
Good points -- and it takes practice for beta and author to work well together. Once I know I won't offend the author, I'll make more nit-picky suggestions, if they're needed. In the beginning, I might let a word slide because it's 'good enough'; later, I'll offer an alternative that I think would more clearly/elegantly express her intention.

That said -- just because the author thanks her beta, it doesn't mean that she took ALL of the beta's suggestions. If the author said, "Thanks for the suggestion, but canon doesn't really matter and this is the way I want to write him," but fixed a few spelling errors that the beta pointed out, she'll feel she should thank her beta, without realizing that her story looks only 'half-beta'd' to the reader.

Of course, different people have different strengths in the beta process, and some things can slip through even the most carefully-beta'd story. But I no longer have an automatic reaction of, "Boy, she needs a better beta!" because it takes two to tango.
.

and it takes practice for beta and author to work well together

Absolutely it does, and it takes time to find the right person to work with. Like any relationship, I guess.

just because the author thanks her beta, it doesn't mean that she took ALL of the beta's suggestions.

I never do :-) A lot, sure, but I'm not afraid to stick with my own judgement when I disagree with my beta. I think the other thing that happens, especially with so many ficathons that come with deadlines, a lot of people only get a fic beta-read once. At minimum, to do it right, you need to get a thorough beta, make all your changes, and then have it beta-read again...and then again as a final proof. I often find that making the first round of changes creates a whole new issue, especially with very long fics.

I my head I guess I tend to "blame" a beta if a story has the obvious mistakes: their/there, your/you're - stuff like that, but you're right. It's very much a two-way effort.

This was really well done. And it's true, you need to have the right person to beta with. You need to trust each other, but also not be overly sensitive about things.

Although I'm still trying to compute that image of Cordy...it's not working.

Although I'm still trying to compute that image of Cordy...it's not working.

*grins* Thankfully, it's not from a real fic...though I wouldn't be surprised if a scene like that exists somewhere. I was just trying to come up with something that no one would argue is out of character.

I was just trying to come up with something that no one would argue is out of character.

You did well! It's *completely* out of character! Cordy would NEVER abandon the fruits of a hard day at the mall! ;)

Seriously, this was an interesting read. I do a lot of beta-work, and even so I still found things I hadn't considered before.

Here via

metafandom and just want to thank you for this service to writers and betas! As a beta, I'm still feeling my way around how best to get the concrit out there; as a writer, I forget sometimes to be directive about what I want, particularly as I want to know what my beta thinks about things like characterization and canonicity. Excellent food for thought here!

I am also here via

metafandom. I found this a helpful and balanced look at beta-ing. I run a community for Lost fic writers called

thequillstation. I think the members there would enjoy reading your observations. Do you mind if I link your essay to the site?

Good advice, and I also quite liked your Firefly example.

From

metafandom.

There are some really great points here, but I can't help but disagree on sort of the over-all belief of what sort of role a beta should act. This is my personal taste in what I want from a beta, and how I go about betaing.

I don't agree that a beta's role is necessarily to nurture a writer's vision. If a writer requires that, I think it is something that should be done before the main editing or beta phase, wherein the writer sits down with either their beta or a close friend and has a dialogue about how to structure a story or how A might react when placed in situation B or what style best communicates and underlines a certain theme. That type of nurturing should take place before or while a writer is still in the first draft stage of a story.

When I send a story to be beta'd, I've already made those choices on stucture, theme, characterization, etc. for better or for worse. I now want a beta to tell me if they work. Am I effectively communicating what I want to communicate to the reader? Does this structure really compliment this story or does it need some tweaking? Are my word choices as strong as they need to be, and is my grammar readable? Is it believable that this character responds this way to this event? If the answers are no, I want a beta that will tell me so.

There is much to be said for being polite as a beta, and it's a hindrance if a beta only dismisses a story right off the bat, either in positive terms ("This is great!") or in negative terms ("This sucks!") without explaining why. But I don't think politeness should interfere with a beta telling the writer whether things do or do not work in a story.

To use your metaphor -- if I've made something that is meant to be a swan, but it looks like a duck, and a bad duck at that, I want a beta to tell me "You've written a duck" rather than "I can see that you were trying to write a swan". I was trying to write a swan but that's almost immaterial now if no one can tell it was meant to be a swan. At least being told that it looks like a duck, I can start the dialogue with my beta of how to transform this duck into a swan.

Obviously I need a beta for my grammar even in comments. *headdesk*

metafandom. You make good points. I've been thinking about this subject too. Over the past few months I have beta'd for *counts* seven different people, four experienced writers whose work I love, two new writers and one for whom English was not her first language.
My main problem is that I am naturally blunt and, when there is a deadline that the writer has to meet, I don't have time to 'smooth the edges' of some of my comments, as I know I should (to use my best friend's expression, who is also on the receiving end, all to often).
As a result, I have now produced a statement of introduction, to send to writers who ask me to beta. It may not be enough, but at least I can feel that I have warned them that diplomacy is not my strongest virtue.

Thoughts of the role of the Beta

no subject

no subject

no subject

no subject

no subject

no subject

via metafandom

no subject

no subject

Here from metafandom

no subject

no subject