Why you don't want me as a teammate

Yes, I turned this in.
Yes, everyone had a good laugh.

Name: Bryce Anderson

Department of Computer Science

CS 3500

Software Practice - Evaluation

  1. Critical evaluation - provide a critical evaluation of yourself, each of your team members, describing the weaknesses and strengths of your or their performance during the project.  If you decide to grade your team members higher or lower than the team average, please justify that in this description.



**** So, let me get this straight: If I say I did all the work,****
****I get all the points, right? Okay, here we go. ****




Person

Evaluation

You

A rock. A shining beacon of dedication and perseverance awash in a sea of mediocrity, ineptitude, and overall slackfulness. A coding god, the likes of which has never been seen in our lifetimes. Singlehandedly saved the project from itself.

Alex Munk

May have turned in a .h file at some point. Or possibly it was an early draft of his screenplay. I honestly couldn't tell which because it was written in green crayon on the back of a napkin.

Nicholas Oliver

Three days after the project began, Nick fled to Mexico, leaving his wife and family and taking only three bottles of water, an extra-large canister of Cheez-whiz, and twelve highly trained ferrets. The last time I talked to him, he was muttering something about "regime change," but I'm not sure that's relevant.

Jonathon Duerig

Barricaded himself in his room the day the final project was announced. Coded day and night, refusing both food and sleep for two weeks. Finally, he emerged, having rewritten GCC for the .NET platform. I asked if it was really necessary, and he shouted incoherently about "needing the proper tools". He said I didn't understand his vision, and then started working on an EMACS-based Visual Studios clone.

 

  1. Work fairness - grade yourself and your team members on how well you did your project, taking into account distribution of work. How well did each team member meet their commitments to the team and to you? Was the initial partitioning of work accurate and fair? For example, although one person may have done less actual work, if they did all of the work that was given to them, in a timely manner, then they deserve an A. If someone did not work the entire time and basically is just riding on the coattails of the rest of the team, then they deserve an E. So, for each person that you are evaluating (including yourself), give an overall letter grade (A-E with A being the best, E being the worst).

Team Member Name

Grade

You

A+++++++++++++++++++++++

Alex Munk

F-

Nicholas Oliver

Is there anything lower than an F-? Just curious.

Jonathon Duerig

D (for effort)