r/javascript • • 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.

  1. Anything written by Douglas Crockford. This includes: JavaScript: The Good Parts and YUI Theater

  2. Read other people's code, jQuery source, Node's source, etc.

  3. Understand JavaScript before becoming dependent on libraries (eg. jQuery, Prototype).

  4. Addy Osmani's Javascript 101 audio course

  5. Build Things - "think of something cool, and try and build it."

  6. Participate at StackOverflow.

  7. 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

  8. And finally, Lord loves a working' man, don't trust whitey, and see a doctor and get rid of it.

32 Upvotes

93 comments sorted by

View all comments

Show parent comments

-1

u/StoneCypher Feb 22 '11

I'm relatively new to Reddit

Obviously.

but isn't the point of voting in comment threads to show agreement/disagreement?

Absolutely not. Point five in rediquette:

Please don't: Downvote opinions just because you disagree with them. The down arrow is for comments that add nothing to the discussion.

This is especially important in programming settings, where novices will frequently disagree with the advice given by people with experience. Reddit is not an agreement circlejerk. Downvote people who are legitimately trolling - making race comments in a technical discussion to get a rise, for example.

Ignore the bad examples being set around you, where assholes who don't understand say "but i disagree with your advice, therefore it is wrong, therefore it is not adding, therefore you are trolling." They're just soothing their egos.

Be better. Upvote is for people trying to contribute. Downvote is for people trying to cause a problem.

NEITHER ARE FOR AGREEMENT OR DISAGREEMENT.

Otherwise we'd have like 50 billion posts with "+1" or "3===D".

Yeah but you aren't downvoting those because you disagree with them; you're downvoting because they do not contribute to the discussion.

This is a distinction that it used to be that everyone understood.

2

u/[deleted] Feb 22 '11

This is especially important in programming settings, where novices will frequently disagree with the advice given by people with experience.

Evidence to back up claim of being "experienced"? I imagine you as a socially awkward old school programmer who knows some stuff about js, but can't or won't participate in the online social sphere creating a Phantom of the Opera (no relation to the browser) scenario.

1

u/StoneCypher Feb 22 '11

I imagine you as

Nobody cares.

At this point it's becoming clear that your only points are that you think I'm wrong because:

  1. You've never seen a big name give my advice, no matter how common it is, and

  2. You imagine that someone who says "how to master" needs beginner's advice.

Find someone else to talk to, if you can't focus on the actual responses you get.

2

u/[deleted] Feb 22 '11

Ad hominem aside, you're making claims of being experienced, with nothing to back it up.

I chose to move past the rest of your post as I don't have anything to say about it.

1

u/StoneCypher Feb 22 '11

Ad hominem aside

There has been no ad hominem.

you're making claims of being experienced

No, actually, I didn't. However, you did, in saying that my advice was wrong, and furthermore you didn't back that up.

I am, of course, experienced. How am I to show that? Shall we climb in my time machine? Maybe you can come visit me at some of my day jobs.

If I say where I work or what I make, you'll either call me a liar or say that it doesn't matter to you.

If I show you my code, you'll either say it's low quality without looking at it, or say that hobby code doesn't make experience.

If I show you my various profitable companies, you'll either say I'm lying, or that companies don't create experience either.

I have not at any point claimed I'm experienced - at least before this post - but I am. What sorts of metrics would satisfy you on that front?

And while we're at it, how do you intend to show that you're experienced, since you've explicitly used experience as a justifier of criticisms that you seem unable to justify in a legitimate technical fashion?

Don't worry, I'll answer first, so that you can scurry off afterwards without showing your own.

I chose to move past the rest of your post

No, you were moved past. Indeed you went on and replied more to another instance of the same post later.

I don't have anything to say about it.

The last two words are extraneous. You've been asked to justify your own stance and failed. Now you're demanding the thing you won't do of others.

I will, of course.

2

u/[deleted] Feb 22 '11

There has been no ad hominem.

There was on my part with the Phantom reference and the hugging comment. For that I'm sorry.

This is especially important in programming settings, where novices will frequently disagree with the advice given by people with experience.

It seemed like you were speaking from a personal viewpoint, implicitly including yourself in "people with experience". This assumption has been borne out what with you going on to say "I never claimed I'm experienced.... but I am".

And while we're at it, how do you intend to show that you're experienced, since you've explicitly used experience as a justifier of criticisms that you seem unable to justify in a legitimate technical fashion?

I am, of course, experienced. How am I to show that? Shall we climb in my time machine? Maybe you can come visit me at some of my day jobs.

If I say where I work or what I make, you'll either call me a liar or say that it doesn't matter to you.

If I show you my code, you'll either say it's low quality without looking at it, or say that hobby code doesn't make experience.

This is why I bring up names that are established. Instead of whipping out our tape measures on the internet, we can point to people who we know can piss really far.

Maybe my stance hasn't come through clearly enough:

** Reading the ECMA spec like a book is only valuable given that you have enough of a grasp of the language in the first place.**

→ More replies (0)