I re-designed my blog again; the last time I wanted better readability and more focus on content. And this time it is no different, again I wanted the experience on my blog to be about the content. It should be easy to read and no distractions.

This is an extract from the talk “Software Development is not a Jenga game” Republished from 16 May 2009 because I had some requests for it.

Today I wanted to explain someone what I learned a while back on a course “Software G Forces” with Kent Beck in Bergen Norway about deploying software. Going from yearly to monthly to weekly to daily and finally to hourly and perhaps even continuous deployment of software takes a lot of discipline and good techniques to get right. One of the difficulties is that when you deploy your software very often you will possibly have features that are not yet completed in each deployment.

I recently introduced you to Client Express where I explained that the goal is to copy the API of Express (Node.js) but for use on the client. This will enable you to share code between the server and the client, specifically the routing.

I have been very intrigued by Node.js since I heard about; just think about it, using JavaScript on the client and on the server as well. How cool is that. But I have never really done anything with it, that is until Heroku announced their Node.js support. I know it is a weak excuse but I just can’t see myself maintain an other server. I have had my own server from about 2000 till about 2009 which is when I got into Ruby and Heroku. Since then I just don’t see the benefit of doing it myself for my own projects (different for big production systems). It means less freedom but also less headaches.