For what it’s worth, reading the ECMAScript spec was one of the best things I’ve done to deepen my work as a developer. It doesn’t touch on console commands, bu

For what it’s worth, reading the ECMAScript spec was one of the best things I’ve done to deepen my work as a developer. It doesn’t touch on console commands, but these do: https://developer.chrome.com/docs/devtools/console/api/ https://developer.chrome.com/docs/devtools/console/api/ https://developer.mozilla.org/en-US/docs/Web/API/console https://developer.mozilla.org/en-US/docs/Web/API/console https://nodejs.org/api/console.html https://nodejs.org/api/console.html It’s not that I’m just reading language docs all day, but I’ve found it to be a really productive use of time when I do. It’s a vehicle for discovery that tutorials, SO answers, and blog posts don’t tend to always cover. For instance, I learned about Realms in JS which allow for a distinct global context, and more recently the proposed ShadowRealms API which not only just sounds cool, but allows for some neat isolation if ever you need to run JS in the browser that shouldn’t affect the window (such as a web IDE). For those who are brave enough to delve into the Shadow Realms: https://www.ecma-international.org/wp-content/uploads/ECMA-262_12th_edition_june_2021.pdf https://www.ecma-international.org/wp-content/uploads/ECMA-2... Point being: there are formal manuals and specifications for every part of the web stack. They can be intensely difficult to grok but are a valuable resource. It’s not fair to say RTFM to every question about the web stack, it’s unreasonable to expect anyone to hold all of that in their brain. Still, these things do exist and have a lot of value.