I'm back, as promised, with 5 more Node.js development mistakes from the “hall of fame” that I've set in place. 5 of the most common pitfalls that developers (and not exclusively those new to Node.js) fall into. From getting sloppy with your testing “routine”, to taking the risk of ignoring the importance of using supervisor programs, to invoking callbacks multiple times, I've included the most “popular” Node.js errors (adding to the 5 ones from my last post) in this “hall of shame” here. So you can remain alert and careful and make the best out of your next Node.js project. Ready, steady...

Just face it: you are or have already been making some of these common Node.js development mistakes that I'm about to put into the spotlight! Especially if you're new to Node.js. For even if this high performant web server/JavaScript runtime's advantages are non-debatable: it guarantees low latency, high throughput, it's conveniently lightweight, it provides you with a heavy load of plugins for custom-building your apps with, it enables you to develop apps with two-way, real-time connections where, “untraditionally”, both the client and the server can initiate communications...