Why Computer Science Students Cheat

alphadogg writes "Enrollment in undergraduate computer science courses is at an all-time high at colleges nationwide. But this trend that's been hailed by the US tech industry has a dark side: a disproportionate number of students taking these courses are caught cheating. More students are caught cheating in introductory computer science courses than in any other course on campus, thanks to automated tools that professors use to detect unauthorized code reuse, excessive collaboration, and other forbidden ways of completing homework assignments. Computer science professors say their students are not more dishonest than students in other fields; they're just more likely to get caught because software is available to check for plagiarism. 'The truth is that on every campus, a large proportion of the reported cases of academic dishonesty come from introductory computer science courses, and the reason is totally obvious: we use automated tools to detect plagiarism,' explains Professor Ed Lazowska, chair of computer science and engineering at the University of Washington. 'We compare against other student submissions, and we compare against previous student submissions and against code that may be on the Web. These tools flag suspicious cases, which are then manually examined.'"

Comments

How many ways are there to do simple things?

[nebaz]

If someone asked me to (in Java say) print the numbers from 1 to 10, I would probably do something like

for (int i=1;i=10;i++) {
    System.out.println(i);
}

So would most other people. Would this flag me as a cheater?

Re:How many ways are there to do simple things?

[keithpreston]

This would be flagged but wouldn't pass the manual review. As a former Graduate Teaching Assistant, cheaters are easy to spot because they are LAZY! They turn in the exact same files (same comments with same misspellings) with maybe a different name at the top. The only good way to cheat is to make sure every things is perfectly correct and has no identifying characteristics.

Re:How many ways are there to do simple things?

[TitusC3v5]

If the person you copied it from also mistakenly used an assignment operator instead of a conditional, then yes. :)

Re:How many ways are there to do simple things?

[fucket]

for (indexnt index=1;index=10;index++) { System.out.prindexntln(index); }

Re:How many ways are there to do simple things?

[CorporateSuit]

What are these unneccesssary scribblings you're adding to your code? This is a job for a single line:

System.out.println("12345678910");

Re:How many ways are there to do simple things?

[VGPowerlord]

System.out.prindexntln

I laughed when I saw this.

Re:How many ways are there to do simple things?

[adwarf]

Other signs of cheating: When you get a student that does A+ work on programming assignments, but fails the exam (not always the case, but usually). Another sure sign is when they turned in two or three sub par programming assignments and then turn in a beautiful program using concepts that haven't been taught yet. Also once you suspect them it is easy to verify. They can either explain the code or they can't, if they can explain it maybe they cheated, but at least they spent the time to learn what the code does, although I never saw this when I was grading work.

Re:How many ways are there to do simple things?

[Normal Dan]

I have a similar question,
If someone asked me to (in Java say) print the numbers from 1 to 10, I would probably do something like

for (int i=1;i=10;i++) {
System.out.println(i);
}

So would most other people. Would this flag me as a cheater?

Re:How many ways are there to do simple things?

[Monkeedude1212]

Woosh.

There is no need for an assignment like that to be scalable (as is kind of his point). If they were going for scalability they need to be using more variables, like i=x;i==y, and then setting x and y previously so it actually counts the range dependant on what you pass it. And then take out i++, because you don't know if you'll be iterating by one. Maybe you'll need every second number, or third number.

The amount of things you can do to make a simple project "Scalable" is very overwhelming. You need to assess at what point does a scalable option becomes pointless.

And in the case of counting from 1 to 10, he said scalable options ARE pointless already.

Re:How many ways are there to do simple things?

[Mike Buddha]

If someone asked me to (in Java say) print the numbers from 1 to 10, I would probably do something like

for (int i=1;i=10;i++) {

    System.out.println(i);
}

So would most other people. Would this flag me as a cheater?

No, the system would flag you as being wrong. "i=10" would give an error either in compile time in a strongly typed language, or in runtime in a loosely typed one. FAIL.

Re:How many ways are there to do simple things?

[natehoy]

But we didn't wirk togehter you isnensitive cold!!

Re:How many ways are there to do simple things?

[breinera]

As a teacher who used Moss (for a Measure Of Software Similarity), it was dead on. I taught an introductory course for non-CS majors and when MOSS detected something above 90% similarity, it meant cheating was involved. When I questioned the students, they all confessed. I would say about 20% of the class was caught cheating at one point of time or another.

Re:How many ways are there to do simple things?

[DrgnDancer]

Let's say a professor gives us both the same very easy assignment. Something that can be done in ten lines or less, and is meant to display how a for-loop works. We're to comment the code and explain what each line does (because it's a classroom assignment, and that's almost always a requirement even for the simplest tasks). Now chances are we'll need at least two or three variables, and just like the comments we'll be expected to use descriptive names; even though the task is mind numbingly simple. You just have to do these thing in classrooms, even when you're only dealing with two variables and "x" and "y" would serve just fine.

So, what are the chances that we will choose the same variable names, use the same comments, put the same number of spaces and/or tabs in our indents, and insert our white space lines in the same places? Pretty slim most likely. It's more than just "did they use the same basic approach to the problem" or even "did they use the same functions and control structures in the same order?". It's more like "Is this exactly the same program?" or at least "are parts of these two programs completely identical or nearly so?" Of course they also manually chaeck what the automated tools flag. Or at least they should and they claim too.

Re:How many ways are there to do simple things?

[Khisanth Magus]

One of the more amusing moments of my time as a Graduate Teaching Assistant was when I caught 3 students working together in a class where no collaboration was allowed. The sad thing is that in this particular class, there was only one correct way of doing the assignments, so anyone who did it correctly could not be caught. These three had such a horribly wrong answer that there was no way that 3 independent people could have gotten that answer.

Re:How many ways are there to do simple things?

[fataugie]

So how did writing the tuition check feel after knowing they were rubber stamping things? It would piss me off knowing I was supporting some lazy ass professors.

Re:How many ways are there to do simple things?

[Asclepius99]

But we didn't wirk togehter you isnensitive cold!!

Re:How many ways are there to do simple things?

[ShadowRangerRIT]

I had a similar experience. Technically, a correct assignment could be done in different ways, but it was a limited enough assignment that I'd be hard pressed to identify cheating on a correct assignment. Fortunately, the two people who decided to cheat not only did it wrong, they did it hilariously wrong. The assignment was to create "bank accounts" based on an input string (c for checking, s for savings, m for money market). Each account created got $400 more than the previous (the initial account got $500). Then you ran each of them through three months of accruing interest (only difference between account types was interest rate), printing the value at the end of each month. The instructions were far more explicit than I'm being; output was provided for enough example inputs so checking your work was trivial. The two cheaters interpreted it in a hilariously incorrect fashion: they statically created exactly three accounts, one of each type, then used the input string to determine which ones would earn interest. So a string of "csm", instead of creating three accounts and running them through three months interest would run each static account through a single month's interest, then terminate. "ccc" meant the checking account ran for three months, and you saw nothing at all for the savings or money market.

And of course, they were lazy as hell about the cheating. The only difference in the code was variable names, and they weren't even well disguised; rather than changing them, the other submitter just appended to the original name. A variable named "cash" in one submission became "cashMoney" in another.

Lesson to future cheaters: If you're going to cheat, cheat off someone who isn't a complete moron. In CS1, you can only solve the problem correctly in a few ways; identifying cheating is hard, and you're not likely to get called on it unless your solution is character for character identical. But if you solve it in a uniquely dumb way, you'll get caught, and provide amusement to TAs for quite a while.

Re:How many ways are there to do simple things?

[Kevin Stevens]

I TA'ed an intro to CS class that used these error tools, and this was almost 10 years ago. Cheating is a very serious accusation, or at least was taken very seriously by the professor of the class, and several methods were used to ensure there weren't false positives. The first half of assignments were not run through the cheat system, because they were a bit too simplistic and could have caused false positives. The latter half of assignments were all 100+ lines of code.

The system did several checks, and included positives with and without whitespace. In most cases where we had matches, there was a 100% whitespace match, right down to sloppy indents, trailing whitespace, etc. Clear cut copy and pasting. Smarter students would try to clean up the whitespace, usually by adding extra lines, changing comments, or removing some, but it was usually pretty obvious from the diffs as to where they would miss some and it would blow their cover.

The system also did code structure tests, and could pretty easily tell if you just renamed some variables and messed around with whitespace. This was a little harder to review, but when you checked their analysis, I agreed with the results.

All positives were personally reviewed by the professor and TA's, and to be quite honest we were conservative when actually making formal charges against a student- if only a non-critical function (IE the code to load in the list of items in a file in a binary search problem, but NOT the function that actually performs the search) or two seemed to have a direct match, we would warn the students not to share code again and let them off with a warning. I can't recall ever seeing a real false positive. The professor more or less forced you to use vi or emacs on the linux cluster to write your code, so there was no IDE manipulation of the code, and CS students have no sense of coding standards or consistent style, or even reasonably formatted code for the most part, which made cheats even easier to spot.

We taught source control (RCS) pretty early. We told students to check in early, check in often. We understood that beginning CS students were pretty poor at frequent check-ins, but my professor would often give them the option of trying to prove that they were at least not the mere copiers by providing their RCS logs to view intermediary versions and progress. Often the cheater and the cheated on were pretty obvious. The source of the code usually had a few check-ins well before the deadline by someone with a B or better in the class. The copier, if he had any, was usually a few hours before the deadline and had been a C or worse student.

The professor wouldn't punish to the full extent that he could unless there was 100% certainty there was cheating going on.

Personally, I think there is (or at least was at my school) more cheating in CS because it takes a LOT of time to produce relatively little output. A "page" of code could easily take a CS student 4-8 hours to produce fully debugged. When it comes down to deadline time, there is intense pressure, and if someone leaves their files in their home directory undetected, or walks away from their terminal to use the bathroom, the temptation was too great for them, if they couldn't get the code by begging and schmoozing. Some thought they could just use code from previous years, except that we already had a database of previous years assignments (oops).

The only time we ever had a gray area was in the case where a student claimed that they had no idea how the other student got their code. Even then the professor would generally error on the side of caution, but watch the student like a hawk in the future. It was all pretty obvious, I don't think anyone was unfairly persecuted, ever.

Problem

[COMON$]

True CS curriculum require a massive amount of critical thinking and other analytical skills. Something the recent graduates of HS are not prepared for. Match that up with the sense of entitlement and you get expected results. Back when I was in CS the dropout rate was around 90%. There were no rent-a-coders and using the web for a resource was a very new thought. So it was write your own damn code or head over to liberal arts...

Re:Problem

[eln]

Leaving aside the usual nonsense that kids today are worthless and can't do anything right, the problem is more complicated than that. Many universities have stepped away from the idea of going to college as a way to get a well-rounded education and have positioned themselves as places to get a piece of paper that will let you get a good job. Combine this with the increasing number of positions requiring a college degree, and you get a lot more people more interested in just getting through and getting that piece of paper as quickly as possible than they are with actually learning anything.

College is quickly becoming like high school: It's a base requirement that everyone has to go through if they don't want to spend the rest of their lives picking lettuce, so people are going to go and try and get through it as quickly and painlessly as possible. There have always been people who do this of course, and cheating is certainly not a new problem, but the above-mentioned issues may make it more prevalent than it once was.

Remember, though, that our generation cheated as well. Every college in the country has an honor code, and many of them have been in place for decades (or longer). These codes wouldn't exist if no one was cheating before.

Re:Problem

[AstrumPreliator]

I also find it interesting that the TFS mentions "...excessive collaboration..." as a form of cheating. Considering many CS students will graduate and get jobs as some type of programmer I would think collaboration would be a really good thing to impart on students. Granted this is a computer science degree and not a software engineering degree, but I personally know my university treated it more like the latter, and I'm sure this happens in many other universities. Even if it were taught more like a proper CS degree collaboration is still something that should be required to learn. The most collaboration I ever did was with three other people in a software engineering course.

I also did a major in mathematics in college. In contrast with the exception of first year courses like calculus you were always encouraged to work on problems together. Most of my classes were small enough (8 people or less) that the entire class including the instructor worked on the problems. Of course in math your grade was 50% homework and 50% exams. So even if you worked on problems as a group and just took the answers without contributing, you would still fail the class since exams were worth so much (and a C- and under is failing).

I agree that true CS curriculum requires a lot more critical thought, it's actually largely a subfield of math, but that's not what a lot of CS students get. I know I didn't.

Re:Problem

[volsung]

Yeah, most of the cheating I heard about in my CS program 10 years ago was not from people who were necessarily lazy or "party-people" or whatever the usual stereotype is. Most of the temptation to cheat was for people who were completely in over their head with the entire subject and felt backed into a corner. They were wedged between a lack of preparation and social pressure to succeed. ("I did OK in math class, and I like using my computer, so why can't I do this?") The first time many of them had ever thought critically about the structure and function of a computer was day one of CS 101 (consider trying to do college algebra if you had never seen mathematical operators before) and they just got more behind as time went on. This was not helped by the cattle herd design of public university classes.

The ethically smart ones got extra tutoring from classmates and teaching assistants, or worst case, switched degrees when they realized they were hopelessly behind. The not so smart ones abused the help of their friendly/naive classmates or found some other way to BS through the material. Most of the time, this didn't work out even on semester timescales, but I do remember one group project where a guy couldn't write a single line of code unprompted, yet somehow had landed a job at IBM to start at the end of the semester.

I don't have any sympathy for people who cheat in classes, but I agree that characterizing the problem as simple laziness or the "moral bankruptcy of the kids these days" teaches you nothing about how to address the problem. Sadly, the solution probably involves things that are socially or economically infeasible: Smaller intro classes, actual focus on pedagogy and not teaching fads in intro classes, de-emphasis of 4-year degrees as a prerequisite for white-collar employment, more investment and advertisement in focused two-year programs for technical fields, etc.

keyword: caught

[Surt]

They're cheating just as much in other disciplines, it's just in CS we have a lot of good tools to catch them. Plus, we get a lot of false positives with no defense, so we get to inflate our successful catch statistics.

Because that first step is a doozy

[gestalt_n_pepper]

CS is just difficult for some people. We didn't all grow up programming in the basement. I've seen students who finally got their program to "run" by commenting out every line, and sadly, were so clueless that they were quite proud of the fact.

Oddly, it's actually easier now that computers are ubiquitous and going to the CS lab to complete an assignment isn't necessary.

Re:Because that first step is a doozy

[jwinster]

Please mod parent up. I agree wholeheartedly with this comment in that there is a really large barrier to entry in CS. I'm a CS grad, and I remember reading the introductory paragraph to my "Introduction to Programming" book stating that this is not a good book for first time programmers, only people with some experience should use it. Luckily I was able to keep up with the learning curve (despite that being my first time programming as well), but it's choices like that which lead to CS dropout rates of 50-60%, and inevitably, cheating.

What is the sound of one hand coding?

[WillAffleckUW]

When the most optimum solution to any problem is frequently the same code, and the same exact question gets asked every single time for that course, is it cheating or is it just optimization?

I use code libraries and recode old stuff to new uses every day - is that cheating or just efficient coding?

Re:What is the sound of one hand coding?

[IndustrialComplex]

I use code libraries and recode old stuff to new uses every day - is that cheating or just efficient coding?

Most of the professors I had would state that you were allowed to use a set list of libraries. If you wanted to use a different library, it had to be written by you and included in your submission.

The set list of libraries was quite small, usually something like std.h and not much else (I don't know if that was the library, I haven't written anything in C or much else for 10 years)

Re:What is the sound of one hand coding?

[patternmatch]

It depends on the point of the assignment. If you're at your job, and you just need to get something working quickly, then you're not "cheating" by using a library or re-using someone else's code. But when you're in school, the point is to learn the material by solving the problem yourself. So if you just use someone else's solution, you're perverting the intent of the assignment, and that counts as cheating.

My opinion:

[butterflysrage]

Enrollment in undergraduate computer science courses is at an all-time high at colleges nationwide. But this trend that's been hailed by the US tech industry has a dark side: a disproportionate number of students taking these courses are caught cheating. More students are caught cheating in introductory computer science courses than in any other course on campus, thanks to automated tools that professors use to detect unauthorized code reuse, excessive collaboration and other forbidden ways of completing homework assignments. Computer science professors say their students are not more dishonest than students in other fields; they're just more likely to get caught because software is available to check for plagiarism. 'The truth is that on every campus, a large proportion of the reported cases of academic dishonesty come from introductory computer science courses, and the reason is totally obvious: we use automated tools to detect plagiarism,' explains Professor Ed Lazowska, chair of computer science and engineering at the University of Washington. 'We compare against other student submissions, and we compare against previous student submissions and against code that may be on the Web. These tools flag suspicious cases, which are then manually examined.'"

Re:Why?

[Z34107]

Is this not the goal of code re-use? I mean, if there is no copyright violations, that's what ppl should do... Schools are always trying to make you implement retarded things anyway...

You re-use code to avoid "reinventing the wheel." The intent is to 1) save time developing what already exists, and 2) take advantage of all the debugging that was already done for you.

The goal of getting a CS degree is to understand what the fuck a wheel is. Copying from expert sex change is not going to make you a good computer scientist; it won't even make you a good software developer.

Why Computer Science Students Cheat?

[rodrigoandrade]

For the same reason Psychology students cheat.
For the same reason Math students cheat.
For the same reason English students cheat.
For the same reason Economics students cheat.
For the same reason Biology students cheat.

You get the idea...

how to not cheat

[Anonymous Coward]

I used to cheat in college, and all my friends do. I don't cheat anymore. My secret? I switched to a major I like. For the most part, I enjoy and look forward to assignments, and haven't cheated on any since changing majors. For me the subject is CS, but I'm sure that most people could find something they like well enough to look forward to assignments.

Re:And then they check it?

[emurphy42]

That's taken out of context. In context, it carries a clear implication of "manually examined for the specific purpose of confirming or denying plagiarism", on top of whatever manual examination takes place for the purpose of confirming or denying that the code is any good.

CS classes need to be in the real world.

[AnonymousClown]

The professors say:

"Many of our students like to collaborate, but at what point are you copying?" Pitt asks. "The course policy needs to be really clear. Some courses will allow you to work in pairs but not in triples. If you don't follow that policy, we would call that cheating."

The industry says:

"In the real world, people write code in teams where they are given pieces of a project to work on," Foote says. "The academic world should be mapping onto the real worldThey shouldn't be handing out assignments where people are coding on their own."

Ladies and Germs:

We see here where academia isn't keeping up with industry. I can't tell you how many times I've seen where jobs descriptions demand "team players" and "the ability to work in teams".

And I'd argue that academia promotes the prima donna. Someone who was a 4.0 CS student is going to have the impression that he's better than everyone else (maybe true) and that everyone else should get out of his way and let him do it all (not good). I worked with the latter. He was a GA Tech grad and he was rather brilliant. Unfortunately, with all his smarts he was a liability to the team. He couldn't possibly do everything himself (2 million+ line project due in 6 months) and he caused a lot of problems to the point where he was slowing the others down even more.

The geniuses need to be off on their own developing - whatever - that's what we had to do with this guy. He was still miserable, though.

Re:CS classes need to be in the real world.

[pclminion]

I disagree. Computer science has never really been about what happens in the real world. What happens in the real world is engineering. And before you scoff that most code you've ever seen is terribly engineered, remember that these people didn't study engineering at all -- they studied computer science. The problem is that people keep trying to glob CS and software engineering into a single idea, when it's not. CS is no more engineering than organic chemistry is chemical engineering. The goals, practices, daily ways of thinking are not the same.

If I work with CS graduates who can't engineer their way out of a wet sack, I'm not very surprised, because engineering wasn't what they actually studied. And it's not their fault either, because the distinction is never explained in the first place. Students are prepared and told that to be a programmer, they need to study CS. I think CS is something you should study if you want to be a computer scientist. If you want to develop real world code, you need to be on an engineering track.

software sucks

[InsprdInsnty]

One of my lecturers decided to test our university's plagarism software as it was coming back with a unusually high number of false positives. As soon as he submitted a sample he wrote it came back positive for plagarism even though he answered a question just using the knowledge he had gained over his 20+ years experience in the industry. He and many other people in the department put hardly any weight on the results that pop up. His issue with using it is that the content of the course changes so little that with every iteration of students passing through the school its more likely to have incorrect results as its saves a copy of the submission to add to its database. I myself have had work come back as plagarised beacuse there arte only so many ways to write the same damn sentance.

Re:software sucks

[poena.dare]

"just because two people use the same algorithm doesn't make one of them a plagiarizer"

The irony - because of skroooie US patent laws - when two people use the same algorithm it makes one of them a IP infringer!

Re:Why?

[Z34107]

It's neither new nor subtle; it's why expertsexchange now hyphenates their URL: experts-exchange.com.

Re:And then they check it?

[martas]

wrong. they may still look at the code for grading. but catching cheating is a much harder problem: in terms of complexity, grading is O(n) while verifying for similar submissions is O(n^2) or worse. also, in big classes you may have multiple TA, each grading a subset of the submissions. hence may be impossible for them to find such similarities.

What is this "sense of entitlement"?

[Anonymous Coward]

I'm European-trained, but working as a visiting professor in the USA. I hear a lot of people here throw out the "sense of entitlement" phrase, and it's almost always when talking of today's students.

Based on my experiences here and in Europe, I don't think that they exhibit that at all. Most of the students I work with put forth much effort, and don't expect anything other than to be taught the material properly, helped when needed, and graded fairly.

The only people I see with a "sense of entitlement" are the Boomers (I think that's the American term for people who are 50 to 65), and Indian students.

The Boomers always have the most absurd expectations, from getting the best parking spaces (even though they've been at the college for less time than even I have) to getting college-funded coffee makers in their offices to getting raises several times a year, while also getting more vacation time. The unionized folks are by far the worst. Even though some of them are merely janitors, with no special training or education beyond high school, they expect a wage and benefits in excess of those that we get as professors.

The Indians, and by Indians I mean the children of wealthy upper-class families in India, are perhaps the worst. Back in India they got everything and anything they wanted, I suppose. And they were used to treating others as being "lesser", due to their social classes. They bring this with them to America when they come to study here.

Methinks many are missing the point

[mschuyler]

The many examples here of array declarations or variable initializations are not sufficient to get you pegged as a cheater. But when you get multi-line programs of dozens of lines that are precisely the same, even including comments, THAT will ring alarm bells. I don't think anyone writing a simple 'Hello, world' program that is exactly like mine will get called out. If you turn in a hundred line program full of regression equations to plot the Fry Readability Index in a matrix graph that is precisely like mine? Busted!

Much easier to catch

[cfulmer]

So, back in the 'day (1989 or so), I was grading for the first data structures course for computer science majors, and wrote a very simple program that stripped comments out of programs and then counted the number of semi-colons, colons, parentheses and so in in each program's source code, then sorted them. When two programs were sufficiently close, I compared them side-by-side and came up with more obvious cheaters than I was expecting. (Including one from two roommates who happened to be alphabetically next to each other.) If those programs have advanced *at all* in 20 years, they're now comparing parse-trees.

The problem is that computer programs have structure, and it's impossible to copy somebody else's work and then 'only' replace the underlying structure. Instead, cheaters reorder their code, add a bunch of comments, rename variables, change indentation and so on. That sort of thing doesn't change the structure, so it's easy to catch.

And, yes, this method only works on sufficiently large programs -- there are only a handful of ways of doing "Hello World." But, nobody cheats on "Hello World."

What is your quest? What is your favorite color?

[proarchist]

It has always bothered me why CS assignments in some classes are so strangely off from what is supposedly being learned. Often there is some trick and the solution can be found only by not being deceived by the weaselly wording of the assignment, nor by being misled by the current subject matter in the class.

If you are already a successful programmer, these CS projects seem especially surreal given that "cheating" is the label given for all those things you would do in real life to learn and solve, including collaboration and seeking example code.

As an assignment in a computer ethics class I gave a talk on how the internet was going to bring college level CS education, especially self-education, to global masses. (Some universities even put their class materials online and available to everyone.) The idea was that once these useful information and materials got out there, they become part of a more advanced world culture.

During Q and A the teacher criticized that I didn't account for how hard it was to come up with new problems year after year to test and grade CS students, and that putting everything online made this only more difficult. The teacher was actually advocating holding information back to make it easier to rate students.

I answered by saying that there are two competing motivations for teaching methods in university classes: one is to enlighten, feed and grow minds, especially all the minds that paid through the nose for the service; the other was to "weed out," and to grade--like putting the class into a series of sifting screens--the course objects getting removed first and labeled low grade, and the finest ones coming out the end and getting labeled "academic excellence." I asked how much the former was to be sacrificed for the latter.

Didn't finish that class.

college the new HS because HS education failed

[electrosoccertux]

Leaving aside the usual nonsense that kids today are worthless and can't do anything right, the problem is more complicated than that. Many universities have stepped away from the idea of going to college as a way to get a well-rounded education and have positioned themselves as places to get a piece of paper that will let you get a good job. Combine this with the increasing number of positions requiring a college degree, and you get a lot more people more interested in just getting through and getting that piece of paper as quickly as possible than they are with actually learning anything.

College is quickly becoming like high school: It's a base requirement that everyone has to go through if they don't want to spend the rest of their lives picking lettuce, so people are going to go and try and get through it as quickly and painlessly as possible. There have always been people who do this of course, and cheating is certainly not a new problem, but the above-mentioned issues may make it more prevalent than it once was.

Remember, though, that our generation cheated as well. Every college in the country has an honor code, and many of them have been in place for decades (or longer). These codes wouldn't exist if no one was cheating before.

Undergrad diploma is the new HS diploma because companies can't depend on people having a HS diploma to mean that they are capable of critical thinking.
That's what happens when you give them out willy-nilly (big thanks to the folks that implemented no-child-left-behind, and the liberals that won't let us fail students; but both of these are passing the buck-- the real problem is the parents not engaging in their childrens' lives.)

So now an M.S. is the new B.S., but this whole education thing is approaching unsustainability due to the exorbitant cost, both fiscally time required. Quick example, my MicroEcon test that I aced today had 20 questions, took me 20 minutes, and if they gave me all the slides up front I could have learned the entire course in 2 days or less of studying. But this amount of work was spread out over an entire semester. Is that economically feasible? No, we do it for the paper that gets us a well-paying job. With the cost of post-secondary education running away from us, the supply of students getting degrees from legit schools (aka not DeVry, ITT Tech, or your local community college that passes everyone for the same reason the high school does-- because they need the money) will dwindle. Eventually the cost of employing those with legit degrees will be so high that it will be economically feasible to consider employing someone straight out of highschool and just train them yourself. The two requirements for this to work are
1). student is smart enough to teach self things if you gave him a book and the internet
2). student is either a). self-disciplined, or b). can be managed to do work.

You can devise a test for 1), and if you just hire people you know and trust (and have people you know and trust who can refer you to people that they know and trust) then 2) is solved as well.

The point I'm making is I could have learned all my circuits stuff a lot faster with proper documentation and material written down than it took me in the classroom. Further, frankly I didn't need chemistry and Calculus I-III & DiffEq to help me design circuits or code. And I certainly didn't need a semester each to learn the applicable parts. A much more efficient solution (and it's much more motivating) is to worry about that stuff when you need it-- when you run into the term "eigenvectors and eigenvalues" while learning on the job about applying neural networks to power systems, you go teach yourself the linear algebra. It's much more motivating when you're stuck at the job for 8 hours, can't surf the web all day, and the most entertaining thing you can do (and it's actually quite entertaining) is learning things. Even better, it's always need-based, never an arbitrary "you have to learn this so that y