Slashdot Mirror


Academic Dishonesty-When Is It REALLY Cheating?

ConcernedStudent asks: "Recently, 10 of my fellow classmates have been brought up on academic dishonesty charges in a senior level engineering class concerning a recent programming project. Granted, some copied other code verbatim and deserve to be caught, probably moreso for just being that stupid. However, there are those who have been implicated because they referenced code of somewhat dissimilar projects from previous semesters at some point during their design process. As long as the old code was not passed off as their own work for a grade and does not appear in the final draft of the code, is this really considered dishonest? How is this different than referencing a book on the language or some other "legitimate" source? At what point does referencing outside sources become dishonest? Is it just to review historical copies of code (using JFS) which were not submitted for grading to see if questionable code exists in these intermedite draft copies of the program? As this is a somewhat grey area, hopefully someone out there has comments which may help to clarify some of the uncertainty."

4 of 120 comments (clear)

  1. Two simple rules by vlax · · Score: 5

    I learned two rules for avoiding charges of cheating in my CS department, both of which strike me as pretty sound:

    1 - You can't be punished for citing references.

    If you get code from some source and you document it, you say so when you turn it in, it isn't cheating. You may not get a very good grade and your prof may not be pleased, but you can't be brought up on charges of cheating.

    2 - The Gilligan's Island rule

    If you look at someone else's code, then go watch an episode of Gilligan's Island. Anything you can still remember afterwards is fair use. This was treated as a way of defining the line between copying someone else's code and learning from it. As rule, it won't save you in a court of law, but unless you have superhuman memory, you will be hard pressed to remember enough detail about someone else's work to be demonstrably cheating from it.

    I have never heard of a student using these policies ever having been charged with academic improprieties. They are much, much easier to follow than the rules for when you can and can't sleep with profs and TA's.

  2. Cheating is a part of academia by JanneM · · Score: 5

    I appreciate the fact that one is supposed to work out their own solution to problem posed in class or on assignments. However, there is a form of academic cheating that is rampant throughout the university world.

    A little more than a year ago, the pages of Science where alive with the debate over whether a certain professor had published erroneous results or not. The case was as follows: his graduate student had been doing a series of experiments, and published a couple of papers on this -- with the professor as the first author. Some of you may not know this, but the tradition is that the person responsible for most of the work is cited first, followed by others, and, sometimes, followed by the professor (or other 'grey eminence') last.

    In this case, it turned out that the graduate student had faked his data to fit with his theory. The professor -- who had been the first name on the paper -- excused himself by saying that he had not even read the paper in question.

    So, either he did read the paper, examined the results, and published anyway, and is guilty of fraud; or he had his name as the first author of a paper he didn't even read until it blew up in his face.

    This _really_ makes you wonder about scientinsts that have hundreds of papers to their name -- papers that are really the basis of their careers...

    --
    Trust the Computer. The Computer is your friend.
  3. An ex-T.A. speaks out... by chipuni · · Score: 5
    I always went by the phrase:
    • If you copy it, and you don't give attribution, it's stealing.
    • If you copy it, and you give attribution, it's research.

    Academics is filled with research, including computer science. Your question didn't tell whether you gave a full and clear attribution of where you found the code.

    If you did, then at a hearing, bring in just about any academic journal, and show how every paper references at least five other papers.

    --
    Never play leapfrog with a unicorn. Or a juggernaut.
  4. The Sad Truth About Higher Education and Cheating by Ars-Fartsica · · Score: 5
    As someone who spent two years as a teaching assistant in a well known university, that students are in university to get high marks, not to get an education.

    I once held an informal poll among the undergrads and concluded that almost all of them chose courses they could get high marks in, and almost all of them would opt to get a high mark than to focus on learning.

    As for cheating - what do you expect? The whole educational experience is driven by marks, so cheating is a natural by-product. Some schools try to get around this by focusing on examinations instead of assignments for the bulk of the course marks, but it has been demonstrated again and again that exams only teach one thing - how to do well on exams.

    The only way to get technical education back on track is to make co-operative/work terms mandatory, even for students who wish to pursue theoretical avenues.