But the situation I described included the basics. I specifically remember explaining pointers to a friend and working through a simple assignment on C pointers with them, for example. Absolute basics, yet collaborative working helped them greatly.
Perhaps your policy puts TAs there in that situation, and I understand that.
We need students to work together and share their experiences. Then we need each one to achieve the learning goals (and we should not assess work they did far from our eyes. We should assess their understanding and skills in front of us).
standardized and written tests, online school, homework, etc is just a way for professors (and increasingly, just TA's) who have no interest in teaching, to get the job done with less time and more efficiently.
Oral exams solve this problem entirely
Sorry, if your answer as to why using a beneficial pedagogical approach is your class sizes are too large, then it sounds like your class sizes are too large!
>> Do not look at other students’ homework files and do not work with other students. At all.
> This is a horrific policy. We work better with other people.
I think that line was in connect with quizzes, which are presumably online. Near the top of the article it says > You may discuss assignments in a general way with other students, but you may not consult anyone else's work.
I'd be with you if they made everyone work in "clean rooms" but that is appropriate for quizzes and tests.As someone who's graded lots of undergrads I can tell you that cheating is prolific. It's easy to identify who is copying code, but it is hard to prove. My wife teaches in another department and says the same thing. AI use has grown exponentially and it's really destructive to the education process. Though I have more complex thoughts on this and that it is just exacerbating larger problems that no one wants to actually solve because they'd be very hard to solve in a way you can have clear metrics for the bureaucrats (including industry). Proper evaluation is unfortunately always going to be fuzzy. Metrics are in contention with making a meritocracy, especially if you don't have a deep understanding of said metrics
Clearly in this world the frats and the sorority members get the highest scores, and after that the best looking, the most amusing or charming etc.. so unless that’s the intent the whole approach is perhaps worth reconsidering.
If you want to teach to improve your understanding the normal thing is you become a TA so that access is open.. not open every assignment to ad hoc collaboration so you disadvantage half of the students on every assignment
As you point out, there are plenty of students who flat-out copy each other. Filtering out those students does plenty to enrich the remaining students, you don't need to go on witch hunts to find ever-more subtle cheating.
So... what it says?
For people that haven't spent time teaching lower-level programming courses, policies like this may seem overly harsh. But, remember, they're not solving particularly advanced problems at this stage. Instead they're mastering fundamentals. An analogy I like to use is learning to play the piano. If someone else is doing it for you, you're not going to develop the skill.
The main reason for the policy is that many students are not able to walk the line between leading someone to a solution and giving them a solution. The teaching staff know how to do this. When students help each other in situations like this, many times they end up just providing code or allowing someone to look at their code (ultimately copying it), etc.
Yet I also understand your view -- students providing and copying code yet not learning and doing work themselves. I completely get that needs to be found. Yet, reading the article I felt truly scared for the students who might get caught up in this yet I don't think would have actually done anything wrong.
I get that, and I think that is partly what drove a lot of the initial turmoil when this started. But, the important thing to recognize (and this could have been better emphasized for sure) is that it's really easy to tell whether someone caught up in this is cheating. A 5 minute discussion is all it takes. And, yeah, maybe some could BS their way through a discussion like that if they had a heads up, but at that point 1) they've now learned at least some of the material and 2) you're not going to catch everyone anyway. Processes like this are somewhat like a police officer catching people speeding. The enforcement alone discourages the behavior, to a degree, and you're never going to catch everyone.
This is a horrific policy. We work better with other people.
When I studied computer science, other students came to me for help. I helped them. We discussed problems together. I saw their code. They saw mine. No one copied: we shared approaches and style and thinking. I shared how I solved things. They learned my thinking. By explaining, I understood what I knew better. Sometimes I learned from them: an idea I wouldn’t have had alone, a new direction. All of us were better off. This was across multiple people.
It was in no way discouraged and so long as you wrote your work — while asking others for help was fine — you were okay.
Humans learn through teaching. We learn through discussion. We learn through interaction. Solitude — ‘do not work with other students. At all’ — is the exact opposite of a healthy learning environment.
I don’t care what their artificial intelligence policy is. I cannot state strongly enough how much I revolt against their human intelligence policy.
As for the lecturer’s warnings in slides: that reads like a trap.