Kevin Chen writes a post in his blog about incentives and scaling from his two years as a teaching assistant. Specifically in his current post he addresses plagiarism in computer science and why it has still not stopped.
The most important goal is to keep the course fair for students who do honest work. Instructors must assign grades that accurately reflect performance. A student who grapples with a problem — becoming a stronger programmer in the process — should never receive a lower grade than one who copies and pastes.
Finally, as educators, we also hope that the accused student can learn difficult lessons about ethical behavior in the classroom rather than the workplace.
From his experience, every semester somewhere between 10% to 40% of the students carry out blatant, indisputable cases of plagiarism with an unknown amount of less clear cases left unaddressed. How does this match with soylentil's experiences here, either in computer science or other fields? The perspectives are likely quite different from institution to institution as well as whether you are still studying in college or university, recently graduated, or in a teaching role.
(Score: 3, Interesting) by BsAtHome on Monday March 26 2018, @02:02PM
This is exactly why we shouldn't focus on the solution of the problem, but the process of getting to that solution.
Many, if not most, problems in programming have known solutions and a very big part of programming is pattern recognition of the problem and map it onto a known solution. But, the process of getting there is what makes programming interesting and is the great learning experience; not the actual solution itself.