[LoSboccacc]

> information that will be often be outdated and useless in a few years

but this is was HR believes, not the actual reality of software engineering nor of software development.

the concepts between persistence, object model mapping, handling user events, propagating user intent to business logic, share data between heterogeneous systems and present everything coherently to the user are not going to change so all the solutions are going to look and feel the same since stems from the same problems.

I mean for example chaining template for code reuse isn't something that only react ever did, I remember turbogear doing something very similar conceptually with how nesting widgets and widget having each their own template and dictionary of inputs that took from the model state directly and the lesson you learn on problem solving and code reuse do stay with you a long time, longer than any single framework.