Post #2575176

2026-03-05 11:41 UTC

@csgordon@discuss.systems @lindsey@recurse.social @jeremysiek@types.pl @krismicinski@types.pl I know it doesn’t help much, but I ask my students to produce a short report along side the technical submission. The idea being you can eyeball the differences between written report and code submission. Identify where more interrogation isrequired. I know genai could produce these reports but every little helps. Submission canaries, for want of a better phrase.

Replies (1)

@csgordon@discuss.systems 2026-03-05 11:53

@jfdm@discuss.systems @lindsey@recurse.social @jeremysiek@types.pl @krismicinski@types.pl I've long had students do a form of this with their assignments, but the generated reports got "good" enough a year and a half or so ago that I spent more time waffling on whether something crosses the line plus basically arguing politely with offended students than I would just meeting with everyone. (I'm sure this balance point varies depending how exactly you set things up with the report, but I couldn't figure out a more effective setup.) Meeting with everyone has ended up more equal for students, less frustrating for me, and more positive (i.e., non-adversarial) for students. The tipping point also depends on enrollment.

Open ##2575177