Final Course Due Dates and Requirements
Tuesday, December 9th
- Multimedia documentation due
Thursday, December 11th
- Documentation projects accepted
- Two memos detailing
individual class contributions (e.g., weekly articles, comments, blog entries, etc.) and
individual contribution to group work (i.e., what you contributed to your group projects) signed by all group members
- Group project evaluation attached below
- Article on technical writing and a detailed analysis submitted to course website with print copy brought to class (only applies to students who need to make up for previous weekly articles)
- class will be held at Scotty's
Tuesday, December 16th
from 10:00 am - 12:00 pm in Heavilon 220 (Cat's office)
- Final draft of multimedia documentation due (revisions based on class and instructor comments
- last day to turn in documentation project
- last day to turn in revised employment projects
Dates to know and love
A brief recap of the dates that I've given in class:
Tuesday, November 25th
- Professional white paper revisions due
- Rough draft of usability documentation due (Project 3)
Tuesday, December 2nd
- Revised employment projects due
Tuesday, December 9th
- Multimedia documentation due
- Revised written documentation due
Annotated Bibliography Resources
Purdue OWL's page on Annotated Bibliographies and sample annotated bibliography
UNC page on annotated bibliographies
Cornell Library page on annotated bibliographoes
Purdue OWL's handout on paraphrasing
Randy Taylor's Complaint
Post your sources for the Randy Taylor research exercise as a comment to this post.
English 421=Shipbuilding 101?
While I was evaluating potential strategies in my head, my initial response was to hang back and see what other people thought. With such a large group of peers, no clear command structure existed, and I was hesitant to give my input for fear of appearing to "take control." I think this observation applies to the white paper project, especially since we will be writing in groups. While a rigid command structure is not crucial to group writing--and in the case of writing with peers may actually be detrimental--, a form of defined leadership helps
That crazy pirate
Building that pirate ship was a great analogy towards writing in a group environment. I think that as well as demonstrating many of the principals of; seeing the big picture first before you iron out the details, of how to effectively break off the work so that maximum efficiency is achieved. It was also a great team building exercise I think it got everyone in the class talking and working together to discuss how to get this task accomplished. It showed how some people stand up and start delegating and others listen to delegations and participate and help in their own way.
Arrrrrrrrrrrrrbys
So at first I thought this was kind of a strange thing to do in an english class, but I usually do not think about things too deeply right at the beginning. This changed after we were told to think about how putting the pirate ship together with the a large group of people was analogous to a technical writing and our white paper project.
Tis a Pirate's life for me
The pirate's ship activity that we are doing in class is an obvious analogy for the skills which are very crucial to the technical writing field. While the ability to organize and classify information, like the step-by-step directions, are definitely important, there were some smaller lessons to be learned as well. For example, we were pretty sure that we had most of the steps in the correct order, but weren't totally convinced.
Resources for Resumes and Cover Letters
Based on your cover letters and resumes thus far, I believe that the following information will be key in the revision process.
Below, please find some resume and cover letter writing resources:
Statements to Avoid on Your Cover Letter:
Navigation
User login
New forum topics
Who's online
There are currently 0 users and 0 guests online.