Books (free): - Javascript Patterns https://shichuan.github.io/javascript-patterns/ https://shichuan.github.io/javascript-patterns/: Good for wrapping your bra

Books (free): - Javascript Patterns https://shichuan.github.io/javascript-patterns/ https://shichuan.github.io/javascript-patterns/: Good for wrapping your brain around scoping and how things flow in JS. It's a very nimble language. While you won't use every single one, internalizing their concepts are central to be efficient in wrangling JS and reading other's. - Patterns For Large-Scale JavaScript Application Architecture https://addyosmani.com/largescalejavascript/ https://addyosmani.com/largescalejavascript/ Docs / Articles: - Callback functions: https://developer.mozilla.org/en-US/docs/Glossary/Callback_function https://developer.mozilla.org/en-US/docs/Glossary/Callback_f... Absolutely mandatory. - Currying: https://www.sitepoint.com/currying-in-functional-javascript/ https://www.sitepoint.com/currying-in-functional-javascript/ - 'return this' for method chaining: https://schier.co/blog/2013/11/14/method-chaining-in-javascript.html https://schier.co/blog/2013/11/14/method-chaining-in-javascr... Annotated Source: (soak these in 10-20 minutes every day over a month or two) - http://backbonejs.org/docs/backbone.html http://backbonejs.org/docs/backbone.html - http://underscorejs.org/docs/underscore.html http://underscorejs.org/docs/underscore.html Frameworks: - None. Webpack 3 + jQuery + babel + pjax Tips: - The longer you hold off on a framework, the better. Focus on getting your stuff out the door, test coverage + CI feedback loop, core business data schemas, and trimming off technical debt. After a couple of iterations and months of stability, consider a/b testing a framework. - Most libraries are still in ES5. Wrap your brain around ES5 is a sure thing. Not everyone is using newer JS features. - In many programming languages in your webstack, you're likely going to be dealing with node for build utilities and compilation. - Webpack, while it seems unintuitive at first, can be pretty nice once you get over the hump. It's like a miss of the old r.js configs and the declartive-ness of grunt. - As a parting note, don't feel a necessity to buy into single page application and frameworks. They're a tremendous time sink and the ROI just isn't there.