r/javascript • u/fl0at • Feb 21 '11
Recommendations for mastering JavaScript.
I'm making it a goal of mine to master JavaScript and was hoping someone else had done the same and wouldn't mind sharing their regime.
**EDIT: ** I've created a new post to host all the references from this post. Find it here.
EDIT: Thanks guys. I've compiled a list of references mentioned here. I appreciate all your contributions.
Anything written by Douglas Crockford. This includes: JavaScript: The Good Parts and YUI Theater
Read other people's code, jQuery source, Node's source, etc.
Understand JavaScript before becoming dependent on libraries (eg. jQuery, Prototype).
Addy Osmani's Javascript 101 audio course
Build Things - "think of something cool, and try and build it."
Participate at StackOverflow.
References -o- plenty: Gecko DOM Reference, HTML and DHTML Reference, Yahoo! YUI Theater, w3schools.com HTML DOM Tutorial, Annotated ECMAScript 5.1, JavaScript, JavaScript Blog
And finally, Lord loves a working' man, don't trust whitey, and see a doctor and get rid of it.
10
u/sjs Feb 22 '11 edited Feb 22 '11
Read about JavaScript's strengths, weaknesses, good, bad, and surprising bits:
Learning Advanced JavaScript by John Resig
JavaScript Garden
Eloquent JavaScript
My Variable Declaration got Hoisted
Another JavaScript Quiz (Be sure to check qfox's comment with explanations)
wtfjs
Learning JavaScript with Object Graphs I
Learning JavaScript with Object Graphs II
Learning JavaScript with Object Graphs II
What is "this"?
A Crash Course in DOM Events (Relevant only in browsers of course)
Watch papa Crock's lectures and talks, they are excellent, even if he's a little too opinionated sometimes. It's good for the community to have an opinionated, pragmatic guy like him around.
Doesn't hurt to follow The Changelog and notable JavaScripters either. If you don't read that list just follow @BrendanEich, @awbjs, and anyone twitter says is similar to them.
Read code, especially code from projects maintained by the best. And of course ... write code of your own! You have to find out what you think are good and bad parts, etc. And when you run into surprises and gotchas in your own code you really learn about them, because you care more at that time.