I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages
• Package.json is a mighty tool
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as a framework and test runner
• Should is a nice way to do asserts - this post
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an API

This post is about an assertion framework that I’ve come to love:...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages
• Package.json is a mighty tool
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as framework and test runner - this post
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

When it comes to testing frameworks on the JavaScript and Node...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages
• Package.json is a mighty tool
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them - this post
• mocha is cool both as framework and test runner
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

This is not Node related but rather a Javascript...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages
• Package.json is a mighty tool
• Git is not that hard, but I need to refresh my knowledge - this post
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as framework and test runner
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

This post is not at all about Javascript or Node. But...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages
• Package.json is a mighty tool - this post
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as framework and test runner
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

This post is about the package.json file that is...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all
• npm is not only for getting packages - this post
• Package.json is a mighty tool
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as framework and test runner
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

This post is about the Node Package Manager, npm, and some...

I’m writing down some of the things I’ve picked up when I started to learn about Node, Express, and Mongo. Here are all the posts in the series:

• Doing stuff in the terminal is not scary at all - this post
• npm is not only for getting packages
• Package.json is a mighty tool
• git is not that hard, but I need to refresh my knowledge
• Callback function is cool stuff, and I even know how to write them
• mocha is cool both as framework and test runner
• should is a nice way to do asserts
• monk is an easy way to access mongo
• Express is best without generators
• supertest is a nice way to test an api

This post is about the terminal and how I...

I have been playing with NodeJs during the evenings. Really late onto that train, but here we are. In fact, this is just by coincidence; I happened to bring “JavaScript - the good parts” to Indonesia and it was the only book I had. Once I had read that awesome book, I got invited to write a review for the NancyFx book by Christian Horsdal and got a free book for my effort. I just picked one and it happened to be Mastering Node.js.

After that book and my head had stopped spinning, we still had to wait for our belongings to arrive in Indonesia. I had nothing to read or code. So I thought I would put my Node-knowledge into action and started to check out Express.

Here we are. I haven’t really coded anything real, but rather read, labbed, and followed...

REPOST FROM CODEBETTER

I noticed that CodeBetter is slowing down. Maybe dying. I’m preserving my original post from there, here on my own site.

Original post

We had set the system up for a test of how this A/B testing stuff could work for us. Would it be useful? Could we communicate it clearly to the others around us? Would the data be easy to understand and make something out of?

From http://www.mikebilleter.com/2009/08/impossible-captcha.html

In order to know what we where doing we picked a no-brainer feature to test it on: registration with or without CAPTCHA. You know, like the one to the left.

Since all of us (and probably you too) hate to type those strange, unreadable letters we were confident that we knew which one would win. Hence we had some really good test data for how...

I’ve started working in a very different organization, in a very different culture, and I see the same problems. For those who don’t know yet, I have moved to Indonesia and work for Bala Keselamatan, better known internationally as the Salvation Army. My task is to help the organization that oversees the Salvation Army hospitals (yes, 6 of them) and clinics (17, I think) become more effective and get more done with less. “Doing the most good,” in other words.

When I came here, I hoped (or maybe bet) that my knowledge of Lean and Agile would be helpful. I’ve seen similar problems here as I did with clients back home. In this blog post, I want to discuss one of these problems: long lead times in important projects.

Yes, I wrote “important” projects. It really stumped me at first. But then I realized that I’ve been in...