If asked why your module isn't using Streams 2, well it makes it so much harder to use a stream as an iterative work queue. Sound SMART.
Node's error handling was inspired by getting mugged in Oakland: You're gonna die and you better have someone to resurrect you.
Our weaponized crime-fighting #nodebotsday project just up and left. “Excuse me, I have to go. Somewhere there is a crime happening” it said
Rewrite all your apps in asm.js for both performance and clarity. It’s even closer to the metal.
For #nodebotsday we’re hacking a weaponized node-powered robot to help Oakland’s failing police force fight crime. What the heck, why not?
The real problem with promises is that they’re an abstraction. This conflicts with node’s close-to-the-metal philosophy.
If someone suggests using CoffeeScript, send a Node Copter after them.
Extract each function you write into its own module. Publish it. This helps flesh out your NPM profile quite a bit.
Does an incoming request have invalid JSON? Crash the process, shut the server down, don't even bother sending them a 400 Bad Request. DONE.