4 ms·

If the professor in question brings the university a lot of grant money, especially if they're tenured, a lot gets ignored. As for the honor code I cynically s

If the professor in question brings the university a lot of grant money, especially if they're tenured, a lot gets ignored. As for the honor code I cynically suspect it's more about having an item go use against someone when the university chooses, rather than a true standard that all are held to at all times. If nothing else, it's just tough for a large institution to handle all of its problems at once.

deleted 5y ago
[deleted]
saltminer 5y ago
Back when I worked as a tutor, we knew a lot about the professors since most of us were also TAs at some point or worked as TAs concurrently. Some were consistent in busting people for cheating, others tried to avoid it at all costs (because they based their self-worth on their Rate My Professor page), but a few were just capricious and arbitrary. On their good side? "Eh, everyone uses Stack Overflow [or forgets to do anything to hide their plagiarism, not even bothering to edit the author name Javadoc comment on the code they copied] every now and then." On their bad side? "Copying others' work is unacceptable, you can either take an F in the course or plead your case to Academic Integrity." Of course, the ones who showed favoritism were also the ones who practically printed grant money, so nothing ever happened while I was there (and I doubt anything ever will).
- downrightmike 5y ago
  With code, as long as it works, so what. Plus learning a language requires copying to learn how to do it correctly. Would you want to be required to be completely original learning French? It makes no sense to burn people for doing what it took industry decades to figure out.
  - CountHackulus 5y ago
    Because the goal of the assignment isn't to write code, it's to learn what code to write. If you're copy and pasting from someone else you're potentially skipping out on a lot of learning. Granted, good luck passing the exam with copy and paste, but I've seen someone do basically that for 5 years, don't know if they ever graduated but they were grinding it out.
  - macintux 5y ago
    > With code, as long as it works, so what. Working as a lab instructor a lifetime ago, I graded two students' C assignments that both worked (mostly) but clearly without understanding what was going on. It took me a while to figure out how they worked; as it turned out, they declared the same variables at the top of each function in the same order. They didn't have globals, they weren't passing values around: the stack was being allocated across the same memory for each function, so the variables "just worked."
    - tcas 5y ago
      I had the same experience when I was a TA a long time ago. Reviewing the code to a homework set I noticed that two students mixed up the naming of two variables (I think min/max were switched). I ran a whitespace sensitive diff and noticed the only difference between the two files was the author name in the header. The professor sent a sternly worded letter to the class about not cheating, and nothing else came from it AFAIK.
  - saltminer 5y ago
    In my experience, the people who get caught cheating (not necessarily the ones who get punished for it, of course) are usually the ones who don't understand the code to begin with or how they might go about creating their own solution. These people also oftentimes came to us and just openly admitted they copied code they found online and wanted us to check over it before they submitted it. I never said anything about the accuracy of their code, but I was willing to explain how it worked so they could decide if they thought it was accurate. Most did not take me up on that offer, instead opting instead to bug people in their class until they found someone a) smart enough to help on assignments and b) dumb enough to help them. They didn't care about learning how their code worked or why, they just wanted an easy A. The few who did take me up on my offer tended to be people who didn't understand the assignment to begin with and, after explaining the problem and how their solution worked, went out and did their own work. I always enjoyed those ones, they tended to want to do things legit but either were too nervous to go the professors/TAs or couldn't make office hours and couldn't get timely answers over email. The people who just didn't care I was more than happy to talk about at at our weekly meetings. If their TAs weren't also tutors, our supervisor would keep them updated on who came in asking for a thumbs up on copied code.

deleted 5y ago

[deleted]

saltminer 5y ago

Back when I worked as a tutor, we knew a lot about the professors since most of us were also TAs at some point or worked as TAs concurrently. Some were consistent in busting people for cheating, others tried to avoid it at all costs (because they based their self-worth on their Rate My Professor page), but a few were just capricious and arbitrary. On their good side? "Eh, everyone uses Stack Overflow [or forgets to do anything to hide their plagiarism, not even bothering to edit the author name Javadoc comment on the code they copied] every now and then." On their bad side? "Copying others' work is unacceptable, you can either take an F in the course or plead your case to Academic Integrity." Of course, the ones who showed favoritism were also the ones who practically printed grant money, so nothing ever happened while I was there (and I doubt anything ever will).

downrightmike 5y ago
With code, as long as it works, so what. Plus learning a language requires copying to learn how to do it correctly. Would you want to be required to be completely original learning French? It makes no sense to burn people for doing what it took industry decades to figure out.
- CountHackulus 5y ago
  Because the goal of the assignment isn't to write code, it's to learn what code to write. If you're copy and pasting from someone else you're potentially skipping out on a lot of learning. Granted, good luck passing the exam with copy and paste, but I've seen someone do basically that for 5 years, don't know if they ever graduated but they were grinding it out.
- macintux 5y ago
  > With code, as long as it works, so what. Working as a lab instructor a lifetime ago, I graded two students' C assignments that both worked (mostly) but clearly without understanding what was going on. It took me a while to figure out how they worked; as it turned out, they declared the same variables at the top of each function in the same order. They didn't have globals, they weren't passing values around: the stack was being allocated across the same memory for each function, so the variables "just worked."
  - tcas 5y ago
    I had the same experience when I was a TA a long time ago. Reviewing the code to a homework set I noticed that two students mixed up the naming of two variables (I think min/max were switched). I ran a whitespace sensitive diff and noticed the only difference between the two files was the author name in the header. The professor sent a sternly worded letter to the class about not cheating, and nothing else came from it AFAIK.
- saltminer 5y ago
  In my experience, the people who get caught cheating (not necessarily the ones who get punished for it, of course) are usually the ones who don't understand the code to begin with or how they might go about creating their own solution. These people also oftentimes came to us and just openly admitted they copied code they found online and wanted us to check over it before they submitted it. I never said anything about the accuracy of their code, but I was willing to explain how it worked so they could decide if they thought it was accurate. Most did not take me up on that offer, instead opting instead to bug people in their class until they found someone a) smart enough to help on assignments and b) dumb enough to help them. They didn't care about learning how their code worked or why, they just wanted an easy A. The few who did take me up on my offer tended to be people who didn't understand the assignment to begin with and, after explaining the problem and how their solution worked, went out and did their own work. I always enjoyed those ones, they tended to want to do things legit but either were too nervous to go the professors/TAs or couldn't make office hours and couldn't get timely answers over email. The people who just didn't care I was more than happy to talk about at at our weekly meetings. If their TAs weren't also tutors, our supervisor would keep them updated on who came in asking for a thumbs up on copied code.