Want to show the world that you have made a conscious choice about what text editor rules them all? Check out my "I VIM" t-shirt.
UPDATE: Now you can have the sticker version as well.
Today’s CMS is ill-suited to meet tomorrow’s increased demands on contextuality and user experience. To explain this further, I held a talk about how you should see content as data.
I began using react js pretty late but like it so far. It solves a couple of problems without being a huge framework. Here are my four top reasons why you should consider it as well.
A good CMS might not always mean a good front-end developing environment. Take wordpress, which has a great admin UI, but templating with php can be a mess. In comes nodejs, which can act as a front-end server and give you access to both great template engines, great cache possibilities and much more control.
Implementing a 2-legged oauth security in nodejs is so simple, that it just takes a just a few lines of code to secure your server.
Sometimes we need our servers to do more than they can handle, at least in a short amount of time. So why not try to create a easy way to distribute the work among other servers? Even Ad hoc?
Yesterday I wrote a blogpost at 24hr.se about controlling plugwise connected appliances with nodejs. Its kind of Part II of my previous post about one of my sideprojects (to control my espresso machine automagically before I get home).
I recently started (yet another) project. I want to automatically have a warmed up espresso machine when I get home. My espresso machine (Rancilio Silvia) takes about 45 minutes to warm up, which means that I need to tell the machine to switch on when I’m on my way home from work.