I agree, but IT and CS are even more prone to deprecation problem regarding the fact that everything evolves so fast, that you can't write a book so fast to cover new technology, in meantime, it can become deprecated.
But that's exactly what universities doing:
They pick up current discoveries and modern set of technology.
Professor takes time and writes learning material, book or scripts.
A couple of years afterward professor established his lessons, and he will stick to that in next 10 years since changes are not what they like to do.
In the next ~5 years, the material is already deprecated since it sticks to concrete language and technology
you got engineers which knows some deprecated technology stack
I personally believe that professors should focus their lessons on problem-solving, agile acting, design principles, testing etc. Then they can use any "current" language in classes to demonstrate that.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
Lots of the skills and knowledge that recent grads lack is also the stuff that barely changes at all.
Some examples include business analysis, requirements gathering, basic stats, ethics, professionalism, code quality, code maintainability, leadership, management, testing, security principles, communication, etc.
I'm putting the finishing touches on a blog post with over 30 books that every programmer should read and lots of those book at 20ish years old. And the oldest book on the list is 52 years old!
The universities and colleges could do some much better.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree, but IT and CS are even more prone to deprecation problem regarding the fact that everything evolves so fast, that you can't write a book so fast to cover new technology, in meantime, it can become deprecated.
But that's exactly what universities doing:
I personally believe that professors should focus their lessons on problem-solving, agile acting, design principles, testing etc. Then they can use any "current" language in classes to demonstrate that.
Lots of the skills and knowledge that recent grads lack is also the stuff that barely changes at all.
Some examples include business analysis, requirements gathering, basic stats, ethics, professionalism, code quality, code maintainability, leadership, management, testing, security principles, communication, etc.
I'm putting the finishing touches on a blog post with over 30 books that every programmer should read and lots of those book at 20ish years old. And the oldest book on the list is 52 years old!
The universities and colleges could do some much better.