Having gone through an engineering program, the first two years were prerequisites which were entirely required before anything useful was learned starting in year three.
And it wasn't just extensive knowledge gained, that was the least important part. It was learning how to think. There was quite a lot of mindset change. It just isn't feasible for many kinds of engineering to babysit high schoolers for 5 years before they become useful. (undergrad graduates aren't useful when they start either).
It was learning how to think. There was quite a lot of mindset change.
Indeed. I remember when a prof introduced us to linear programming - it was literally mind expanding - suddenly a whole class of problems that I couldn't even properly think about before because I lacked both the vocabulary and the mental structures, were within my grasp. Now it would theoretically have been possible to teach myself LP... But I couldn't have in practice, because I didn't even know there was such a thing, let alone what it was called. All the googling and stack-overflowing in the world can't help you in that situation.
A sufficiently motivated student could do it via MOOC sure (I am doing one myself right now to get up to speed on ML) but for most people, most of the time, the traditional old-fashioned in-a-lecture-theatre degree is the right call.
I don't think there is anything inherently wrong with google programmers. Sometimes looking something up is faster, sometimes it's inspiring.
The thing a degree does though, is make sure people know what stackoverflow code to ignore.
You can certainly obtain the same knowledge on your own, and you can certainly avoid getting it with your degree.
The thing is though, hiring people is about minimizing risks. The most expensive mistake you can make as a manager is hiring the wrong person, and degrees offer the highest probability of skilled labour.
> I don't think there is anything inherently wrong with google programmers. Sometimes looking something up is faster, sometimes it's inspiring.
I think the term "google programmer" covers too much ground to make a blanket statement.
On one hand, Google and StackOverflow can serve as an easy to use interface to documentation and troubleshooting information. I think this use of Google is great.
On the other hand, it's also possible to use them as a source of copy/paste code snippets without necessarily understanding what the code is doing. This second kind of "google programmer" is a huge problem. These are the type of people we all laugh at for not being able to solve FizzBuzz (assuming they haven't found somebody else's solution to copy/paste).
> The thing a degree does though, is make sure people know what stackoverflow code to ignore.
I wouldn't count on it. Even if a code snippet on SO is 100% correct, that doesn't mean it'll be the best solution outside of the original asker's situation.
Having gone through an engineering program, the first two years were prerequisites which were entirely required before anything useful was learned starting in year three.
And it wasn't just extensive knowledge gained, that was the least important part. It was learning how to think. There was quite a lot of mindset change. It just isn't feasible for many kinds of engineering to babysit high schoolers for 5 years before they become useful. (undergrad graduates aren't useful when they start either).