Comment Re:Yes, but no (Score 1) 637
But the bigger problem we have with new-grads and junior-devs, in general, is the same problem you'd have in any field: they're green. They don't test well, or at all. They don't think designs through. They don't communicate well. They ask too many questions, or maybe worse, they ask too few. They try to fix things that aren't broken. They're bad at estimating task sizes (admittedly, people rarely get much better at that even after decades.) In an attempt to not suck, they reach out for best-practices and apply them zealously and inappropriately. They can't imagine how things will fail, or be abused. They spend too much time fixing small problems, and not enough time fixing big ones. And maybe worst of all, they're under the illusion that what they learned in school ought to prepare them for the workforce, when really it just gets their foot in the door.
The way I summarize these problems is that the problem with most college graduates is that they thought and behaved as if the purpose of their college years was to learn stuff, when it was really to learn how to learn stuff. The first skill you will need in most of the jobs you might get after college is learning. You should have had a lot of practice if you approached college right, which most don't. You're right that *what* you learned in school does not and cannot prepare you for joining the workforce, but *practicing the act of learning* a wide range of skills and thought processes can prepare you very well.
I tell people if you want to be a professional, college is professional learning on training wheels. If the thought of learning as much as all the learning you did in college every couple of years until you die is not appealing, consider a non-technical non-professional career. Because you're going to suck at it otherwise.