
Covers the bits of Javascript that are worth using, and how to use them, as well as the bits that should be avoided.
https://www.oreilly.com/library/view/javascript-the-good/978...
Helped me get a more pragmatic approach to use that chaotic mess of a language and environment. Just use what works, ignore the rest (but I also ignored some specific advice from the book and used what worked for me).
[0]: https://www.oreilly.com/library/view/javascript-the-good/978...
I'm working on a book called "How to not get your knickers in a twist because you neglected to learn from people who came before you."
* The Mythical Man-Month, Fred Brooks: Provided an argument against inexperienced managers who errantly assert that they need more developers to get projects done quicker; perhaps more importantly, it gives as a model for a programming team with a "chief programmer" to whom these managers need to report
* The Timeless Way of Building, Christopher Alexander: Taught me the original (perhaps better) concept of design patterns, which helped in talking to colleagues about the parts of software we build and reuse
* JavaScript: the Good Parts, Douglas Crockford: Led me to a solid understanding of how to make good use a crummy scripting language that was only really meant to glue DOM behavior to Java applets
He's done the work, so he has more right to complain than most:
* https://www.oreilly.com/library/view/javascript-the-good/978...
https://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockfo...
It may be a perfect time for a revision.
Eventually it makes sense to learn JavaScript on its face. It is a weird and beautiful language. Abandon hope of understanding it unless you read a coherent book about it. As for me, I read JavaScript: The Definitive Guide from cover to cover. I have also read good things about JavaScript: The Good Parts, and I know that Douglas Crockford is smart.