r/javascript • u/[deleted] • 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
7
u/HeathenForAllSeasons Jul 11 '17
This is pretty close well right on the money.
All the other threads about ES6, React and ASM are way off. Sure, ES6 adds some great features but the entire Babel toolchain is temporary by its very nature. Some serious projects may yet not use it and that's fine. ES6 won't save you if you don't understand scope or architecture.
As for ASM and React, sounds a bit like a No True Scotsman fallacy. To be serious, we should know your flavor of the month?
To elaborate on the point about scope and architecture, you HAVE to know your design patterns in JS. There's no way around it. You must know Pub/Sub, Revealing Module Pattern, Currying and others. You really should know how to hand-roll a Tightly Augmenting Module Pattern across multiple files. (it's how your favorite frameworks handle their DI magic).
Understanding the mechanics of these types of patterns and how/when to use them sets you apart from non-serious developers.