IMHO, today to many people think "don't have to worry about them" equals "don't need to know anything about it".
It’s not like reading 10 bullet points on the subject is “diving deep” and making huge time investment.
It’s just getting the minimal context, so later on at least some keywords are known.
Not sure how many computer related topics you know/want (“The more you know, the more you know you don't know”), but for me, 50 topics on programming seems sufficiently high at frankly a very low effort/commitment.
True, but you're using so many abstractions that the rule can't feasibly be "read a short summary of every abstraction you're using." There are just too many. At some point you have to choose a threshold where the likelihood of an abstraction leakage is sufficiently low. When you're debugging a CSS selector you will almost certainly never need to know about even the existence of, say, Fermi–Dirac statistics.
Rule - no. Goal - yes.
Some topics are more stable and valuable then others, so prioritisation helps.
“How utf8 generally works” vs “implementation details of js-node-utf-related-library-X.”