It's important to note that the students are encouraged to interact with the many teaching assistants that we have available. And, while that slide is somewhat harsh in how it states it, the larger lecture discussion surrounding it makes it clear that students are permitted to discuss assignments in a general way. When you get into implementation details, that's where the academic integrity problem arises.
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.
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.