We can't generalize. Not all students are like the ones described in this article. I work with CS and CE graduate students 40 hours a week. I help them conduct research. The best of these students have an eagerness and desire to learn. They work on projects at home in their spare time, they learn new languages (just for the sake of learning them), etc. They want to learn C and C++. They love it.
Since I work directly with these kids and have seen dozens come and go, it's easy for me to quickly pick out the good ones. They are the most fun to work with too as they teach me as much or more as I teach them.
I see the average/bad ones too. The ones who do just barely enough to get by. The ones who "code by Google". They are far more common than the good ones. Their work speaks for itself. Poorly written, plagiarized and seldom delivered on time.
Hopefully employers have methods in place to weed out the bad and average kids. And incentives to hire and more importantly keep the best ones.
Since I work directly with these kids and have seen dozens come and go, it's easy for me to quickly pick out the good ones. They are the most fun to work with too as they teach me as much or more as I teach them.
I see the average/bad ones too. The ones who do just barely enough to get by. The ones who "code by Google". They are far more common than the good ones. Their work speaks for itself. Poorly written, plagiarized and seldom delivered on time.
Hopefully employers have methods in place to weed out the bad and average kids. And incentives to hire and more importantly keep the best ones.
Just my 2 cents.