Read about the basics of Node’s Require and Exports: http://openmymind.net/2012/2/3/Node-Require-and-Exports/ (Links to an external site.) http://www.sitepoint.com/understanding-module-exports-exports-node-js/ (Links to an external site.) Dive deeper into exports: http://bites.goodeggs.com/posts/export-this/ (Links to an external site.)    Read about CommonJS: http://dailyjs.com/2010/10/18/modules/ (Links to an external site.)   Read about modular Javascript, especially the section on CommonJS: http://addyosmani.com/writing-modular-js/ (Links to an external site.)  Read NodeJS Require best practices: http://www.mircozeiss.com/node-js-require-s-best-practices/ (Links to an external site.)  Video on the same topic: https://vimeo.com/89258863 (Links to an external site.)  Read Preface, Chapter 1 and 2 of Testable JavaScriptPreview the documentView in a new window by Mark Ethan Trostler A shorter blog series, read all four articles, up to the one on coupling:  http://www.innoarchitech.com/scalable-maintainable-javascript/ (Links to an external site.)    Read Chapter 1 of Clean CodePreview the documentView in a new window by “Uncle” Bob Martin Read Clean Architecture by Uncle Bob: http://blog.8thlight.com/uncle-bob/2011/11/22/Clean-Architecture.html (Links to an external site.)   Create an app that demonstrates you know how to use modules AND includes a has-many relationship.  For example, write a command line script or (small) express app that has two related resources like classes and students.  In a has-many relationship, a student could have many classes, or a class could have many students. Your app should print out or visualize that relationship.  The app should also use clean, modular code. Use module.exports. Follow the separation of concerns principle. Have each resource in a separate file. Use JSHint and JSCS to check your code style.  Submit a PR to your own repo.