I’m also on the side of “would love to have such feedback as instructor, but would rather not automate decisions from it”.
What I would add is that I think something that goes off the “submission” that is triggered with the run button would be limited, unless I misunderstood the intent. Personally I would rather see something that simply records diffs on the code that the student is editing, maybe snapshotting it every 30-60 seconds or whatever a suitable time is, and records those snapshots/diffs (whenever there is a change of course) for the instructor’s perusal. Maybe this is happening already? I’m kind of new to it. Would it be too resource-intensive on the storage side? It doesn’t have to phone home on every change, perhaps it can still only send the collection of changes on the run button click, but it would send basically multiple snapshots on each run, if that makes sense.
Charilaos Skiadas
Professor in Mathematics and Computer Science
Hanover College