Tools however is harder. Elastic, graphql, docker, front end framework (angular, react vue), are very very different conceptually compared to the past technology.
To me the problem is the emphasis some companies place on knowing specific tech.
>Must have five years experience in Web development with a focus on front end frameworks eg react/angular and cloud experience (aws preferred)
VS
>must have two years experience with the following; asp net 5.0, aspnet mvc 5.0, automapper, xunit, tiny ioc and azure Webapps
However, typical the good companies have the former. So you can spot it out pretty easy. Although I fear the industry is moving more to specific skill sets and certification. The certificates trend is being pushed harder as it makes a lot of money for these companies.
With certification, I don't think it'll happen in near future, due to how hard it is to certificate a programmer and how scarce they are right now. Though it's possible for outsourced foreign developers such as India to be required certification.
What this assertion misses is that many no longer want to work in their free time anymore. Even if I love programming ever since 12y/o I can no longer make myself care about $day_job when I can have a proper rest, which is precious and not that much anyway.
Benefits over jquery were clear. However replacing one jquer my developer with 10 modern developers that got only a fraction of the work done.
Well that broke my brain too.
Now I’m in a situation of developing against k8 infrastructure, I’m seriously thinking of going back to compiled python programs that can be emailed. Just some people can actually get work done.
If your team is small, use tools that can perform the best on small team, if your team is big, use one that can support it. K8s is used for going big, angular is used for complex interface.
If your team is always gonna be small, then how are you going to learn the stuff that scales?
Are you going to wait get a job that allows you to do so?
Then you can still add that to your resume.
I learned Python programming almost 20 years ago by also writing a small script on my Linux machine (a Mandrake distribution), running it through py2exe and then copying it on a floppy disk, then get to work and use that .exe program to automate some stuff for me there.
That proved to me that programming can be very helpful sometimes, as in that example it provided me with lots of free time during work, on the behalf of the stuff I had just "automated" for myself. Very good times.
But yeah, much of the "relearning", I've found, is to work with new sets of tools that solve problems that... we didn't have 15-20 years ago. Or, not to the same degree, at least. And some of those new problems and changes have benefits, some don't, some are solving self-imposed problems, some are "solving" problems that don't have concrete "solutions", only "opinions".