Posted in Methods, Resources, Writing

Beta Reading and a Thesaurus 

I didn’t spend a lot of time writing today. In fact, I didn’t do much writing. What I did end up doing was beta reading through serveral pages of acquaintances’ stories. This was mostly due to the fact that I was avoiding my computer because I used it a lot during November and I, sort of, neglected my reading responsibilities. Either way, I got through a lot of pages today.

I could have read through more but these certain pages needed many comments and suggestions on setting, sentence structure, and missing words. It’s not like I mind the extra work. I’ve told them to let me know if they don’t want me to stop picking out bad grammar. So far, they haven’t said to stop. This also helps me in a way because reading other people’s work not only gives you an opportunity to come in contact with a different writing style, you can avoid some mistakes that you may see in someone’s work and vice versa. I believe that one can always learn something from reading other’s works. 

There was one story that I read today that appeared to be vomitted on by a thesaurus. This is possibly the harshest thing that I have said. I mean it in the nicestest of ways too. It wasn’t as bad as I make it sound but there were a few words that didn’t belong there. I couldn’t even figure out what the original word was meant to be. This isn’t a warning about uaing a thesaurus but more like something to keep mind. 

Usually, I used a thesaurus so that my writing and certain words become repetitive. For example:

It’s not like this person had every word changed. It just so happened to be in one paragraphed and I had trouble figuring out what they were  to describe. You can say that this was my lesson for today.

Posted in Methods, Writing

Beta Reading

Recently, I was asked by a friend, let’s call him J, to read his story for him as a Beta reader. I’ve done beta reading before – changed some minor grammar issues – commented so, I like to say that I know what I’m doing. Plus the last 60 or so hours of college was all about reading, editing, and commenting on classmates’ work. I have experience under my belt.

There are a few things I have to keep in mind when I read over someone else’s work.

1. I read through it first.

I like to take it all in before I start to analyze a story. Mostly because if I’m confused on something and I comment on it but later the information is there then, I made a mistake. I also think its nice to just read a story and think about it afterwards.

2. Use a red pen.

Normally when I print a story out then, I tend to use a red pen. There’s nothing special about a red pen, in essence, but it helps me get into the mindset of editor.y job is to look for grammacial errors, minor mispelled words, ect.

3. Be honest but don’t be mean.

There’s a fine line between disliking something and being mean. At least that’s my opinion. In my comments, I’m honest. If I think something is cliche, I say it. However, I also include suggestions on how to fix or change whatever bothers me or I think needs to be changed.

4. With a grain of salt

I always tell the author  to take my advice with a grain of salt. Ultimately, it is up to him/her to decide what theu want to change or keep. All I can do is tell him/her about my thoughts on their story. It also helps if the author has a lot if beta readers so if there’s an issue everyone notices then that issue should be worked on.

5. Track changes.

MS Word has an awesome button called track changes. I like this because the author can see what I have changed and kept. Google Docs and I believe Drive also have a feature that let’s you see changes. This way, the author can knownwhat was changed without having to compare the documents side by side.

Lastly, my opinions and advice are my own. I don’t feel offended if an author disagrees with my comments. I’m just glad that they were willing to let me read their story.