Delivering services over the web requires building software that is suitable for deploying to an environment that allows for scaling up without significant changes to the application itself. It should allow businesses to take advantage of high[...] Returning errors in the first argument of a callback works great in the simplest of examples, but the further you go down that path and the more code you write it quickly becomes apparent that it's not maintainable and should be handled differently.[...] It comes from the best intentions, and we've all seen it before. The business has a need, a project is started, developers are hired and given a rough set of specs that outline basic functionality and they get to work crafting HTML & CSS to make[...] We've been developing solutions with Node.js for a couple years now and once you wrap your head around a few simple concepts, going back to anything else feels like work. Before getting into details, lets talk about a few key points.
Node.js is not[...] I've heard plenty of developers talk about how being "lazy" has pushed them into using build scripts, but that's not being fair to the value that can be achieved from a good build script. It's not about being lazy, it's about being smart. The[...] When we talk about software project estimates, a section on Testing is usually the first one to take some heat.
While the argument could be made that the necessity of software testing on small project is be less than that of a
large project, it's[...] 
The Twelve-Factor app Methodology
NodeJS - Best Practices Error Handling
Guidelines for a Great API
Introduction to Node.js
Grunt tips
Software Testing and Quality Assurance