3 ms·
I especially noticed this when grading programming projects, because it is slightly complicated. I’d either find that: A bug was really common, got to re-eval
by bee_rider 3y ago
I especially noticed this when grading programming projects, because it is slightly complicated.
I’d either find that:
A bug was really common, got to re-evaluate after the first couple times I see it, apparently it is an easy mistake to make.
Or, I’d find a new bug that was pretty common, but which I didn’t know about at first. Got to update my tests and re-run everybody.
I tended to be really thorough and re-do the whole stack eventually, but it was a real pain. Could have half-assed it of course, but they spend weeks on these things, feel like I owe them honest feedback.
It would tend to lead me to “softer” grading as well, if you are lazy and only check for a couple bugs, you might take a large number of points off for each problem. Finding some problems and punishing them harshly is not very fair for those students that randomly hit the bugs you expect. If you find every bug, you can only take a couple points off per bug without tanking everybody’s score.