‹ BackHN Continuity

Thread

CS240 AI Cheating Retrospective

120 points · 104 comments · ArchAndStarch

  1. aenigmaclamo · · focus · HN ↗

      * Do not use variable length array in this class
      * Some of are you are copying code and concepts from things outside of course material
         * `fgetc()`, `sizeof()`, `malloc()`, etc
         * You're probably cheating.
         * You're also making your life more difficult
    
    I always found these sorts of instructions quite frustrating as a student. If I'm a student enthusiastic about learning a language, I would have definitely been one of the kids trying to figure out how to use malloc and creating novel approaches to the projects that are assigned to me. It's a university class, why the hell not? Besides, isn't that going to be an advantage towards me considering the code is going to be evaluated by a anti cheat engine?

    The AI stuff aside, this comes across as a professor who feels threatened when his course isn't taken as doctrine. Being called a cheater for using external resources is ridiculous to me.

    1. broodbucket · · focus · HN ↗
      My professor in a C course said anyone that uses `goto` gets failed. It was quite liberating for me to then end up writing `goto`s for a living
      1. OkayPhysicist · · focus · HN ↗
        Are you so graybeard that structured programming was interesting enough to be part of the focus of a C course? Because I can see in that context requiring the use of appropriate control flow structures. Nowadays, I can't imagine in what context students would be so eager to reach for GOTO that they don't preferentially use other control structures.
        1. broodbucket · · focus · HN ↗
          This was in...2013? I think the main point was just to stop students from footgunning themselves
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.