I think the best you can do here, is to grade based upon what is in front of you.
If the code doesn't work, it means they (as you said), didn't understand what they copy and pasted. And as the whole point is to demonstrate learning, understanding, it is valid to mark such things as failures of that.
And this matches real world expectations too.
If there is any way you can tilt assignments to better demonstrate understanding, that's a win.
Hmm.
You could try to break up responses. By that I mean, have a dozen short coding exercises, but then tie them all together.
EG In the end, one bit of code to call the api/functions of the rest?
Having multiple exercises that in the end get tied together is a pretty good idea! This would also highlight inconsistencies between different pieces of code that may indicate that the code has been generated and/or students are not understanding what they are doing.
Comments
I think the best you can do here, is to grade based upon what is in front of you.
If the code doesn't work, it means they (as you said), didn't understand what they copy and pasted. And as the whole point is to demonstrate learning, understanding, it is valid to mark such things as failures of that.
And this matches real world expectations too.
If there is any way you can tilt assignments to better demonstrate understanding, that's a win.
Hmm.
You could try to break up responses. By that I mean, have a dozen short coding exercises, but then tie them all together.
EG In the end, one bit of code to call the api/functions of the rest?
It might help break AI responses a bit.
Having multiple exercises that in the end get tied together is a pretty good idea! This would also highlight inconsistencies between different pieces of code that may indicate that the code has been generated and/or students are not understanding what they are doing.