Skip to main content

2009 Year End Summary

I started out 2009 insinuating that hardware isn't always cheaper than programmers. That post attracted scant attention until a few months later when it showed up on Dzone, Ycombinator and Reddit.

Apparently annoying programmers is one way to attract attention to your blog.

This ended up being a demonstration of the short  attention span of that type of social media. The flurry subsided within a day or so. I'll admit that I took screen shots - just in case I don't get the other 14.5 minutes of fame.

One thing I disliked about the link-ins from those services is that the comments and discussion took place largely in the social media services rather that on the blog.

Similar attention was given to posts on Resume building consultants and Continuous Deployment. John Allspaw commented on how continuous deployment is used at Flickr. Forget the post. Read the comments.

In Cargo Cult Systems Administration I attempted to describe cases where system administration might really be cargo cult.

I'm pretty paranoid about privacy. It's not  hard to see where we are going with privacy (or the lack thereof).

Other potentially interesting posts from 2009:
Throughout year 2009 my 2008 availability and structure system management related posts seemed to do quite well also:
As in 2008, I also attempted humor. As with 2008's attempt, the 2009 humor attempt also failed.

Popular posts from this blog

Cargo Cult System Administration

“imitate the superficial exterior of a process or system without having any understanding of the underlying substance” --Wikipedia During and after WWII, some native south pacific islanders erroneously associated the presence of war related technology with the delivery of highly desirable cargo. When the war ended and the cargo stopped showing up, they built crude facsimiles of runways, control towers, and airplanes in the belief that the presence of war technology caused the delivery of desirable cargo. From our point of view, it looks pretty amusing to see people build fake airplanes, runways and control towers  and wait for cargo to fall from the sky.The question is, how amusing are we?We have cargo cult science[1], cargo cult management[2], cargo cult programming[3], how about cargo cult system management?Here’s some common system administration failures that might be ‘cargo cult’:Failing to understand the difference between necessary and sufficient. A daily backup is necessary, b…

Ad-Hoc Versus Structured System Management

Structured system management is a concept that covers the fundamentals of building, securing, deploying, monitoring, logging, alerting, and documenting networks, servers and applications. Structured system management implies that you have those fundamentals in place, you execute them consistently, and you know all cases where you are inconsistent. The converse of structured system management is what I call ad hoc system management, where every system has it own plan, undocumented and inconsistent, and you don't know how inconsistent they are, because you've never looked.

In previous posts (here and here) I implied that structured system management was an integral part of improving system availability. Having inherited several platforms that had, at best, ad hoc system management, and having moved the platforms to something resembling structured system management, I've concluded that implementing basic structure around system management will be the best and fastest path to…

The Cloud – Provider Failure Modes

In The Cloud - Outsourcing Moved up the Stack[1] I compared the outsourcing that we do routinely (wide area networks) with the outsourcing of the higher layers of the application stack (processor, memory, storage). Conceptually they are similar:
In both cases you’ve entrusted your bits to someone else, you’ve shared physical and logical resources with others, you’ve disassociated physical devices (circuits or servers) from logical devices (virtual circuits, virtual severs), and in exchange for what is hopefully better, faster, cheaper service, you give up visibility, manageability and control to a provider. There are differences though. In the case of networking, your cloud provider is only entrusted with your bits for the time it takes for those bits to cross the providers network, and the loss of a few bits is not catastrophic. For providers of higher layer services, the bits are entrusted to the provider for the life of the bits, and the loss of a few bits is a major problem. The…