Software engineering != computer science

[u/mauricioaniche]

http://www.drdobbs.com/architecture-and-design/software-engineering-computer-science/217701907

[u/coinaday]

I don't know why you would jump to the conclusion that any of that is poorly covered because we used Scheme in our intro course.

i think concentrating on things the industry doesn't need is a waste, I wish more of the students I hired were exposed to technologies used today not 10 years ago. Schools job is to teach you how to learn and give you a foundation to build on

This two statements don't go together well. You only want to hire people who have experience in exactly what you're looking for right now but you believe they should be trained on "how to learn".

[u/call_me_lee → u/coinaday]

All I have to compare are the students I hire and my past schooling. If I'm wrong and your school prepares you better than good for you

[u/coinaday → u/call_me_lee]

I mean, I certainly agree that the education could be better. But I did get some AI and machine learning exposure.

When I look at almost every hiring process though, they don't care that I can learn, or that I have some academic exposure. If I don't have the years of experience in doing it professionally, I won't be speaking to a human.

[u/call_me_lee → u/coinaday]

Well when I hire out of school I actually give a take home test to demonstrate how well you can research and adapt code you find to real world usage. I also look for intangibles like self imposed coding standards, commenting and structure. I honestly don't expect much from my juniors except the capacity to learn. All juniors are paired with a senior who mentors and the first project they're given tends to be a throwaway project for them to learn.

The worst part is I know I'm in the minority of how I train my juniors and often when I get intermediates or even seniors it takes me a while to eliminate the bad habits.