Mild counterpoint. Our professions(all things IT) moves bloody fast.
If I were looking for info on cooking, baking, knitting sure... but IT stuff, I opine many of us seek the latest info because of the breakneck speeds this profession is known for.
Some areas do, some areas not so much.
I have a colleague that's incredibly strong with databases (we use a mix of MySQL and PostgreSQL) and he's living off the learning he did 20 years ago when he was a junior Oracle consultant.
I live off the learning I did in Linux now that I administer Kubernetes clusters for a living. Once you get past the "cloud native" abstractions (and other BS) it's penguins all the way down, and I get to reuse most of my core Linux competencies I learned 10+ years ago (eg: I do tcpdump in prod, and it's quicker and more effective than many of the modern shiny tools).
It still does change and you have to adapt.
E.g.
> databases (we use a mix of MySQL and PostgreSQL) and he's living off the learning he did 20 years ago when he was a junior Oracle consultant
And there's lots of changes here, e.g. vector stores, all the different query engine improvements, PostgreSQL IO improvements, etc and they all may impact your job. Your optimal query back then might not be the same. Living off the old learnings is like taking a 50% discount on the max potential.
> I live off the learning I did in Linux now that I administer Kubernetes clusters for a living.
And these have had changes consistently too e.g. io-uring and gateway api. You can only be in legacy for so long.
That is why there isn't much else to go but the heuristic of the most new class with the most ratings.
A few years ago i happily spent 12€ on a course about gitlab ci that saved me quite a bit of time reading documentation and got me started within an afternoon. I had no previous experience with gitlab, but i was well versed with git.
Those were money well spent, for example.
It wasn’t a big deal but I would have still appreciated it if the author inserted some new recorded segments or re-recorded some content to make up for it.
I think you are confusing interiorizing some fundamentals with things moving fast. There are languages and frameworks rolling out higher level support for features covering concurrency and parallelism. While you focus on thread-safety, a framework you already use can and often does roll out features that outright eliminate those concerns with idiomatic approaches that are far easier to maintain. Wouldn't you classify that as moving fast?
