Traditional TDD dicates that you write code like this:
In practice, the TDD process doesn't always work out. You might waste too much time writing tests that don't actually matter. You might spend too much time mocking data. You might not actually know what test to write.
There's not a developer out there that hasn't been bitten by JavaScript's pass-objects-by-reference nature. Oftentimes developers will attempt to empty an array but mistakenly create a new one instead:
var myArray = yourArray = [1, 2, 3];
// :(
This is a thought exercise. Nothing to be taken seriously. I'm not a serious node programmer (yet), and I'm still relatively new to functional programming. But, I'd like to look at some common node patterns using callbacks and apply funtional programming techniques to them. Some of these exercises might seem impractical or contrived, but the point is learning. Seriously, I'm very new to this. Please be forgiving if I make a stupid mistake, but also let me know. :) Let's have some fun!
The examples are derived from Andrew Kelley's article here.
This is directly from Andrew's post:
Chaining in javascript can come in many forms. Here, I'll discuss method chaining, lazy chaining, and pipelining. My aim is to help me, and maybe you, understand these chaining options. This gist is inspired by Michael Fogus's O'Reilly book 'Functional JavaScript.' Like Fogus's book, I'll assume use of underscore.js as a supplement. If you're interested in functional programming in javascript, I highly recommend Fogus's book.
What do I mean by 'chaining'? Let's look over a quick example just to be on the same page. This example uses underscore.js's _.chain method.
function findFruitCosts(groceries) {