Friday, May 6, 2016

Open Post to Peer Reviewers

Below is a link to my podcast Rough Draft. Enjoy!

https://drive.google.com/open?id=0B5txK3C1QkvYczFNanMzSEx5aEU

  1. My main focus is to talk primarily about my past projects, and talk about my personal growth and realizations throughout the course of the semester.
  2. I sometimes randomly changed pacing of the argument, which was weird at times. I think I will be able to adjust accordingly for the final.
  3. I stuck to what we needed genre-wise for the podcast; I included a stinger, and included natural pauses in between thoughts to regather.

Peer Review 15

 For this blog post, I made a content suggestion about Sofia's podcast.

I reassured Sofia that the length of her podcast was not distracting in the slightest. It's even more distracting when you click on a youtube video and it's 3 hours long. No one has any interest in something that seems to drone and takes random, useless tangents.

Also, I noted the chronological ordering of events was extremely effective. It showed a natural growth pattern with regards to her work ethic and approach to time management in the class.

I made a content suggestion that she should add a closer. By adding a closer, it would make the final project seem much more "final" rather than just talking about the four different project. Overall, there were no major gripes.

Editorial Reports 15a and 15b

 These blog posts concern editorial reports for both 15a and 15b.

As far as my first body revision goes, I simply chunked my thoughts together so it would sound less like me droning and more like me talking. I also included more substance to fill the time.


Raw Body:
“On the very first project, when we were told we had to pick something to write about within our major, I knew that put 90% of the thing I wanted to write about off the table. I enjoy English class because it’s somewhere that I don’t have to go full on math-science mode. Don’t get me wrong, I love math and science, but not here. After I had chosen a topic that semi-suited my interests, I slammed together a bunch of paragraphs about how artificial intelligence is something we shouldn’t fear. My essay was pretty solid. I made my finishing touches, submitted, ready to get an A or a B at lowest. I was SHOCKED to see a 60% a few weeks later. Mortified, I opened the dropbox, to see that it was my ROUGHEST form of all the rough drafts I created. Lesson learned – do it right the first time. Don’t space out when submitting a paper, because that could be the thing to bite you in the back.

Revised Body:
"The layout of the class blindsided me from the start. On day one, we were told that we weren't going to read any books, do any quizzes on comprehension, or any of that normal song-and-dance English work. Instead, there were four major projects, one which just happened to be an essay. This seemed to be the easiest, so I decided to go with that. Once I was told that we had to write about something pertaining to our major, this is where things got a little bit funky. As an engineering major, I found it extremely hard to get passionate about WRITING about engineering.

I enjoy English class because it’s somewhere that I don’t have to go full on math-science mode. Don’t get me wrong, I love math and science, but not here. English is enjoyable because it's English class, not because it's "write about Engineering" class.

After I had chosen a topic that suited my interests, I pieced together my essay carefully and I have to admit, it was pretty solid. I made my finishing touches, submitted, ready to ace the first project. I was SHOCKED to see how low of a grade I got. Mortified, I opened the dropbox, to see that it was my ROUGHEST form of all the rough drafts I created.

This was a learning experience to not only double check, but triple check my submissions.


As far as this second revision goes, I decided that I needed more context to what I was talking about, and the exact difficulty that arose as a part of the interview. The t

Raw Body 2:
“When I heard we had to interview somebody, I was nervous. How was I going to speak intelligently to a PhD in electrical engineering when I struggle to write 5 lines of code on my own, have no experience with circuit boards, and haven’t even passed baby land math yet? After I sorted the details out, I realized I probably couldn’t speak intelligently and would be a waste of their time to go in person. So, I decided to do an email interview. After emailing 5 or so professors, I already had 2 lined up that I said I was going to on the blog work. One of the guys I intended to said he couldn’t do it, and the other said he could. I completely spaced, and I sent questions I made for the guy who couldn’t do it to a back up. And it was a MAJOR screw up! They were extremely focused questions about self-repairing mechanisms, completely proprietary to this one man’s work and theses. I had no choice but to backpedal awkwardly, and I never spoke after I got the answers to the interview. That’s why I hardly incorporated quotes into my QRG, but still got an A!

Revised Body 2:
“When I heard we had to interview somebody, I was nervous. How was I going to speak intelligently to a PhD in electrical engineering when I struggle to write 5 lines of code on my own, have no experience with circuit boards, and haven’t even passed baby land math yet? After I sorted the details out, I realized I probably couldn’t speak intelligently and would be a waste of their time to go in person. So, I decided to do an email interview.

After emailing 5 or so professors, I already had 2 lined up that I said I was going to on the blog work. One of the guys I intended to said he couldn’t do it, and the other said he could. I completely spaced, and I sent questions I made for the guy who couldn’t do it to a back up. And it was a MAJOR screw up! They were extremely focused questions about self-repairing mechanisms, completely proprietary to this one man’s work and theses. I had no choice but to backpedal awkwardly, and I never spoke after I got the answers to the interview.

The answers that I got from the interviews were lackluster at best. You could clearly tell that there was little time put aside for each person. Maybe it was how I worded the questions, but I think it was more a result of the individuals not wanting to dedicate time to some random freshman that they have no attachment to. Also, I might have screwed up saying it was for an English project. I think I would have been taken a little more seriously had I not done so. But hey, I ended up with an A on the project, so I can't complain too much. ”

Sunday, May 1, 2016

Peer Review

 For this blog post, I peer reviewed James' content outline.


I applauded James' ability to make the document concise. The readability of the document of a whole was extremely high due to his usage of chunking.

I made a brainstorming suggestion to include 1 sentence in each paragraph about how he was able to overcome said difficulties, if he was able to at all. It would provide more closure than simply identifying the issues and leaving the ends loose.


Production Reports 14a, 14b

This blog post concerns production reports for 14a and 14b.


Body:
This is where I talk about what happened on the first project. The first project was really solid, in my opinion… Until I submitted a rough, rough draft to the dropbox…. Dang.  I will talk also about how I realized the blog posts were not something I could procrastinate…. Recall the week when we had a rough draft AND blog work due. BAD!

Raw Content for Body 1:
“On the very first project, when we were told we had to pick something to write about within our major, I knew that put 90% of the thing I wanted to write about off the table. I enjoy English class because it’s somewhere that I don’t have to go full on math-science mode. Don’t get me wrong, I love math and science, but not here. After I had chosen a topic that semi-suited my interests, I slammed together a bunch of paragraphs about how artificial intelligence is something we shouldn’t fear. My essay was pretty solid. I made my finishing touches, submitted, ready to get an A or a B at lowest. I was SHOCKED to see a 60% a few weeks later. Mortified, I opened the dropbox, to see that it was my ROUGHEST form of all the rough drafts I created. Lesson learned – do it right the first time. Don’t space out when submitting a paper, because that could be the thing to bite you in the back.

Body 2:
This is where I talk about how disastrous my interviews went. I conducted both emails over email. One of the professors wasn’t available. Like an idiot, I emailed him the questions I made for the other specific professor. He was grossly offended, and it reflected in his email. I could feel the passive aggression radiating through his voice when I told him I was impressed with his COLLEAGUE’S work!


“When I heard we had to interview somebody, I was nervous. How was I going to speak intelligently to a PhD in electrical engineering when I struggle to write 5 lines of code on my own, have no experience with circuit boards, and haven’t even passed baby land math yet? After I sorted the details out, I realized I probably couldn’t speak intelligently and would be a waste of their time to go in person. So, I decided to do an email interview. After emailing 5 or so professors, I already had 2 lined up that I said I was going to on the blog work. One of the guys I intended to said he couldn’t do it, and the other said he could. I completely spaced, and I sent questions I made for the guy who couldn’t do it to a back up. And it was a MAJOR screw up! They were extremely focused questions about self-repairing mechanisms, completely proprietary to this one man’s work and theses. I had no choice but to backpedal awkwardly, and I never spoke after I got the answers to the interview. That’s why I hardly incorporated quotes into my QRG, but still got an A!”

Content Outline

This blog post concerns my content outline for the final project.

Intro:
I’m going to discuss the real reason that I decided to take English 109H: the fact that it was only a semester course. It had absolutely nothing to do with challenging my brain, testing my time management skills, or any precocious answer that I would have liked to be the real reason.

Body:
This is where I talk about what happened on the first project. The first project was really solid, in my opinion… Until I submitted a rough, rough draft to the dropbox…. Dang.  I will talk also about how I realized the blog posts were not something I could procrastinate…. Recall the week when we had a rough draft AND blog work due. BAD!

Body 2:
This is where I talk about how disastrous my interviews went. I conducted both emails over email. One of the professors wasn’t available. Like an idiot, I emailed him the questions I made for the other specific professor. He was grossly offended, and it reflected in his email. I could feel the passive aggression radiating through his voice when I told him I was impressed with his COLLEAGUE’S work!

Body 3:
This is where I talk about how surprised I was when I opened D2L and saw that I got an A on my QRG. At that point, I realized that it was all about the form. My QRG was much more polished – the content was arguably worse than the essay I got a 60% on, so that really goes to show that looks are everything.

Body 4:
I’m either going to talk about my favorite project, or about the project I felt was the hardest. This is a tentative holder paragraph.

Conclusion:

Give advice to students taking the class next year. My honest advice would be to get a lot of caffeine, accept the fact there is too much work, and get over it. Get the coffee ready and crank it out.

Production Schedule

This blog post concerns a rough content outline of the remaining few days to come.

MONDAY: Revise content outline
TUESDAY: Actually go through and talk on the podcast
WEDNESDAY: Global and Local Revisions
THURSDAY: Global and Local Revisions 

I can do all of this in my dorm on my PC and my laptop. Having both of those makes video editing a lot easier.