Hello, everybody. Since I have added some new Blogspot and Google addresses to my paper lists this week, I thought it would be a good idea to let you guys know about them. The complete lists (so far) are as follows.
Here are the Blogspot addresses:
Myself: jasonwilliamseng101metadiscourse.blogspot.com/
Steve (Overall Class): eng101fall2007uat.blogspot.com/
Joshua Tornetta: joshtornettaeng101metadiscourse.blogspot.com/
Daniel Soltyka: danielsoltykaeng101metadiscourse.blogspot.com/
Seth McElroy: sethmcelroyeng101metadiscourse.blogspot.com/
Helen Walters: helenwalterseng101metadiscourse.blogspot.com/
Stephen Allen: stephenalleneng101metadiscourse.blogspot.com/
Travis Mohler: travismohlereng101metadiscourse.blogspot.com/
Daniel Bialecki: danbialeckieng101metadiscourse.blogspot.com/
Anthony Pine: anthonypineeng101metadiscourse.blogspot.com/
Joshua Upton: joshuauptoneng101metadiscourse.blogspot.com/
Brandon Richard: waldothecat.blogspot.com/
Robert Newbry: robertnewbryeng101metadiscourse.blogspot.com/
Tony Kanaan: tonykanaaneng101metadiscourse.blogspot.com/
Clint Monette: clintmonetteeng101metadiscourse.blogspot.com/
Bradford Hale: bradfordhaleeng101metadiscourse.blogspot.com/
Zachary Potilechio: zpott.blogspot.com/
Next, here are the Google addresses:
Myself: jasonkdude@gmail.com
Steve (Instructor): prof.brandon@gmail.com
Tony Kanaan: kanaant@gmail.com
Stephen Allen: quadcored@gmail.com
Joshua Tornetta: tornettaj@gmail.com
Seth McElroy: malekk77@gmail.com
Clint Monette: deadnerve@gmail.com
Brandon Richard: waldothecat@gmail.com
Robert Newbry: saiule.sarin@gmail.com
Travis Mohler: deydrakayne@gmail.com
Anthony Pine: awpine@gmail.com
Paul Oyola: betaboy99@gmail.com
Daniel Bialecki: danbialecki@gmail.com
Helen Walters: helen.m.walters@gmail.com
Daniel Soltyka: dsoltyka@gmail.com
Okay, that should be everybody. The last thing that I really want to say is thank you! All of you have been so helpful not only in the class shell discussions but also with reviews and comments about my papers on Google Docs. You have helped me to refine my writing and even made me laugh sometimes. I hope that I have returned the favor. I didn't know a majority of you coming into this class, but I can now count you among the other great students that I have met in previous classes.
I know that it sounds like I am saying goodbye, but next week is probably going to be really busy for us all. So, I just wanted to say it here. Especially since I noticed that I have not responded to most of your critiques within my papers. Again, thank you for your support!!!
Sunday, December 9, 2007
Thursday, December 6, 2007
Week 4 - Final Project Portfolio Cover Page Pre-Writing Exercise
Here is my pre-writing exercise for the Portfolio cover page draft that we have to do this week. I hope it is comprehensive, and makes sense. In any case, here it goes:
Who is your audience(s)?
As with all other formal assignments and really anything that I have produced for this class, my audience for this assignment consists of my fellow classmates as well as our instructor, Steve.
What goals do you want to achieve by producing your text?
The main purpose of the cover page for my Portfolio Assignment is to argue for my final class grade. I will back up my opinion by mentioning the work that I have done in the class not only for myself, but to also help my fellow classmates.
However, I can't really see another goal for this assignment other than the one mentioned above. So in simple terms, the goal that I want to achieve by producing this text is to effectively show that I deserve an "A" for this class based on the work that I have put into it.
What is your topic?
My topic is a cover page for this class's Portfolio, where I will argue for a certain overall grade and use my class work as evidence to back up my opinion.
How will you organize the text?
I will start by making a claim about what I think my final class grade should be. Like I mentioned previously, I will make a claim for an "A". I will then talk about exactly what I have done in class to warrant that "A". The first thing that I will mention is all of the discussion posts that I did before we were told that we should ignore most of the class shell. I have all of these posts in one document, which I will point to in the cover page itself.
Next, I will talk about how I seem to do well on the formal assignments even with my first drafts. I am also able to improve upon those documents with further drafts.
I believe the last thing that I will talk about is how I have commented on the work of fellow students, helped them as much as I can, and also taken their critiques of my own work to heart.
I don't want to sound like I am conceded, but since I am trying to justify my own final grade, I think I have to toot my own horn a little!
I hope that effectively answered all of the questions. Onto the cover page!
Who is your audience(s)?
As with all other formal assignments and really anything that I have produced for this class, my audience for this assignment consists of my fellow classmates as well as our instructor, Steve.
What goals do you want to achieve by producing your text?
The main purpose of the cover page for my Portfolio Assignment is to argue for my final class grade. I will back up my opinion by mentioning the work that I have done in the class not only for myself, but to also help my fellow classmates.
However, I can't really see another goal for this assignment other than the one mentioned above. So in simple terms, the goal that I want to achieve by producing this text is to effectively show that I deserve an "A" for this class based on the work that I have put into it.
What is your topic?
My topic is a cover page for this class's Portfolio, where I will argue for a certain overall grade and use my class work as evidence to back up my opinion.
How will you organize the text?
I will start by making a claim about what I think my final class grade should be. Like I mentioned previously, I will make a claim for an "A". I will then talk about exactly what I have done in class to warrant that "A". The first thing that I will mention is all of the discussion posts that I did before we were told that we should ignore most of the class shell. I have all of these posts in one document, which I will point to in the cover page itself.
Next, I will talk about how I seem to do well on the formal assignments even with my first drafts. I am also able to improve upon those documents with further drafts.
I believe the last thing that I will talk about is how I have commented on the work of fellow students, helped them as much as I can, and also taken their critiques of my own work to heart.
I don't want to sound like I am conceded, but since I am trying to justify my own final grade, I think I have to toot my own horn a little!
I hope that effectively answered all of the questions. Onto the cover page!
Week 4 Peer Editing Assignment
Hello, everyone! I wasn't exactly sure where to put this, but I thought my blog would be as good as any place.
For this week's Peer Editing Assignment, I have proofread four student docs that were shared with me using Google Docs. For each one, I used a different proofreading technique. I just focused on surface level issues like incorrect spelling and punctuation since this is proofreading, not revising. I also used a light green text to show what I had changed.
First of all, I just have to say that there were very few surface level issues. In Seth's case, there were none that I needed to correct. I will now break my thoughts down into sections based on who's work I proofread.
Week 3 Essay: Process Analysis by Stephen Allen
On this project, I used the technique "Read backwards from the last sentence to the first". This was the most interesting technique out of the four that I chose. Because you are reading backwards, you aren't looking at things like how the paper "flows". It really put the words into focus for me. At first, it was a little confusing because I have never used this technique before. Once I got used to it, it was pretty effective since I was only supposed to look at surface level issues. Onto the actual paper, Stephen did really well. There were a few misspelled words like separate being spelled seperate, but that was about it. Very nice job, Stephen!
TAMohler Week 4 Cover Letter Draft by Travis Mohler
On this project, I used the technique "Read slowly and out loud". I was pretty comfortable with this technique since I already use it regularly. Well, as regularly as I can without disturbing my parents! It was also different from the previous technique because I actually did get into the flow of the paper. I tried to stay on the surface level, though. With all of that said, I only found one word tense mistake and the sentence about Travis' efficiency with Google Docs was a little unclear. I edited it to make it a little clearer. I believe that this last aspect is still on the surface level, but if one of you thinks it is not, let me know. Still, good job with the paper, Travis.
Week 3: Process of Recording and Mixing by Daniel Soltyka
On this project, I used the technique "Physically touch every word". While I have used this technique a few times before, I don't use it regularly. I think my biggest problem is touching the words at a fast enough pace that I don't get lost in my head. This technique combined with the previous one could be a really good combination technique, though. As far as Daniel's paper goes,
there were just a few words that were not spelled correctly. However, it was great otherwise, Daniel!
Inventory by Seth McElroy
On this project, I used the technique "Use the grammar and spell checker". This technique I try to use as regularly as possible. Almost any computer tool that we use for text creation should and often does have a spell checker. While I don't think this technique should be used alone it can be a simple and effective technique to start proofreading with. When I actually used Google Docs' spell checker, it only detected the word McElroy. This was probably because the name was not in the spell checker's library of words. Since it was not an actual misspelling, I did not change it. So, nice job goes to Seth as well!
Overall, you guys did great, and I want to thank you for sharing your docs with me. This was an interesting assignment, and I might actually add the techniques "Read backwards from the last sentence to the first" and "Physically touch every word" to my regular process. In any case, I will post my pre-writing exercise for my WPA Inventory cover page as soon as possible. Hopefully, in a few hours!
For this week's Peer Editing Assignment, I have proofread four student docs that were shared with me using Google Docs. For each one, I used a different proofreading technique. I just focused on surface level issues like incorrect spelling and punctuation since this is proofreading, not revising. I also used a light green text to show what I had changed.
First of all, I just have to say that there were very few surface level issues. In Seth's case, there were none that I needed to correct. I will now break my thoughts down into sections based on who's work I proofread.
Week 3 Essay: Process Analysis by Stephen Allen
On this project, I used the technique "Read backwards from the last sentence to the first". This was the most interesting technique out of the four that I chose. Because you are reading backwards, you aren't looking at things like how the paper "flows". It really put the words into focus for me. At first, it was a little confusing because I have never used this technique before. Once I got used to it, it was pretty effective since I was only supposed to look at surface level issues. Onto the actual paper, Stephen did really well. There were a few misspelled words like separate being spelled seperate, but that was about it. Very nice job, Stephen!
TAMohler Week 4 Cover Letter Draft by Travis Mohler
On this project, I used the technique "Read slowly and out loud". I was pretty comfortable with this technique since I already use it regularly. Well, as regularly as I can without disturbing my parents! It was also different from the previous technique because I actually did get into the flow of the paper. I tried to stay on the surface level, though. With all of that said, I only found one word tense mistake and the sentence about Travis' efficiency with Google Docs was a little unclear. I edited it to make it a little clearer. I believe that this last aspect is still on the surface level, but if one of you thinks it is not, let me know. Still, good job with the paper, Travis.
Week 3: Process of Recording and Mixing by Daniel Soltyka
On this project, I used the technique "Physically touch every word". While I have used this technique a few times before, I don't use it regularly. I think my biggest problem is touching the words at a fast enough pace that I don't get lost in my head. This technique combined with the previous one could be a really good combination technique, though. As far as Daniel's paper goes,
there were just a few words that were not spelled correctly. However, it was great otherwise, Daniel!
Inventory by Seth McElroy
On this project, I used the technique "Use the grammar and spell checker". This technique I try to use as regularly as possible. Almost any computer tool that we use for text creation should and often does have a spell checker. While I don't think this technique should be used alone it can be a simple and effective technique to start proofreading with. When I actually used Google Docs' spell checker, it only detected the word McElroy. This was probably because the name was not in the spell checker's library of words. Since it was not an actual misspelling, I did not change it. So, nice job goes to Seth as well!
Overall, you guys did great, and I want to thank you for sharing your docs with me. This was an interesting assignment, and I might actually add the techniques "Read backwards from the last sentence to the first" and "Physically touch every word" to my regular process. In any case, I will post my pre-writing exercise for my WPA Inventory cover page as soon as possible. Hopefully, in a few hours!
Saturday, December 1, 2007
Further Thoughts on Essay 3 - Game Level Design Process
Per Joshua Tornetta's suggestions, here are some further thoughts about my Essay 3 - Game Level Design Process.
To me, the whole purpose behind this assignment is to identify the general process that each of us uses to complete tasks. I have chosen to do this by talking about one specific task that I did in the past, and seeing where I could have done better by altering my process.
In general, I don't think I do enough preplanning with my tasks. I don't have a job, so when I say tasks, that normally means tasks relating to college work. I think the message that I want to get accross to my audience is that preplanning is important so that you can do the best job possible. I have done pretty well in school, college and otherwise. However, in the case of the game level I designed, I could have made it better by doing preplanning in the beginning of the project.
Before I go into the actual content of the essay, I should say that I have already written the essay and think that I am almost finished with my first draft. I started off the essay with some background information about Warcraft III: Reign of Chaos. It seemed like this would be a good idea in case anyone in my audience is not familiar with the game. In the second paragraph of my essay, I talked about the features of my finished level. This way, the reader would know about the finished product first, and then read the rest of the essay to see how I got there.
The UAT class where I created this level gave us the last two weeks of the class to create and refine the level. Therefore in my essay, I divide my process by the first week and then second week. I had to determine what the requirements were for the level, and how I could accomplish them. I think the two most important things that I learned from this assignment is that preplanning is very important, and also having time to review your work is important.
So, those are my further thoughts. Thanks to Joshua Tornetta, and I hope this makes my pre-writing opinions a little clearer!
To me, the whole purpose behind this assignment is to identify the general process that each of us uses to complete tasks. I have chosen to do this by talking about one specific task that I did in the past, and seeing where I could have done better by altering my process.
In general, I don't think I do enough preplanning with my tasks. I don't have a job, so when I say tasks, that normally means tasks relating to college work. I think the message that I want to get accross to my audience is that preplanning is important so that you can do the best job possible. I have done pretty well in school, college and otherwise. However, in the case of the game level I designed, I could have made it better by doing preplanning in the beginning of the project.
Before I go into the actual content of the essay, I should say that I have already written the essay and think that I am almost finished with my first draft. I started off the essay with some background information about Warcraft III: Reign of Chaos. It seemed like this would be a good idea in case anyone in my audience is not familiar with the game. In the second paragraph of my essay, I talked about the features of my finished level. This way, the reader would know about the finished product first, and then read the rest of the essay to see how I got there.
The UAT class where I created this level gave us the last two weeks of the class to create and refine the level. Therefore in my essay, I divide my process by the first week and then second week. I had to determine what the requirements were for the level, and how I could accomplish them. I think the two most important things that I learned from this assignment is that preplanning is very important, and also having time to review your work is important.
So, those are my further thoughts. Thanks to Joshua Tornetta, and I hope this makes my pre-writing opinions a little clearer!
Subscribe to:
Comments (Atom)