Starting with the control/data plane concept, I broke apart the cloud into multiple planes and then focused on how the layers would communicate to enable a cloud management platform that inherently scaled in and out as well as up and down.
Now that the team is armed with new weapons, it is time to help the Scrum Master to fight back. If you didn’t read my first post on this topic have a look at the 10 things a Scrum Master can do to drive the team crazy blog post I wrote two years ago. Here we go:
Some time ago, I started a hobby project: writing a new operating system. I’m not trying to create a concurrent to Linux, I’m just trying to learn some more stuff about operating systems. In this post, I’ll describe the boot process I’ve written for this operating system.
After upgrading from Apache 2.2 to 2.4 in a Windows development environment, all my virtualhosts stopped working. I could add syntax errors to the files which would make Apache refuse to start up, or get notices about invalid document roots, but the virtual host server names just wouldn’t catch on.
In my opinion a deployment of any application should be as automated as possible to avoid errors due to manual mistakes. This is no different with a Mule ESB application. This instrument makes the governance of the deployment of your Mule applications into different environments easier and therefore the whole deployment cycle less error-prone.
This is intended as a bare-bones intro to saving for retirement, targeted at software engineers. Ballpark, you make about $100k a year in your 20s. If you want to have that same income in retirement, you need about four million dollars saved up.
MySQL is designed for lightweight connection creation. Therefore, you may not use connection pooling. However, if you are a connection pooling fan (Java and Ruby devs, please raise your hands), don't forget to configure the MySQL for that:
We Agile practitioners are probably less thrilled by these New Year’s traditions. We have been desensitized by countless iterations kicking off with commitments and coming to a close with retrospectives. Our cynicism toward a Waterfall approach most likely makes most of us jaded about these end-of-the-year festivities. Or maybe not?
I was recently asked for advice on how to go from two week sprints to one. The conversation was one I've had several times. Client: "We are a scrum shop that has two week sprints. We'd like to release faster. Any suggestions?"
I’m currently having a lot of fun experimenting with node.js using IntelliJ IDEA. I installed the node.js plugin, and although this added options to create a new ‘Boilerplate’ or ‘Express’ project, the rest of the node.js integration wasn’t quite so obvious…
Managing energy is more important than managing time. Energy is what gets things done, and time is only a crude surrogate for energy. Instead of only looking at what you could earn per hour versus what you could hire someone else for per hour, consider the energy it would take you to do something versus the energy it would free to delegate it.