r/javascript • • Jul 11 '17

help What 10 Things Should a Serious Javascript Developer Know Right Now?

I'm inviting pure opinion here, but what's your list of ten things that everyone looking for a good javascript role should know and understand. Personally, I'm in a role where what I know is adequate, but I want to be somewhere better; somewhere that has some flippin standards. I'm learning outside of work requirements at the moment, but there is so much shit to learn out there.

The objective is to do good work in a good place.

Narrow it down to your ten for me, or for you.

Can be your own "I must learn x" list too. I'm very interested to hear what people think.

348 Upvotes

223 comments sorted by

View all comments

1

u/[deleted] Jul 15 '17

I'm one of those weirdos that limits myself to native javascript (entirely for web development and big databases). The use of external tools can be very helpful for some purposes, but a person can pour a lot of time into learning them. That time might be better spent learning alternative languages more suited to purpose.

I realize that as a non-commercial JS programmer (with copious experience non-scripted languages), I have more 'time luxury'. But over the past 7-8 years (starting with ES5) I haven't found much that's 'too hard' for native. And most of the additions to ES6 were 'nice' but not all that essential.

1

u/[deleted] Jul 17 '17

I know what you mean, I already know javascript, and 9/10 times I think I just can't be arsed with a lot of the new stuff.

I never bothered with Coffeescript, and it looks I'll probably start using Typescript soon, as it's a superset of ES6 with a few bits about strong typing bolted on top. To that extent, it has an eye on the coming standards, but it isn't full of cute, clever nonsense, and isn't "javascript for people who don't like javascript" like Coffescript and a few others are.

In terms of features that are actually needed to benefit the user, HTML5 APIs are far more commonly of benefit than any ES6+ features.

1

u/[deleted] Jul 18 '17

Over the years I was more than 'once burned twice shy' by a lot of specialized environments (particularly proprietary ones). I invested a lot of time in learning and developing stuff in them, and then they were abandoned. So now I tend to stick closely with widely-used, close-to-native-as-possible stuff, and keep my data as portable as possible ... all text.

Look like native JS will be around as long as I'll need it !