Slashdot Mirror
Georgia Tech Cracks Down on Learning
The Washington Post has an article today on a Georgia Tech student who almost flunked his intro to comp sci course for just discussing his homework with someone else. Note that no one including the faculty accused him of actually copying any code from anyone. However, the "honor code" at Georgia Tech "forbids its introductory computer science students from seeking any help from other students on their homework." The faculty recorded part of his violation on the forms as "He was trying to learn it." This is something that high school seniors might want to keep in mind when selecting which university to attend.
...it's for drinking, partying, having casual sex and possibly absusing some illegal substances.
It must be true, popular culture says so.
STOP MISUSING APOSTROPHES, YOU MORONS!!!
Rigid "honor codes" lead to ridiculous situations. I am reminded of a story from a friend who went to Davidson, where someone she knew was disciplined for honor code violations after taking an extra can of soda that a machine mistakenly dispensed. A true honor code should be flexible. Otherwise, what is the point? Everyone knows what they are supposed to do when the rules are cut-and-dry, the purpose of an honor code should be to foster honorable/moral behavior in situations the rules do not cover.
[quote]
A brand-new rule says a computer science student is wrong to try to seek answers to questions ANYWHERE other than from course materials or Georgia Tech staff
[/quote]
An exam is one thing, homework is another. Homework is supposed to reinforce the skills you'll need later. One of those skills is research.
How To Be An Incompetent Engineer 101...
I would send the following mail:
To whom it may concern,
I would like to apologize for my behavior. It was wrong and immoral. I suppose, because of my youth, that I thought it would be justifiable to learn. I now see otherwise, and hope to discontinue this behavior for the rest of my career.
I thought that it might be a good dodge to spend some of my time in first year learning, and that it might be an investment towards my GPA for me to acquire knowledge from other human beings. Oh well, I guess we all learn our lessons of life somehow. I understand that in discussing in an academic forum setting is wrong and I promise that for the endurement of my University career, I will absolve any attempt at communicating with my peers, as it seems to only decrement my academic standpoint and tarnish the reputation of the University, as well as compromising the institution of Education on the whole.
I promise I will avoid learning for the rest of my college career and rely only on myself and my own experiences with the natural environment to do so. Furthermore, I resolve to lock myself in my room for the remainder of the semester in hopes that social interaction will not tempt me into deteriorating my Computer Studies goals. As well, I will avoid going to lectures and tutorials, as well as any open labs, since the professors and TAs may accidentally teach me something, in which case I will compromise the goals the University seems to have set forth.
Sincerely,
****
Glad to know open academic forums (What Universities are intended to be) are still just that.
Karma: Non-Heinous
wouldn't it be good to wait until we hear the school's side of the story? It is very easy to claim that you were only trying to learn the course material, but with only a single quote -- which was certainly taken out of context -- to indicate the school's view on the situation, it is hardly fair to weigh in on either side.
Tarsnap: Online backups for the truly paranoid
I go to Georgia Tech. Yes, the student was accused of cheating. Yes, this is because he was caught cheating. Yes, the article states this, and then goes on to tell how it's "not that bad." Whoever wrote this summary of the article needs to brush up on their reading comprehension skills.
As for what happened to the student....He had a substantial amount of code (probably around 30 lines) that was verbatim with another student. As the article says, he should have not turned it in and lost the 2% instead of cheating. He can't handle responsibility for his actions so he and his dad pitch a fit and blame it on the college of computing.
Tech may not be the top CS school, but I think our program is pretty good, and their strictness when it comes to cheating only adds credence to the degree you get when you graduate from the Computer Science department. The strictness is not a reason to avoid this school, but a reason to come here.
For the bonehead award, Programming I was basically just Pascal on personal computers. Well, I had gotten into "trouble" for not commenting my source code. So, for my final program, I wrote it in Pascal, compiled, disassembled, rewrote the assembler code to Pascal inline assembly statements, and lined up the original Pascal as the assembly inline comments. My prof wasn't amused.
But, on the other end, I took another programming course which was supposed to be COBOL, c, and FORTRAN. The first day, the prof said that we will not need our FORTRAN book and would not write any FORTRAN programs or be tested on FORTRAN. However, we were instructed to learn FORTRAN on our own. Well, almost no one kept their FORTRAN book or even bothered learning FORTRAN. I was lucky enough to have already learned most FORTRAN working on physics stuff. Our final program was to write a source converter in c to convert FORTRAN programs to c. Not only did we have to know FORTRAN, but we had to KNOW FORTRAN!
Click here or here.
And the CS13xx courses have newsgroups for asking questions and have tons of TAs. There are recitations and labs and office hours. There is plenty of a chance for students to ask for help and get help. Unfortunately, too many students are lazy bastards and don't want to put forth the effort of doing the assignment honestly and getting help when they need it.
My god, this sounds like something I was ranting about earlier today. %90 of the people in my final class from my CS major couldn't write a few lines of code to save their lives. We are doing the whole final project in C# (project requirements, not our choice). Being a programming class, and being that it is the capstone of the major, you'd think that the people would take the time to at least look at the language right? Wrong. I've written the entire project so far. They don't even have a clue how the code works.
On the bright side, I did get them to do all of the documentation for the project but still....it really scares me how many technically inept people are graduating along with me in my major. On the other hand, it made it a lot easier for me to score the job that I have =)
Most of you are misinterpriting the idea behind this type of rule. Yes, in the real world collaboration is increadably important, infact it is so important that we actually take classes in software design where the entire class is in groups. Learning how to interact with people and function in teams, methods of interaction and teamwork, dealing with problem members and managment, these are REQUIRED classes, and yes, groupwork is a required part of them. We even cover different philosophies of team interaction, the ancient methods and new concepts such as Extreme Programing. However, these rules are for the very begining, we are talking CS1 and 2 here, collaboration is not permitted. Yes, when I was taking the classes, I complained about the very constraining rules, and I did say that "In the real world, collaboration (and while I'm at it, not re-inventing the wheel) is important." However, it is also important to learn the basics yourself. Everyone in the entire university must take CS1 and most CS2, these are just intro programing classes to get people familure with coding and thinking on there own. That is their point, and to accomplish that, they must seperate the students out. Some of the strictness is misunderstood. The java API is not looked down upon, we are told to print it out and sleep with it under our pillows, to use it so much that by the end of the year it looks a bit the something from the 12th century. Granted that is in jest, but the point is, documentation, man pages, that type of stuff is encouraged. It is just the first few classes need to focus on the individual, not the team. You must first build yourself before you can build on yourself, and in order to assure that, rules must be in place. The CS majors know, or eventually realize once they reach the 2000 and above CS classes, that they benifitted from the artificial division. Maybe they knew everything going into CS1 and 2, but now all (or most) of their peers are strong on their own. So when it comes time to work together, each programmer could stand on their own, but together their skill is greater than the collective sum. In addition, it goes to teach the true value of working together, they know first hand how hard it can be to stand alone. Maybe it is difficult to see looking in, but there is a good concept behind the rules. Yes, they might not need to be there if everyone was honest, but unfortunately this is not a perfect world, and the restrictive environment helps in the long run.
I'm a graduate student in CS at Georgia Tech, and I recently graduated from their undergraduate program.
Georgia Tech is in no way against teamwork. In fact, in many LATER courses, it is not only encouraged, but required to pass. In the introductory course, however, students are expected receive a firm foundation in the BASICS of programming and computer science like recursion, searching, sorting, algorithmic complexity, data structures, trees, graphs, etc. If a student cheats his way through ANY of these concepts, and expects to survive a later computer science course, he will not only damage his own grade, but the grade of his teammates as well.
I'd also like to point out a couple things either pushed aside or conveniently not mentioned in the article. First, the student in question was NOT accused of discussing his assignment with another student. To my knowledge, regular discussion of assignments is a very commonplace occurrence--especially on the four newsgroups available for the class. He was accused for CHEATING. No cheatfinder, however good, is going to find out if people DISCUSSED anything. It's only going to find people who have VERY similar, copied, code. Secondly, I'd like to mention that the person in question is also, apparently, the son of a Washington Post editor.
I found a copy of the course-specific honor code here. Here's the relevant excerpt:
It actually looks pretty reasonable. I'd like to direct people's attention particularly to the last "good guideline" sentence. Now, what did the student do? From the original story:
Now, "chatting" is obviously vague; there's a big difference between "what are they asking us to do" and "how do we do it". However, it doesn't matter. According to the "good guideline" in the honor code, the student would be in the right even if he discussed answers with the other student, so long as neither was looking at or copying from the other's actual code and both could explain independently how their solution worked. If anything, the honor-code standard as stated in the referenced link seems a little too lenient to me.
It's entirely possible that the student did something more egregious than what's mentioned in the article. It's also entirely possible that someone's being a little overzealous about enforcing their own interpretation of what is really a pretty lenient standard. Assuming either to be the case would be premature, based on the information available. All of the political rhetoric, on either side, seems just a little bit misguided in the absence of anything but the most fragmentary and incomplete information.
Slashdot - News for Herds. Stuff that Splatters.
I find it interesting you refer to 30 lines as a substantial amount of code. The article suggests the program was a rather large one, and that 30 lines was a small fraction of the overall code. My own computer science experience in the past suggests 30 lines probably was a teeny fraction of the code.
Of course, the pureist will say, copying is copying, and even if it was 2 lines that's cheating. The problem is I see no proof he copied from another student. You may scoff, how else would the code be the same, well, that's easy.
I remember more than a few times sitting in the lab working next to 5-10 of my classmates. A common activity was to repeat the problem to each other to be sure we understood it. "The assignment said the program should output the data in sorted order case insensitive, one on a line, right?" "Yes." That's not cheating. Then someone else might pipe up "Didn't the GTA give us a handout with a sorting example on it?" "Yes," another would pipe up, and a third would produce the class handout for all to read. Again, no cheating yet. Of course the GTA example was case sensitive, so it had to be changed to be case insensitive. It also worked on plain strings, and the data was stored in structures (which were all remarkably similar due to a similar process) so that change had to be made as well. Those two changes were done independantly.
In this case I proport no cheating has happened. Students conversations were limited to the problem statement, not the solution. Materials "shared" by the students were class handouts that all had, although perhaps not at that moment. The probability code ended up the same, high. Identical, moderate.
Several times after assignments were returned to us (graded et all, even after the course) I would then compare with a friend to see how to do the things I got marked down on, and vice versa. Several times I found whole functions that were only a few characters off of being identical, even though we never colaberated at all. Everyone uses x, p, i. "print_sorted_output" is a common function name choice. Add to the copied GTA (course) suppied code and you get a lot of similar programs.
We don't have enough facts to determine if this student is guilty or innocent. The fact that 30 lines are roughly the same, or even identical does not, in my mind, prove he cheated. There must be other evidence to help lead us to that conclusion.
As for Georgia Tech, there is a root problem here. They have a separate computer science college,so it's hard to tell where they fit. Most schools put computer education in the College of Arts and Science, or in the College of Engineering. This is important. If you look at other Arts and Sciences, students are encouraged to work together. If you are majoring in dance, and another student views your "final project" (a dance, of course) and suggests "hold your chin up higher while you spin" that's not considered cheating on your homework. If you write a book, and let another student read it before turning it in, and they say "you should be more emphatic in chapter 2" that's not cheating. On the other hand engineering has right and wrong answers. If you show someone your calculations on the load capacity of a beam for homework that's cheating.
So what is CS? Is it a creative discipline, like dance, or painting, or writing? If so the root of improvement is working together, public performance, peer review. On the other hand, is it a hard science. There is a "right" program, and everyone should get the "same" answer, so any sharing would help a student leap to a conclusion without doing the work?
I was in several classes in which work was assigned to "development teams" of 4 or 5 students. We were expected to hold "development meetings" and discuss "development strategies" whilst constructing the piece of software we'd been told to create.
A noble idea, right? Work together, just like in the real world? Get help from your peers, everyone does their share, all that happy horseshit?
Did it ever work that way for anyone? The smart kids in the group (if there were any) ended up doing all the work. The stupid kids hung around for one or two meetings and maybe sent off the occasional email asking when the next meeting was, but never contributed line one of code. The worst part came at the end of the semester, when we were all asked to rate our fellow teammates. What can you say? "This stupid retard was too busy fucking around and getting drunk to write any code, and when we asked him to debug this function, he sent it back exactly the way he received it"? Well, you can, but it doesn't seem to matter, as everyone always got the same grade.
Come to think of it, group work is exactly like working in the real world, because it's full of people who don't do jack shit and make you wonder why they're still hanging around like a festering boil on an unwashed butt cheek. Honestly, I don't know how some kids in my class got their degree.
- A.P.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
The bit about a new policy saying students will not being allowed to look for answers anywhere other than course material or Georgia Tech staff?! That's what research and learning is all about: using any resource available to you. This doesn't directly map to plagiarism and cheating. For example, using an alternate text book often helps more clearly understand a concept not well explained in the assigned text. Lastly, how on earth did they manage to write down "He was trying to learn it" in any context that makes sense?
I hope you're not pretending to be evil while secretly being good. That would be dishonest.
Write a java applet that does x with y functions using a hashtable. You can consult any paper materials you have on your person. No talking to anyone in the classroom except the teacher. You have an hour.
In my CS courses, tests in this format are given all the time. The Chairman of the TCU CS Department, Dr. Richard Rinewalt, has been head judge of the ACM programming contest-THAT programming contest-for several years. He supports this format and knows that it works. I believe it's reasonable to trust what he is doing.
They were *not* cracking down on cheating.
a computer science student is wrong to try to seek answers to questions ANYWHERE other than from course materials or Georgia Tech staff. Rooting around in old books in the library, checking the Internet, calling your cousin at Caltech--all are forbidden.
If you research a problem outside the "official" materials you are flunked. I'm sorry, but reading Knuth's The Art of Computer Programming on your own shouldn't ever be used to flunk you from a required freshman CS class. Yet at Georgia Tech, it is against the rules!
What the student did in this case was against the academic rules for the course. Now it's possible, even probably, that those rules are arbitrary and unfair, but what he did violated them.
I repeat, its not cheating to read another textbook. Its *not* cheating to say, "I can't make my doubly linked list work because I don't understand C pointers. Can anybody explain C pointers so that even I can understand?" My God, they seriously listed part of the freshman's offense in exactly these words: "He was trying to learn it."
However, it is also important to learn the basics yourself. Everyone in the entire university must take CS1 and most CS2, these are just intro programing classes to get people familure with coding and thinking on there own. That is their point, and to accomplish that, they must seperate the students out.
... there is also an LAS compsci program which I know little about). These rankings change from year to year (and source to source), so I don't know where the U of I stands currently, but I'd be surprised if it had slipped all that much.
... reinforcing the very lessons they are to be learning. And if you choose to be a lazy bastard and let someone else do all the work, then try to rewrite it so that it is sufficiently different, you'll either learn despite yourself, or screw it up sufficiently to get the grade your laziness has earned you.
... so there is a disincentive for people to be too free with their solutions built in. In short, the complexity and demands of the assignments coupled with the grading model (bell curve), and a systematic check for plagorism, were sufficient to prevent and punish cheating without resorting to draconian absurdities such as disallowing any discussion of assignments amongst students.
What utter nonsense. Please keep in mind that you are being taught that your University is right and its critics are wrong in each lecture you attend, if not overtly, then certainly on a subliminal level.
I attended the University of Illinois at a time when it was considered the 2nd or 3rd best university for computer science (Engineering College
In any event, that particular university had an impeachable reputation in computer science. They never had such an asinine rule that students could not discuss the subject and their homework assignments amongst themselves. Not only would such a rule have been unenforcable, or led to the kind of absurdities you are defending here, but it would have precluded one of the most important facets of education, through which people learn any subject, at any level, rudimentary freshman level through advanced post-doctorate: studying, discussing, and digesting the material.
Instead, the homework assignments were made to be sufficiently challenging that, even if you were to collaborate with others, you would learn the material and your grade would reflect how well you learned it. Keep in mind if your work resembles another's too closely you'll get nailed for cheating, so even if several people solved the problem together they'd essentially have to reimpliment it differently from one another
Then there is the bell curve to contend with
Georgia Tech is simply wrong on all counts, and probably too arrogant to recognize and fix the real problem, which isn't their students, but their approach to education.
Maybe it is difficult to see looking in, but there is a good concept behind the rules. Yes, they might not need to be there if everyone was honest, but unfortunately this is not a perfect world, and the restrictive environment helps in the long run.
Now it becomes clear what Georgia Tech is teaching its students. Obedience, and the sublimation of one's intellect to the authority of others, without question. The fact that you would write something like that with a straight face (and for your sake, I truly hope this was a clever troll and not meant in earnestness) is indicitive of the kind of education you are receiving at your university.
I humbly suggest you start shopping around for a more sensible university to transfer to, one that concentrates on teaching science and technology rather than obedience.
The Future of Human Evolution: Autonomy