I have so much grading to do. Going to try to get this done tonight so I can work on Christmas Horse tomorrow.
I'm gonna use the "grade one CLASS at a time" strategy, so just grading my CS 200 stuff and getting that done before moving on.
I don't always have emojis in the little grading sheet but I do here for this project, thought it might add some visual representation of their performance.
Generally a 5/5 (100%) on an item means Mastery, 4.5/5 (90%) is satisfactory, 2/5 (less than 50%) means it's not good enough yet, usually just really broken or maybe the interface/code is really ugly.
Different criteria has different grades so for the 8 point one it's 8 points for mastery, 8*0.9, 8*0.5, etc.
I didn't make my CS 200 projects all connect together this semester so next semester I'd like to plan a little better and have it be one program they build up over time.
That just kind of requires me to plan the project before the semester starts, so I know where we end up at, and not be writing the project one at a time as we go through the semester, because I don't always have the foresight to make the design make sense further down the road. xD
When a certain student always turns in projects that have a ton of build errors...
(It was worse because they keep having "#include "XYZ.h" inside the XYZ.h file, it keeps happening, why does it keep happening???)
Some students waited *way too long* to start catching up, despite all my emails and warnings about it.