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
6
u/alinnert Jul 11 '17
This reminds me of the people who say Webpack is way too complicated. And I'm like: Here's my entry file, there's my output file, these are my loaders. And it works. Hooray!
I totally understand that you can gather bad experiences if you stumble over tutorials you don't get or get errors by reading the wrong part of the documentation or whatever. But that doesn't make the products bad.
I made bad experiences with RxJS, but I know it's my fault since other people can use it.
I use Webpack and Babel in almost every project and they just work. No problems here. And yes, they do help me. Namely organizing my project files, shorten my code and make it slightly more readable.