The non-PEBKAC problem was that I was using Turbo Pascal 2.0 (1.0?) that couldn't identify I'd screwed up a method's parameter definition.
Doing things last second that didn't give you any chance to fix issues before a deadline is a flaw in and of itself and should be a lesson.
Unfortunately many don't understand this and I have many colleagues who slack off until it's almost too late and then there is a huge scramble before a deadline.
Of course your mileage mag vary, but I think it was very fair, and most of my classes were already way too easy - many students are just terrible and lazy. My classmates who became teacher assistants told me also that they felt terrible but they had to fail some students because they didn’t even turn up to their one past the last retake exam at all.
gcc myprogram.c
That brings you 90% of where you need to go, especially for a CS course.
It's not obvious to students. The insight to simplify and simplify until things work and only then keep piling new things on top, that's a really powerful one and is underappreciated in teaching CS.
I got a 60% one for an assignment that demonstrably implemented all required features including the “for extra credit” ones, and a few more besides. I can only think it was scored by grams of documentation.
In the students mind they’re going to ask “is it fair to get a 0 when I feel close?” Then they (might) cheat. Obviously there are ways around this, like going in to office hours for help, but some schools start kids with C++, which seems like a wrong first language.