Node.js – A Revolution for Front-End to be Back-End

Node.js hit the scene a few years back and has taken off like crazy. Particularly among front-end developers. It gave them a chance to get their hands dirty on the backend without looking like fools. If you’re new to this game, don’t worry, intimidating at first, but you will get it.

Along with Node.js, NPM empowers people even more to be complete BADASS with their skills and abilities. NPM is the node package manager, much like Ruby Developers have Gems, and Python developers have Pip. Javascript developers have NPM thanks to Node.js. I will admit that when I first dived into Node.js, I was intimidated. I didn’t quite understand how it worked. I could find several good examples of Node.js in use, for local servers, no more Apache setup on my local computer – YAY.

I think majority of developers out there are still in this bucket with Node.js. They know about Express, Server, and several other NPM modules that help you use functionality of Node.js but Node.js itself is still a mystery.

Node.js is like your flour in the cake, you know it’s the most important ingredient but without the Baking Powder or sugar, it won’t be a cake. Just like when it comes to baking a cake, you can learn a lot just about flour. I recommend learning more about Node.js for any developer using it. Not just continuing to use the nicely developed NPM packages. Understanding Node.js at the core level will help you debug packages that might have conflicts and even potentially develop your own.

Some great reading material I recommend:
Node: Up and Running