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

Show parent comments

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.

19

u/alinnert Jul 11 '17

(...) the entire Babel toolchain is temporary by its very nature.

No. As long as ECMAScript is actively developed on, Babel serves a purpose. Babel doesn't transpile ES6 to ES5 but future proposals and new final features to code that's interpreted by most widely used browsers at the given time. That's why it was renamed to Babel after all.

If I didn't get your point please let me know.

-16

u/zayelion Jul 11 '17

Maybe you just shouldnt code with Babel, its edge enough to cut you.

3

u/alinnert Jul 11 '17

After writing my comment I noticed a mistake: Babel doesn't transpile anything. It's fueled by plugins. So it can even be used to transpile JSX or TypeScript or whatever the future might bring. There also are plugins for minification. So I wouldn't be surprised if there are some that do performance optimization and what not. So it's extremely versatile.

-10

u/zayelion Jul 11 '17

I've only seen it complicate shit in the field. Its highly misused and needed to fix problems which shouldn't exist.

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.

-3

u/zayelion Jul 11 '17

Im getting at when people use layers of frameworks on top of each other. A leftpad situation. https://github.com/webpack/webpack/issues/1914

After 8GB it should compile right? well why are you compiling, because typescript, well why are you using typescript, because I need type... no learn ES6 proper.

Webpack is a good tool, Im not saying that it isnt.

8

u/liming91 Jul 11 '17

If you think TypeScript is some sort of handicap for not knowing ES6 properly then you have some serious misconceptions about ES6 and TS.

1

u/zayelion Jul 11 '17

I've just seen it used or maybe miss used in the field that I've mentally labeled it a code smell.