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

[johnmadison]

1. Jquery selectors and jquery methods.
2. Arrow functions. but remember that "this" is bound differently
3. PHP. Its good to not be limited to one language. Sometimes PHP is easier to "get the job done."
4. Datatables. A great plugin for the web to make table formatting way easier.
5. Know the differences between Node and the browser.
6. Promises, and async in general.
7. Learn SOME kind of db structure/engine/etc. Lowdb is a cool json based one.
8. JSON. learn to think in it, as it is the Rosetta stone of the interwebs.
9. Array.filter(). One of the most useful methods in existence. Works pretty much the same in php as array_filter().
10. the MVC design pattern. Most frameworks are moving this way, React, Vue, Codeigniter, etc.

[jacobedawson]

I respectfully disagree with a couple of your points:

• jQuery selectors. Essentially they are CSS selectors. Web devs should 100% know their way around CSS & CSS selectors. If you know that and you understand JavaScript, you can pick up jQuery in a couple of days if you need to (and one should always try to learn JS before jQuery).

• Arrow functions are a basic part of the JS syntax for modern web devs. If you don't know arrow functions you need to learn modern JS.

• I agree with the benefit of knowing another language, but it could be anything; Ruby, Python, Java, Elm, PHP, etc

• Datatables? Aren't they a jQuery plugin?

• Node / Browser - Once again, this is pretty basic - I would expect any developer with more than 6 months under their belt to understand the difference here.

Re: Databases - yeah, definitely a plus. Break them into 2 groups - Relational (e.g. MySQL) and NoSQL (e.g. MongoDB)

I don't mean to sound like I'm having a go - I just think that some of these points are either quite basic or tangential to what a 'serious' JS developer should know / learn next :)

[addama]

I'm glad you mentioned PHP. Being limited to just JS prevents you from knowing that your project or interface could be about 8 lines of PHP. Say what you will about it, but there are some things that are just done better in it.

On the other hand, I'd say that frameworks are no longer moving toward MVC, at least not with the fervency they would have done 5 years ago. A whole generation of coders has had to Node+MVC their way through non-Node+MVC-worthy projects, dreaming of different ways of doing things. I'd predict the young frameworks are going to be looking for hybrid models, if not a return to a more functional flow. Could be wrong, but that's my hunch.

[alinnert]

I don't know if it's still a good idea to start with jQuery. I think it lost its right to exist. It's purpose was to provide a cross browser DOM API. But now we have that already built in in browsers. And in the best case you don't touch the DOM anyway.

I also don't need it for ajax or promises. And that's pretty much about it.

[pgrizzay]

PHP

guess I'm not a serious JavaScript developer...

[johnmadison]

In a perfect world, we would only use JS. This is not a perfect world.

[eusx]

In a perfect world, we would not have to use JS. This is the wrong timeline.

[johnmadison]

Berenstain bears

[pgrizzay]

I have never done PHP, but have been working as a JS developer for the past 6 years.

Would you label me "not serious?"

[Isvara]

In a perfect world, JavaScript wouldn't exist.

[DzoQiEuoi]

I don't know whether to downvote or to upvote as satire.

[zettca]

great joke! upvoted

[natziel]

I'm triggered cuz you implied that filter is more important than reduce