Exploratory clicking on MDN can help. For the language itself, a recent official ES paper. When learning yet another programming language seriously, I’m usually skimming through the standard library symbols to see the spirit of it, because stdlib/lang creators usually know both design and rationale. I also clicked through all of the tabs in a developer console in my browser to see what’s useful there. I doesn’t take up much time, and is much more complete. Personally I’ve never understood the value of these blog posts, because their appearance on your horizon is erratic and unpredictable unlike documentation and exploration, e.g. this article brought nothing new to me despite I’m only 2-3 years into javascript/web (out of much longer swdev career which taught me to educate actively), but ymmw.
My absolutely respectful but straightforward advice is: stop relying on blog posts, just go and click where you didn’t. It’s not a secret sacral knowledge, it’s you being anxious of unknowns of your development tool and of scary docs which are actually your friends.
My absolutely respectful but straightforward advice is: stop relying on blog posts, just go and click where you didn’t. It’s not a secret sacral knowledge, it’s you being anxious of unknowns of your development tool and of scary docs which are actually your friends.