As Computer Coding Classes Swell, So Does Cheating

I think this creates a massive disincentive in order to ask why they didn't get the mark they want. For fear of being marked as a complainer.

At the end of the day you are there provide guidance to get their skills and knowledge to place they want to be. Not to simply filter wheat from chaff.

Is it not standard to have your ID checked when taking exams? I had to take my university ID with me to all that I sat at a British uni.

I've been an assistant on 1st to 3rd year bachelors courses in CS in the Netherlands (basic OOP, Software Architecture and Algorithmics like courses) and probably seen many of the types of copying and forgery. I can concur that most students don't really understand but just regurgitate what has been said even at Academic levels. On some Examples of what i've seen which sometimes leads to the types of interns you give:

- 1-on-1 copy paste, change the name: Easily caught by looking, no need for anything else. These will fail.

- mostly copy/past, changing names some locations: Easily caught by letting them explain the workings of their code, they will always fail. I've had one lazy student who could easily explain while copying but was just lazy out of hundereds. These can slip through if the course is understaffed or badly designed.

- Hand written assignments: Mostly parallel working when individual required, I'm not agains cooperation but mostly you could see that one student got the exercise right and the other just copied him/her and usually lacks details which are in the other assignment. It is very noticeable if they copied it due to similar layout and textual form. If the assignment is too simple this is harder to detect, but quite easy in algorithmics courses. These are far harder to detect and prevent, though individual checkups (at random) are a good way to test the true knowledge acquired. Needs lots of staff which is never there since 'budget cuts'.

The biggest problems are the group assignments as noted in other posts. They are hell to get rid of people as failing one usually means failing all even when some didn't perform. The usual trick to get it right is to either fail the entire group and give them an individual assignment to filter out the incompetent or to do the same thing on an individual basis. The problem is that you actually have tangible evidence otherwise it is very difficult, though commit logs is a start. The people who should fail and get through are at least some of the 95% you mention.

The 5/100 ratio is not odd/off in my perspective. You describe the top 5-10% (which are good and you want at your company) vs the next 30-40% which are average and simply make things work but lack initiative or knowledge vs the rest which should look for another job since these applications usually contain at least some amount of incompatible applicants.

Consider that if you pay peanuts, you get monkeys so that also might be the problem.

ps: IT-managers without proper IT knowledge (and yes I mean the basics) are the same thing as a CEO who is unable to speak in public: Nice decorations on the office floor but utterly useless in practice.

OK, but real success in sales takes enormous talent, skills, and experience.

There are many different job-roles out there and it is hard to find out what these roles even are. It takes time for people, especially freshly graduated students and career changers, to find their niche. At some point almost everyone gets themselves into situations where they're not competent and then realize they need to either make a switch or get focused.

Rather than viewing such career-exploration failures as "fraud", as some are apt to do here, it is better for employers to take a more active role in developing talent and recognize that early career folks are going to be hit-or-miss.

As a JavaScript developer none of this matters to me. Here is the reality I see:

JavaScript skills are in demand almost everywhere even if it is not the primary language or skill of a given job. Almost nobody receives any kind of formal education or training in how to write in JavaScript. If you work for a web based company you WILL at some point be tasked to write in JavaScript.

When developers, who have never touched JavaScript before, are tasked to write JavaScript one of a couple things happen. First, they will attempt to write Java (C# or whatever) in this language because the syntax roughly looks the same. Secondly, they will grab the easiest framework they can find and hope to fill in the blanks.

Essentially, at the end of the day, almost nobody knows what they are doing. In this line of work most people are utterly afraid to write code. We would be in much better shape if our biggest problems were developers or students cheating.

Some food for though: https://www.reddit.com/r/programming/comments/66hpqs/less_th...