Live data from Hacker News

Tips to Become a Better JavaScript Developer

justinchmura.com

1–10 of 46 posts

Re: Tips to Become a Better JavaScript Developer

#4
post #2

Shouldn't this be titled something more like "five things every competent Javascript developer must know"?

I wonder which title attracts a larger audience. Maybe confident developers would assume “five things every competent Javascript developer must know” would contain nothing new to them, while “5 tips to become a better Javascript developer” promises to offer something new.

Re: Tips to Become a Better JavaScript Developer

#5
post #2

Shouldn't this be titled something more like "five things every competent Javascript developer must know"?

No, because I think one of them is kind of wrong (you can be competent and still use jQuery) and three of them are better off replaced by "use jshint".

Also, you'd be surprised how many otherwise competent javascript programmers don't understand this and simply avoid it most of the time. Heck, I wrote some pretty ridiculously awesome (and robust) stuff without really understanding this, and it's quite possible someone telling everyone they need to understand this, doesn't.

Re: Tips to Become a Better JavaScript Developer

#8
I dislike when people say that good developers don't use libraries like jQuery. The main reason I use them is because I'm lazy. I'd much rather write $("#id") than document.getElementById("id"). I rarely write any javascript code that is so resource constrained that the extra time added by jQuery is not acceptable.

Re: Tips to Become a Better JavaScript Developer

#10
post #5
post #2

Shouldn't this be titled something more like "five things every competent Javascript developer must know"?

No, because I think one of them is kind of wrong (you can be competent and still use jQuery) and three of them are better off replaced by "use jshint". Also, you'd be surprised how many otherwise competent javascript programmers don't understand this and simply avoid it most of the time. Heck, I wrote some pretty ridiculously awesome (and robust) stuff without really understanding this , and it's quite possible someo…

99% of the time I can, I avoid this. Only use it when it's the cleanest way to do something... Avoids a few headaches. Of course, this is also helpful, and when it is, it's great.
Post reply on HN