One problem people face when starting out with Node (and Javascript in general) is handling the asynchronous, deep callback nesting issue. EventEmitters help fix that.

Continuing on with building out a NodeJS app with Express and other buzzwords - I decided to build out a page using my API, while I build the API.

The best way to build an API is to use it while you're building it. At least that's what I find the most effective. But how am I going to consume this API?

Mongo is installed, our data is ported. Time to roll together our first model: the Customer. How do you model this stuff with MongoDB and Node?

NodeJS has a pretty specific convention when implementing callbacks in modules - function(err,result). Does this always make sense?

The data has been rolled into MongoDB - at least the first round - and now I need to get the API up and tested.

I've chosen to use MongoDB - now what?

I love learning in the open. The simple process of relaying what you see/do/think/learn/fear/love can, itself, be illuminating. So here we go again - I'm going to fuddle around live, with some edge technologies, and you get to laugh at me.

Rails 3.1 and beyond has the asset pipeline. Node has connect-assets, and there are plenty of "Just In Time" CoffeeScript compilers out there for other platforms as well. I like using a File Watcher - and here's my code.

I've always marveled at the geeks who can write good, clean Javascript. Not jQuery - Javascript. I've never cared much for the language - but my mind has been changed with all the great stuff coming out.

This was a multi-day bug with 10 deployments behind it. I was tired, frustrated and hateful of the incessant problems Internet Explorer brings to the world. I was about to give up. To hack in Yet Another IE Workaround, when I noticed something strange in the response headers...

Good Lord Above I am going out of my mind with these "tutorials" that murder javascript at the alter of KnockoutJS. It's a dandy little tool - one that apparently leads people to get drunk on HTML Markup, causing them to puke javascript out their noses and into their examples.