Earlier quoted context omitted.
Whatever you want it to be.
Care to expand? This isn't exactly a helpful answer
As Computer Coding Classes Swell, So Does Cheating
51–60 of 303 posts
Re: As Computer Coding Classes Swell, So Does Cheating
#52This is very interesting: the clause that apparently gives a way out to the student is never/seldom used, but it gives the teachers more confidence and easiness to report their students. Its a measure that literally just makes it harder on the students, even if it appears the opposite.
Economics is truly magic.
Re: As Computer Coding Classes Swell, So Does Cheating
#53What they call "cheating" is how I do my job as a developer of a 3-person (dev) software company. We make software. People like it and use it. We make money. Who cares whether the code came from our head or from something publicly available on the internet, or from someone willing to help us? As long as it wasn't an actual violation of the law. There's no good reason to create a separate set of laws for the classroom…
But it is a violation of Academic Integrity, which is sort of a law you agreed to when signing up for a class. At least at my school it was like that.
Re: As Computer Coding Classes Swell, So Does Cheating
#54Earlier quoted context omitted.
Its a sunk cost. You won't know if they pass or not until you interview them.
What part is the sunk cost? Interviewing applicants takes time out of a lot of peoples' busy days. They don't have to spend that time if the company doesn't bring the applicant in for an interview.
Then they're brought in for a technical interview. There's no escaping that. You don't give automatically give them a job because they listed a 4.0 GPA on their CV and were nice on the phone.
Re: As Computer Coding Classes Swell, So Does Cheating
#55Then it's no wonder that, on the other side, we see things like https://blog.codinghorror.com/why-cant-programmers-program/
Re: As Computer Coding Classes Swell, So Does Cheating
#56Earlier quoted context omitted.
What part is the sunk cost? Interviewing applicants takes time out of a lot of peoples' busy days. They don't have to spend that time if the company doesn't bring the applicant in for an interview.
That's obvious enough. Any recruiting funnel will have a criteria of requirements that the prospect needs to fulfill. Then they're brought in for a technical interview. There's no escaping that. You don't give automatically give them a job because they listed a 4.0 GPA on their CV and were nice on the phone.
Re: As Computer Coding Classes Swell, So Does Cheating
#57Re: As Computer Coding Classes Swell, So Does Cheating
#58This is hugely important as a lot of people see programming as a ticket into higher-end jobs and will spend as little time as individual contributors as they can. The idea that "oh, they'll get caught in the workforce" is not correct - quite often the plan in the mind of these folks is that they will try to fake their way through and be moved up into project management, technical marketing, etc. and never have their…
Here's the trajectory: Fake your way through basic CS courses. Find your way into group-work heavy projects in later years, possibly doing enough ancillary aspects of the work to be semi-useful. It will be likely that your other group members will find it easier to grin and bear it. Optionally: do a Masters or PhD. Plagiarize your work, or potentially hire someone to do it for you. Continue into the work force, focus…
Anyway, he would get up in front of the staff meetings and say, the school is graduating students who do not know how to code. The school didn't care; they got paid. Every class of any import had team projects because "that's what the real world is like". And every team would have the one person just skating by. The only exceptions in my entire undergrad education was in the graduate level course I took with a friend, which thankfully had two-person teams. And the one elective I took with the aforementioned lecturer, who actively kept tabs on who was doing real work through surveys and looking at the source repositories.
Re: As Computer Coding Classes Swell, So Does Cheating
#59My engineering courses were filled with cheaters. Fortunately, these become apparent in the workplace and filter out in the first few years. Any major with promise of wealth will have those who will resort to ill means to get ahead in the system. Again, fortunately, many are weeded out in later stages.
You are assuming the system is perfect. > Again, fortunately, many are weeded out in later stages. Why do you care?
Re: As Computer Coding Classes Swell, So Does Cheating
#60My engineering courses were filled with cheaters. Fortunately, these become apparent in the workplace and filter out in the first few years. Any major with promise of wealth will have those who will resort to ill means to get ahead in the system. Again, fortunately, many are weeded out in later stages.
You are assuming the system is perfect. > Again, fortunately, many are weeded out in later stages. Why do you care?
chose to use the word "many" to imply the current process is imperfect.
> Why do you care?
I'm a recipient of freshly graduating (and interning) engineers who got past the hiring committee.
The project roadmap puts a burden on the other team members when one member is underperforming and/or not forthcoming with their abilities.