• candyman337@sh.itjust.works
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    3 years ago

    I understand cheating is shitty but it would make a lot more sense for the teacher to make this a teachable moment about cheating, and to promote collaborative solutions, but also checking work you get from others.

    A huge part of development is copying code and reusing code from libraries. The important part is that you know how the code you copy works.

    • funkless_eck@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      3 years ago

      universities take plagiarism very seriously. Friend of mine teaches stage craft (how to make sets, props, costumes, lighting and sound design/planning/execution/engineering)

      First semester, first test, easy pass: Someone pokes their head into the class and my friend goes to the door to answer them, stepping outside for like ~30 seconds

      comes to mark the papers:

      “In a proscenium theater, what is the very front of the stage called?”

      Real answer: apron

      55% of the student answers: the same made up word that sounded vaguely Portuguese with no hits on Google.

      even though it’s super dumb and super easy and barely matters at all and is a one word answer to a basic question - the students ended up being investigated by the university and my friend had all his classes audited.

  • randomaside@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    1
    ·
    3 years ago

    Cheating in academia is the name of the game. There is a survivor bias here assuming the other 78 students didn’t cheat. They’re Learning how to not get caught. Building a better trap may simply yield a better better cheater. The proof ends up being in the work.

    I still think honeypots are amusing AF.