This is mostly shallow advice masquerading as deep advice by disparaging “shallow” frameworks. The main thrust of the article seems to be “learn design patterns

This is mostly shallow advice masquerading as deep advice by disparaging “shallow” frameworks. The main thrust of the article seems to be “learn design patterns” plus a list of books. That’s a fairly thin amount of information for an entire article. My own input to the debate is this: learn frameworks. Do not learn bleeding edge new frameworks, only those that are proven and have significant market share, or unless your job requires them, or you have a personal interest in them. Expect that these will change every few years and that you will need to pick up new ones, but hang on to the ones you already know until they’re effectively deprecated. On top of this, know good practises ala clean code etc. and design patterns. I really don’t know how I could spend 80% of my time learning the fundamentals and 20% learning frameworks. Am I just supposed to keep reading the same basics again and again instead of learning technology that is actually new?