Slashdot Mirror


Student Who Released Code From Assignments Accused of Cheating

Death Metal sends in a story about Kyle Brady, a computer science major at San Jose State University, who recently ran into trouble over publishing the source code to his programming assignments after their due dates. One of Brady's professors contacted him and threatened to fail him if he did not take down the code. Brady took the matter to the Computer Science Department Chair, who consulted with others and decided that releasing the code was not an ethical violation. Quoting Cory Doctorow at Boing Boing: "There's a lot of meat on the bones of this story. The most important lesson from it for me is that students want to produce meaningful output from their course-assignments, things that have intrinsic value apart from their usefulness for assessing their progress in the course. Profs — including me, at times — fall into the lazy trap of wanting to assign rotework that can be endlessly recycled as work for new students, a model that fails when the students treat their work as useful in and of itself and therefore worthy of making public for their peers and other interested parties who find them through search results, links, etc. But the convenience of profs must be secondary to the pedagogical value of the university experience — especially now, with universities ratcheting up their tuition fees and trying to justify an education that can put students into debt for the majority of their working lives."

10 of 333 comments (clear)

  1. Teachers wrong here by XPeter · · Score: 5, Interesting

    The student released the source after the release date, which prevented any of his peers from cheating. In the computer science classes that I take, it's allowed to share the source code for your assignments as long as it isn't for a pending assignment and/or test.

    The only reason that comes to mind for the teacher wanting the code to be taken down is because he was going to use the same assignments next year (Which is fairly common among teachers). Regardless, in this case it's his code and he has the right to do whatever he wants with it.

    Unfortunately schools have become more about preparing you for standardized tests and such rather than giving you a real education with the information you actually will use in life (Which is why teachers always have to cover their asses). What Brady was trying to do was help his peers and kudos to him for doing so.

    --
    "The difference between genius and stupidity is that genius has it's limits" - Albert Einstein
    1. Re:Teachers wrong here by think_nix · · Score: 5, Interesting

      The only reason that comes to mind for the teacher wanting the code to be taken down is because he was going to use the same assignments next year (Which is fairly common among teachers). Regardless, in this case it's his code and he has the right to do whatever he wants with it.

      Unfortunately schools have become more about preparing you for standardized tests and such rather than giving you a real education with the information you actually will use in life (Which is why teachers always have to cover their asses). What Brady was trying to do was help his peers and kudos to him for doing so.

      +1 to that . I think (some not all ) educators need to get off there high horses and start being more innovative. Instead of always re-running assignment X for the past 5 years.

      I remember a certain "educator" I had while I was going back to school in 2001. If I didnt code the way he saw fit (which in other terms) a way he could understand he would would fail me , code comments or no code comments. In the end it went up in front of the school Directors , and I had my current employer at the time backing me with some other clients that I was coding for , because otherwise I would have failed out. Luckily the board decided in my favor .

      These certain types of educators that dont understand the depths of the own things they are "teaching" should either A.) be more innovative and come to terms with newer techs and their way of teaching or teaching style. B.) count their losses stfu and find a new line of work.

    2. Re:Teachers wrong here by Jurily · · Score: 4, Interesting

      In the computer science classes that I take, it's allowed to share the source code for your assignments as long as it isn't for a pending assignment and/or test.

      One of my teachers had a different approach: he'd let you do anything, as long as you were clear on what you wrote yourself, and what you didn't. OTOH, if he found the same snippet of code in two different assignments and both students tried to take credit for it, both failed.

      None of us dared use large chunks of someone elses work.

    3. Re:Teachers wrong here by nietpiet · · Score: 4, Interesting
      > Regardless, in this case it's his code and he has the right to do whatever he wants with it.

      This is probably not the case. At my University they own the rights to all code that is written as part of the educational program, not the students.

    4. Re:Teachers wrong here by natet · · Score: 4, Interesting

      Good profs at the very least work on a 4 semester rotation of courses where you're going to have to dig up a student from a few years ago at least before you have an easy "tweak and resubmit" assignment. Any instructor that dishes out the exact same projects semester after semester isn't showing any commitment, and certainly isn't staying with the times. Computer science is in such a continuous state of flux that any prof that isn't consistently reworking their coursework isn't doing their job.

      Depends on the school. I'm and adjunct professor at a local satellite campus, and I teach the same class every year. The topic is data structures, and not a lot changes year over year when you're talking about something so fundamental. I have changed my curriculum each year, but only because I have yet to find a book that I feel really treats the topic well. Each book has some high points and some glaring low points, but I dream of the day when my lectures actually become somewhat static. I spend way too much time tweaking my lecture notes.

      Also, you don't seem to have considered that in some courses, each programming assignment builds on the one before. By posting his assignments, even after the due dates, he may be influencing his fellow students in the follow on assignments.

      --
      IANAL... But I play one on /.
    5. Re:Teachers wrong here by Attila+the+Bun · · Score: 5, Interesting

      This is a lazy instructor working to maintain his laziness.

      Do not underestimate the work involved in preparing a new course. I teach for a few weeks every year, and can easily spend several days preparing a new one-hour lesson. Even recycled material needs updating and revising, and the preparation time is at least equal to the teaching time. Think of the time you spend to prepare a presentation at work. Now imagine spending your whole working day giving presentations, and doing the preparation in the evenings.

      Teaching is a tough job, and only those who believe it's important stick at it. Some teachers are more talented than others, but I've yet to meet a lazy one. A lazy teacher will quickly move to an easier (and better paying) job.

  2. Problem Solved Many Years Ago by eldavojohn · · Score: 5, Interesting

    When I did my undergrad at the University of Minnesota in 2000, they let us know that they took our code that we submitted and stored it in a program with a database. Whenever a student submitted new code, it went through this program. Essentially, some really fancy Hamming Distance that I think might have been similar to FASTA or BLAST algorithms for genetics were employed to score assignments against all the other ones.

    If it was common for students to write assignments -- say they had been given a design template -- then all of the scores would come back rather high. If the TA noticed an outlier, they would investigate. If two submissions came up sufficiently similar, they would investigate.

    It was (of course) never explained in detail how it worked but I bet that today one could take this to many new levels with things like ANTLR that might allow the program to check the inherent structure in code to avoid something trivial like different comments or variable names skewing the results.

    Was it me who was in the professor's situation, I would bite the bullet and code the very basic above application using a web form submission for TAs and Professors. Then I would ask for help from other members of the department and make it a customizable growing project to protect the academic integrity of my school and students. Then I myself would put the opened source on there and run all my students assignments against it.

    Problem solved, you can keep all your assignments static, you lazy bastards :)

    --
    My work here is dung.
  3. FIRST! And welcome to fraternity file cabinets by Antique+Geekmeister · · Score: 5, Interesting

    FIRST POST!! Oh, dear, you must have all had a good Friday night.

    There's an old practice of fraternities at my college, where they kept file cabinets filled with old homework and course notes of all the classes their members took. I had wondered how some frat boys coasted through so many classes and got so much more sleep than those of us who struggled working to pay for college, paying for food, etc. Then I found out this was one of their most important reasons. It was a known practice, and one of the less publicly mentioned benefits of joining a fraternity.

    Since small-scale publication of old hoomework and course notes, such as what I describe above, has been going on for centuries, it seems completely reasonable that larger scale publication be permitted.

    1. Re:FIRST! And welcome to fraternity file cabinets by Cor-cor · · Score: 4, Interesting

      My fraternity actually used to do this and we've all but stopped now since nobody uses it. The reason is that nearly all of our classes have started posting old exams, answer keys, course notes, and a few of the good teachers will even post past homework. Most classes also have homework weighted pretty lightly so that learning the material (as tested on the exams) is what really matters. With this setup, past homework of course can't be used for cheating, but sometimes seeing something worked out will help make a connection you might not have otherwise and past exams really help take away the horrible feeling of not knowing if you're prepared for a test or not. I will agree with previous posters that if students are able to use past resources to cheat, this is more the fault of a lazy professor than anything.

      Also, back when we did keep study files, it was an "advertised" benefit of joining the house, not swept under the rug as you seem to describe. As far as I know, no one at the university ever had a problem with us or any other house/organization/random group of friends doing it. Now we mainly focus on the fact that we've got older members from a wide array of majors who are willing to help out younger members as needed.

  4. The Real Deal: Licensing for Schoolwork by betasam · · Score: 4, Interesting

    The specific case (covered heavily - check Techdirt for one) in question has actually brought in a much larger problem to light. How should students treat code written as part of assignments or as part of their course-work in terms of licensing? Is there a precedent for licensing? Most research activities conducted by universities have already adopted licensing framework. Here's an example. There has been debate whether such licensing should be free. Just check Medical Research and you can open Pandora's box. One more example is Singapore's A-Star which is more of a group focused on preparing research for industry adoption including licensing and legal usage terms.

    How about code released in books on Data Structures, Algorithms, Fundamental C programming? To my knowledge (do correct me if I am wrong), the code is usually licensed under the same copyright notice as the book itself. In some cases, the author changes this licensing and makes it available. One example is "Numerical Recipes in C" where the licensing terms of the code from the author(s) of the book is explicit and can be found on a google search.

    When it comes to university assignments, it is no news that the same template (if not the same course material itself) tends to get recirculated over a periodic basis. In some cases this period is annual and in others, the frequency is different. The debate raised is ages old. For most data structure or standard assignments of programming, you could find most of the code online. You could use this as a starting point or choose to write your own and learn your fundamentals. That's up to the student and the professor who is teaching and grading.

    There is some truth in the statement (IMHO) that the Academia is shielded from the real commercial world. It works positive in some cases and is counterproductive in fields like Engineering (not Theoretical Computer Science.) In this specific case, if the University were to read all the fine print they have on students sharing course material (for which they pay for) and lecture notes and assignments, they would find the right solution. Bringing this (issue between a student and the professor) out to Open forums seems more of a publicity stunt that is going to get someone infamous for some and noticeable for a few others.

    Focusing on the larger issue, a Varsity must be clear on how course-work and assignments from the students will be licensed and treated. They already have set legal precedents for most research work (which in some cases is funded by commercial bodies.) Hopefully this issue raises a flag and lets varsities understand and embrace Open Source, encourage students to use it particularly in programming assignments. At the very least they should at least reserve procedures to let a student obtain due permission for displaying his/her works online under appropriate licensing. In the absence of a precedent and clear guidelines, such confusion and unnecessary nerve wracking experiences between a Professor and a Student are more likely to surface. I hope not.

    --
    No Greater Friend, No Greater Enemy! (Lucius Cornelius Sulla)