pull down to refresh

One of the professors I had in advanced Java made a point of having folks explain their code, line by line, as well as being constrained to just the tools she gave for use in class. Anyone stupid enough to rely on AI 100% was always caught in those traps right away. They weren't hard to deal with, but the laziness of some students was shocking.

Explain the code line by line in-person or using comments? Because wouldn't the AI also be able to add comments?

Similarly with restricted toolset. You can just prompt the AI to use the allowed tools.

reply

AI uses a very dumbass obvious form of English. When you compare a student's emails to the language used explaining code, it becomes very clear to someone who does know code when the person is bullshitting. In-person would be even harder to evade. LOL. What's this function form? Um, it defines i. Yes, but what does it do? It loops i! And then what? Well, you get i +1... So lots of i's.

reply
When you compare a student's emails to the language used explaining code, it becomes very clear to someone who does know code when the person is bullshitting

100%. It's pretty easy to spot students' AI use, but I kinda hate grading based on that subjective feel, so I avoid it as much as I can. Because of that, my implicit AI policy is very permissive.

In-person would be even harder to evade

Most of my students would get absolutely wrecked in any kind of in-person assessment

reply

It should be done at least once in a class. They would have to do the same thing in a scrum meeting in the real workplace explaining what they did the day/night before to a senior dev or a project manager. I quiz my contractors all the time. Drives the contractor PM nuts, but he respects it.

reply