10 Things a Serious JavaScript Developer Should Know?

Course I took to learn web development! $10 dollars for a limited time!

Reddit Post Mentioned in this video

Find me here

[kylerjohnson]

Erik, great video man.
I despise when people use the phrase, "You're not a real/serious developer if..." like the guy on reddit. In my experience, people who use phrases like that are narcissistic, pretentious know-it-alls who believe themselves to be infallible. They tend to limit themselves with their own ego and create work environments where people are afraid to ask questions when they don't know something. Everyone has to start somewhere and for those of you who are new to development, don't let people like this guy discourage you. You'll get there. Follow people like Erik here who push great content and you'll get there.

[kikutnik]

the main thing what js dev should know is "there is tone of stuff you dont know". trust me, i'm js dev from couple of years. i'm suprised almost every week how big is js world and how many things is in it

[bryanenid]

To be an expert on JavaScript only requires to know what tools do you need for a certain task and look for it in the docs, read and understand it, not memorize it.

Basically Logic.

And then with this, knowing how to debug requires the cycle of the code, like knowing: Closures and Scopes, this also depends of your paradigm that you are using .

These can be summarized as “Algorithms”.

This is not only for JavaScript developers, but for all developers.

[alimfuzzy]

I'm not a dev but at my work the number one thing the top devs try to do is create good tests for their code. They have written down on the whiteboard "Write the test first", meaning they should write or at least think about how to test the program before it is written. It also highlights the question of what are you trying to accomplish by creating this function. It make sense to me.

Also if you work for a government department accessibility moves up very high to be one of the most important things to know (for legal reasons).

[markthomasnoonan]

I'd disagree on the accessibility point. The upper management many not care either way, but a developer making small decisions on the implementation side can make or break the experience for people with disabilities. Developers who make software that might be used by somebody navigating with a keyboard, say, or spoken instructions to their computer, should take the basic steps to ensure these things are not broken (or made weird/difficult) by the choices we make putting the page together. If you can build up a few habits in terms of semantic html, navigation, and forms, you won't much have to think about accessibility after that. With JS, accessibility is often broken by naive choices with handling events. Stuff that works on mouseover but doesn't fire when a field is focused with the tab key, or things that run on a click handler not responding to pressing enter. It's worth taking a couple of afternoons to get some perspective on this as a developer.

[GoGroomer]

New developer here:) thank you for this info 👍🏻

[Maleficarios]

Understanding hoisting, closures, events & asynchronous code and you are pretty set, pretty much everything else can be derived from this.

[threeone]

Flash gives you front-end, Perl gives you back-end. That's full stack 2018 right there. Futureproof too.

[jasonwelsh]

Great video - you gained a fan and a subscriber. I have pretty strong Front End skills and I am struggling to get a foot in the door as a Front End Dev and looking around your channel it seems like there is a ton of excellent content for me. Thank you!

[PothOnProgramming]

I'd say that scope is pretty important. Inheritance is another big one. Also, you should know how to write clean, efficient JavaScript even though the unstructured nature of the language allows you to write very sloppy code that still works. It's not a strongly typed language, but it still runs better when you write your code as though it were. You need to know when to use the advantages of its flexibility and when to stick to a structure.

[clovisrodriguez]

What an amazing video, I'm currently starting a new job search and even I have 3 years working as a developer and I have contribute to 3 big companies projects sometimes you find some test and questions that make you hesitate about your skills and your career as a developer, I know I started working with frameworks and some things underlining this are vague to me still I feel I have done a good job and I'm capable of get job done with every requiremente, I think some companies should be more flexible about hiring developers about some skills that you will learn on demand if the project require it like state management libraries for example, great video it help me to feel better

[matomarkovic]

Well everyone can learn everything, just thing is that someone does/learns something easier then others. And the access to a problem and manipulation of certain things is that shapes the expert in certain way. That said, you come to question that defines your expertise. "You can do it, but how good and in what given time?"

[tradertube]

Interesting video and list ! Thanks for sharing!

[akhilm_cs]

Very Genuine review on the Reddit list.

[Luxcium]

I don’t agree with number 3 and 4 because I am NodeJs Enthusiast and I am not interested in DOM (I would like to be better I know more than the basics But I lack experience) I am pretty sure the opposite of my situation is true and I wouldn’t be learning NodeJS if I was a DOM lover but regardless having a basic understanding of both technology is preferable for sure but it’s also ok to specialize and master one side more than the other ...

[geneparcellano]

Designers can take care of #9 these days. I also agree that in the end it's all about the product. Does it provide a solution for a problem and does it provide great UX? When it comes to web applications, writing the best-cleanest code does not help when it doesn't benefit the user. Or, if it provides a bad user experience.

[sasayaki]

I could hear the sneer in this person's voice in my mind lol

I do agree about getting some basic accesibilty worked in. As a student I noticed people give it lip service but don't try too hard unless there's a government connection somewhere (in the US, 508 compliance). If you went to site after site and the page was a mess you would be annoyed. The docs make it seem complicated but you don't have to do a lot to get a site at least tabbable. If the docs were more concise people wouldn't ignore it so much. It's a pain in the ass reading the WACG docs but that might be my newness.

[asdqwe]

before watching the video. I would say:
testing
git
oop concepts
basic concepts of functional programming
node, and npm
webpack or similar
roughly what features work in what browsers

after watching

always try to avoid a hard problem if possible rather than spending weeks trying to solve it
learn teamwork, ask when you need and offer help when you can
security, how did I forget that :(

[davidbasil]

The title should be "Just learn JavaScript". No one should tell you about Dom and callbacks when learning js, it's given.

[xerotolerant]

Bro I think you’re getting a little hung up on what is apparently a simple ordered list. I don’t even think it’s ordered from most to least important. Also you have to know your js scope to get remotely good at it. Otherwise you’ll be sitting for hours on end debugging errors that you don’t understand.