Some of it was so silly that I was accused of cheating in the C course for using and citing the hashtable implementation from the assigned textbook. On just talking to the graders and professor, they dropped it and were amused that anyone used the book.
For the other sciences, they would shake up the rules on how to capitalize figures. Idea being that cheaters would use last year's rules. Or, lazy people would just not pay attention..
It wasn't really overblown, it was a problem with that course. The instructors and TAs were grossly unprepared to teach hundreds of freshman a semester in a language they (the instructors and TAs) weren't familiar with that was fundamentally harder (especially for an arbitrary student rather than those actually interested in the topic) than what was done before.
The rest of my comment was about appropriateness of the first course to the students and their objectives. MATLAB being a much better first language for the engineering majors than the general CS requirement provided.
So, yes. They had evidence of massive cheating on a level they had never seen. They also had evidence of near incompetence in teaching at a rate never seen before. Not shockingly, they focused on the cheating.
My assertion is that the behavior in the cs students was no different from any other students. They just had more mechanical grading schemes and were less prepared to teach such a variety of students.
Edit: and apologies for skipping the Matlab assertion. As an EE at the time, that was my intro. I don't recall it being particularly good. Or bad. It just was. They shifted to java soon for many folks. As someone that was a TA for the Java classes. Then the VHDL classes. Then the C classes. I can't really see any benefit of any one over the others.
Though I couldn’t read the full article, but that’s what it seemed to say in the first two paragraphs.
There seems to be two slashdot threads discussing the issue from 2002. Perhaps it was worse after you left?
[1] https://www.chronicle.com/article/georgia-tech-concludes-che...
Rather, a lot of what they classify as cheating in that time was stupid close to standard practice for sorority and fraternity members. Having banks of previous years tests and assignments, for example. (I say this as someone that was not in one, so mayhap I am misrepresenting.)
So, my request for hard evidence is mainly to get to a root cause and to establish norms and base rates of behaviors. Yes, it could have gotten worse or had some bad years. It feels highly suspicious that it just happened to correspond with the rust of automated graders. Yes, coincidences happen. Feels really shaky, though.
As of 2016, CS1301 was still in Python. CS1331 was in Java. MATLAB was present either in specialized CS classes (like computer vision) or in the Intro To CS for Engineers (CS1371). Not aware if it remained this way afterwards though.
At the same time they had the Scheme-based course (and possibly before, but I know at this point) they also offered a MATLAB-based introduction for non-CS/CMPE/EE students (EE and CMPE had to take the first 2 or 3, respectively, CS courses with the CS majors as part of their degree program). This MATLAB course was targeted more towards ME, AE and other majors who really just needed something that let them write programs to solve problems in their domain. Many of them did much better. The problems assigned were better motivated for them and they were able to apply it within their broader course of study or internships or research work.
That a first course should be appropriate to the desired outcome for the students seems obvious, I'm rather surprised there's much debate around this topic.