« November 02, 2005 | Main | November 09, 2005 »
November 07, 2005
Finding Outside Sources for Your Project
Download file
(PDF, 1 page)
On Wed 11/9 class will meet in G8A FLB
Peer-Review a Playful Technology Proposal
For this assignment, first re-read the grading rubric passed out in class on 10/19. Then, follow the instructions given in the last class and summarized in the Illustrated Guide to Commenting on Blogs to obtain a TypeKey user account so that you can submit comments to student blogs. Next, read the project proposal on the blog listed below yours. If there is no proposal (e.g., the student dropped the class), move down to the next blog. If you are last, start at the top.
Write constructive comments on the proposal. A constructive comment is one that contributes helpfully to the development of the project. For instance, the comment "Fun!" is nice but it is NOT constructive because it doesn't leave the reader with any ideas for improving the project. Examples of phrases that might be helpful:
- "The most interesting part of your project is ____, you could develop that more."
- "I wasn't sure what you meant when you wrote ____"
- "When I read the second paragraph, it reminded me of the concept ____ from the ____ reading."
- "I think the project menu item ____ could be really interesting for your project. You could write about ____ ..."
- "____ could be a good source of videos / images / storyboard ideas for your project."
- "Maybe doing ____ would be a good idea for your fieldwork."
- "I've played the game ____ and it could be a useful source of ideas for this project."
- "The ____ reading said '____' (on page ____) about what you wrote."
- "The lecture on ____ talked about what you wrote about ____ ..."
Note that it is HARD to write constructive comments. Please give this a genuine effort and spend the time required to give your peer comments they can truly use. It will help to look back over your old notes and flip through past readings and the readings list for the course. Keep the grading rubric in mind -- remember that the class project is supposed to show off knowledge of class material. IMPORTANT: Suggesting design changes or detailed features is not constructive unless you link these suggestions to course material. To receive credit, your overall comments must contain references to course material.
Finally, after you have written these comments,
- use your TypeKey account to post them as a comment on the proposal blog entry
- press refresh to be sure the comment appears on the blog entry where you posted it
- copy the URL of the project proposal entry where your comment appears
- post a one-sentence entry to your own blog that says "I peer-reviewed the project ____" that includes a link to your review. (To make a link in Movable Type, highlight the text you want to be clickable, then press the link button
just above the editing window.)
To receive credit, your comment and blog post with a link to it must be on time, at least 200 words, and must contain constructive statements about the project. Please write, spell-check, and save your blog posts in a word processor first, then post them to your blog. When you make a direct quotation or paraphrase, include a citation to the page and author where you found the material. DUE: 11:30 a.m. on Monday, October 17 (one hour before class begins).
Parasitic Interventions
Schleiner, A.-M. (1999). Parasitic Interventions: Game Patches and Hacker Art. Opensorcery.net Texts: Unpublished manuscript. http://www.opensorcery.net/patch.html
Subversion and Play
In class demonstration: UIUC Library Online Research Resources (search for "ComAbstracts", "ProQuest").
In class examples: machinima, Red Vs Blue, Ice Man Commeth.