since I'm largely in the same boat: I think it has more relevance in some fields than in others. E.g. programming is relatively good at naming things descripti

since I'm largely in the same boat: I think it has more relevance in some fields than in others. E.g. programming is relatively good at naming things descriptively, but less-so many fields that name tons of things based on the discoverer, e.g. biology-related things have a fair bit of this. And obviously there are numerous exceptions in both directions. For programming: I'm quite happy saying "learn concepts, not terms/frameworks". There's obviously some value in things you use a ton daily, but you'll naturally remember those through use - for the rest, thankfully, programmers are great at making things searchable, and there are loads of tools to search even when not (e.g. grep). Terms can be useful for communication purposes, learn them as needed and meh beyond that. Frameworks though are basically the programming-world equivalent of fashion, they change with the weather / at the whims of popular tweets. Yolo - learn how it works instead of the API, that's waaaay more useful, and is probably transferrable to dozens of other frameworks. But as an example: I routinely forget the argument order and finer details of the various "split a string" funcs in the 3 or 4 languages I use ~weekly. Because I only use them every few months. And in my next language, quickly-recall-able memory of those other-lang patterns won't help me in the least (if anything, they might slow me down). Splitting a string though, and choosing which end to start from, and how many times to split, and the various i18n complications, is a general concept that's applicable in all languages.