[top] [TitleIndex] [WordIndex]


Peer Grading Guidelines

As we've mentioned in class, you're going to be grading one another's assignments. Learning to read, evaluate, and test other people's code is an extremely important skill for any programming you'll do as a part of your job, be it in industry or academia. If you're a novice programmer, you'll get the chance to see how more seasoned programmers attack various problems, and pick up a few tricks. Even if you're old hat at this, I can virtually guarantee that you'll learn something by thinking back through the basics, or explaining why something isn't working in simple terms. Plus, you'll get much more feedback from your peers than we'd have time to provide on every single assignment.

Send what where?

First, let's go through the mechanics of how we've set this up. Here's how the system will work:

So to summarize:

How should I grade?

First and foremost, let me say: your goal as a grader should be to provide as much useful, constructive feedback as possible. We're going to have a simple grading scale for each problem: everything gets either 2, 1, or 0 points. For the record, we're not trying to meet any "curve" here -- we'd be happy to see most students get full credit on most of the problems they do, as long as they're actually correct.

An important note: you should be able to back up any claims about their code failing to function with inputs that demonstrate the bad behavior. So if you say "this goes into an infinite loop sometimes," you need to back that up with an example of input that goes into an infinite loop.

Are we graded on our grading?

Yes, you are. We're going to glance over the comments you make, and we're looking for a few things:

Basically, we're going to look and make sure you took the time to grade carefully.

2013-05-11 18:32