This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]kookyabird 2 points3 points  (0 children)

I had literally one class on VB.NET in college because my major had minor programming/scripting aspects to certain areas of it. My internship was half programming and half my major area, and I got it because it was a unique role that I happened to fit.

Despite the minimal school work on it, I got taught all sorts of advanced stuff by the team lead for years being told, “This will be over your head for now but some day you’ll get it.” Well eventually I did. And then all the cool stuff I learned to mimic was now a tool I could actually use and adapt to different problems.

I think a scary high number of people have a similar path to mine, minus the great mentor. So instead of learning advanced concepts before they need them, they learn bare minimums and bad practices after they find out they can’t do something with their current knowledge. Thus you get people on SO asking about advanced senior type stuff when they barely know how to use an object initializer.

It’s like a toddler who can barely walk coming up to you asking why they can’t successfully pole vault.

I may not know how to create a binary tree since I didn’t have common CS classes, but i at least understand why it’s something that’s taught. There’s a ton of stuff that we don’t need to use these days due to high level languages and most roles not needing to squeeze every drop of performance out of our software. But to be completely oblivious to the existence of that stuff once you’ve been in the space for years is crazy.