| This is a mostly garbage. It doesn't even mention control flow; callbacks, promises. A big problem with JS is in part its best quality; flexibility. New and old developers need to be shown how JS has evolved to be written. I see massive code-quality and structure discrepancies in various large modules throughout the JS community and it only serves to dissuade contribution. I'm not sure if it exists, but there should instead be a site dedicated to: "JS, done right." It could outline actual best practices.
- Building, usage of precompilers
- Control flow
- Code structures
- Tests
- Everything in between Usage of precompilers.
- Browserify, for modularity
- Babel, for next-gen features and code elegance Control flow
- Bluebird, for promises Tests
- What libraries to use
- How to build tests and how the big guys do it
- Guides for complex tests Then you could introduce other somewhat subjective deviations, like CoffeeScript, other promise libraries, other control flow techniques. Describing code structures is another big one.
With the use of Babel, the example-code can feature ES6 classes which would remove a nice chunk of the confusion newbs might associate with JS's prototype system (Not to say it shouldn't be introduced). Then describe when to use each code structure. My last thought would be to link to Github repos; for example, applications in both node.js and the client, which could describe a standardized filestructure, explain build steps, introduce tests, supply a step by step guide, etc.. Then I might say that if someone makes it through that gauntlet (and everything I missed in between), they might just be a competent JS dev. |