Javascript refrence

Review of javascript functions

Review

Grasp javascript at a general low level of understanding

Raw DOM manipulation is good to know, but it's also unnecessary in almost all scenarios. DOM - agree with the feeling, but lost it all with the idiotic 2800 times slower comment. Really, it should have just said "learn how to do all the dom operations jQuery does without jQuery"

Good to know, but you'll probably only be quizzed on the bare basics during interviews. Just know about basic time/space complexity, linear time, constant time, hashing, stacks/queues, traversing tree-like structures, you'll probably be fine. Linked lists, other types of data structures

https://medium.freecodecamp.org/a-quick-and-simple-guide-to-javascript-regular-expressions-48b46a68df29

Formatting, Commenting, variable naming, debugging, testing, flow, a little on typescript. Learn good habits. I don't mean some fad style guide. I mean learn not to expose globals, learn not to loop over stuff multiple times when once will suffice, learn when not to do something. Learn to tune out the noise. There's lots of BS out there from people who have a lot of time to write about JavaScript, because they don't have to manage and write a lot of real code.

ESLint and Prettier, https://edgecoders.com/the-mistakes-i-made-as-a-beginner-programmer-ac8b3e54c312

How to test your application with Mocha, Chai or similar postman

Utility libraries Know about Underscore, lodash, Ramda, or something like that.

How do we go about designing the structure of a Web app, RESTful app or SPA? Flux? 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).

How to organize data in an app, in a way that allows for the fastest possible execution. Good to know, but you'll probably only be quizzed on the bare basics during interviews. Just know about basic time/space complexity, linear time, constant time, hashing, stacks/queues, traversing tree-like structures, you'll probably be fine.

The interactions imposed by JavaScript can present accessibility barriers. A serious JavaScript developer is already familiar with WCAG 2.0 and knows how to work within its recommendations or when to push back on violating business requirements. Security. You need to have at least a basic understanding of security violations, security controls, and privacy. You don't need to be a CISSP, but you need to be able to supply recommendations and avoid obvious failures. If you cannot get this right in

https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/ Perf Auditing: Putting aside standard algorithmic complexity stuff, when trying to speed up an existing application being able to use Js Perf tools is pretty important. The Chrome Dev tools have a lot available here, but take some practice and learning. Being able to discern & solve JS parse time, resource lock delays, slow JS execution, inefficient DOM interaction, and long paint triggers is a tricky advanced skill.

https://www.ecma-international.org/publications/standards/Ecma-262.htm https://www.reddit.com/r/javascript/comments/6mlc9d/what_10_things_should_a_serious_javascript/ https://edgecoders.com/the-mistakes-i-made-as-a-beginner-programmer-ac8b3e54c312

https://drboolean.gitbooks.io/mostly-adequate-guide-old/content/ Learn about functional programming and object oriented programming, learn to use the concepts. But please don't go overboard, going too far in any direction usually leads to a long trail of spaghetti. Some times things are better structured as object sometimes they're better expressed as functions. It's okay. Everything will be okay.

DevOps for your application, understanding every part of your project will make you stand out and will make you a better developer

Caching: There are multiple ways to do HTTP caching (etags vs hard expiration). A speedy web app will utilize static assets via CDN as well as live data sets. Being able to boot a web app with appropriate caching, while avoiding cache poisoning, and being able to invalidate cache or update references sanely is pretty important for performance.

Browser APIs like background sync, web payments and generally keeping on top of new things coming out

Reactive Extensions for JavaScript (RxJS) is a reactive streams library that allows you to work with asynchronous data streams. RxJS can be used both in the browser or in the server-side using Node.js.