Wednesday, March 17, 2010

Blog activity temporarily suspended

Due to beginning a move from the Cincinnati area to Scottsdale Arizona, my writings are temporarily suspended. Most, if not all of March will be taken up by activities related to the move.

You may still see some activity on my Twitter account, but I don’t have time for much more than 140 characters at a time.

On the bright side, I’ll soon be a resident of an area of the world that is home to palm trees and cacti. Everyone should experience that at least once.

Monday, March 15, 2010

“Remember when every business had their own SysAdmin(s)?”

I.Fix.it.cropped

Do you think that sentence will ever be uttered? If so, do you think you’ll hear it in your lifetime? In your career?

According to a recent CIO article titled “Cloud and the Death of the Sysadmin”, the answer to each of those questions may very well be “yes” (unless you plan on retiring in the next few months). The cloud is the reason.

In the article, sysadmins are analogized with car mechanics of old. Back before cars didn’t need software updates and laughed in the face of a potential EMP “event”.

There was a personal touch and much lore and insight that mechanics had. A bit like Systems Administrators today. Journeyman programs prepared young grease monkeys to become arch mechanics much like Jr. Admins (or PFYs if you prefer) are ideally mentored by an experience admin in the nuances of administration.

Fast forward to today. According to the CIO article, the average high-end car has more lines of code than the Windows 7 and that codebase is distributed over more computers than a small office has.

Mechanics can no longer turn a wrench or replace a hose to fix many problems. They resort to rip-and-replace tactics for various microcomputer components (called Electronic Control Units or ECUs) because they don’t know what else to do. Half of all replaced ECUs show no signs of errors.

Apparently automobiles are now so complex, that remote support technicians will soon be who mechanics turn to for diagnostics. It is intelligently hypothesized that cars will be connected to a network and remotely diagnosed by highly skilled and specialized technicians. Those techs will then tell the mechanic what parts to replace.

A ever increasing disparity in skill will exist between the highly specialized remote worker and the local “mechanic” which will become little more than the hands for the remote tech. Maybe a few local mechanics will be kept on to do physical tasks like changing oil or rotating tires. At least, until that’s automated with arms that are similar to those seen on factory floors.

The generalist mechanic will become a relic. Any current-day specialist skills will become obsolete. We may no longer need a transmission specialist any more than we need switchboard operators today. Those displaced mechanics may find satisfaction in restoring those old cars that served their career so well, but they will no longer have a job working on a modern fleet of vehicles.

Change the story to focus on SysAdmins. The older automobiles change to private server room. The new autos to the cloud. The applications and services to the increasingly complex individual components or ECUs.

According to the CIO article, application complexity is increasing and troubleshooting is becoming harder. Specialized skills are needed for each service that an IT department is required to render and maintain.

The article continues the conjecture and considers a future where finely honed specialists for each service will be centralized and will service the applications that are being delivered. Onsite personnel are now only there to handle physical tasks for the service’s required onsite hardware.

Visions of a Googler walking through a non-descript server isle with a shopping pulling out bits of failed hardware from servers comes to mind. Even that scenario is old fashioned when you take into consideration the new datacenter pods that are never opened by humans, but simply get replaced wholesale when a certain percentage of hardware failure is reached.

The jack-of-all-trades (and if he’s especially amazing, master-of-some) SysAdmin has gone the way of Car Hops and Lamplighters. Maybe they’re needed in third world countries or in a themed Old Tyme amusement park, but not in the Real World.

To further drive home the point, the author reminds us that skilled workmen once filled factories. Now those same factory floors have had the lighbulbs removed and are filled with robotic appendages working at threatening speeds, eerily aping human motions that our grandfathers once did. The few workers that are still employed are the ones with the highest specialization… in robotic repair, efficiency analysis and various factory systems.

Essentially, information workers.

Is this true? Will SysAdmins be a fabled creature, spoken of in the same sentence as American Wild West cowboys? Vestiges of a time before more efficient, predictable and civilized ways of handling things was implemented?

In my opinion, probably to a large extent that scenario is true. I believe that the role of the Systems Administrator will change drastically in the next 10 years due to SaaS and cloud-ifying applications. How and why that happens is a question I’m still trying to answer.

The article only mentions application complexity as a reason for the move highly specialized positions. I disagree. I think it’s a simple matter of sheer scale.

SaaS is in many ways cheaper. It is also much more reliable. Cheap and reliable… who could resist? More services will be moved offsite from a private datacenter to a cloud service. Cloud services develop and grow at an exponential rate. More and more people will be needed to run those datacenters and the individual application ecosystems on them which will be massive in scale.

The drive for specialized skills will primarily be born from positions that must manage services on a massive scale. The complexity comes as a result of scale. Not, as I believe the article is implying, that the applications themselves are becoming more complex.

Maybe I’m drawing a blurry line. However, the important part to take away is that needed skills will change both their nature and their location. Skills will become specialized and will be moved from the onsite datacenter to massive, centralized datacenters. To what degree is in question.

The article’s emphasis on the increasing gulf between those that are specialists in one thing and those with lower, generalist skills seems accurate to a point.

However, I doubt that most business will offsite a majority of their services in the near future. Maybe non-trivial amounts of it… say, 30%. I do believe that there will be a tipping point. For example, once say 50% offsiting is achieved, it seems that the remaining percentage will be easier to achieve than the first 50%.

Nonetheless, the SysAdmin’s role is changing. That change is happening now. That change is unavoidable. Instead of fighting it, we ought to intelligently prepare ourselves for it today.

When the day comes that we have to decide to become datacenter infrastructure specialists or cloud applications specialists versus being relegated to SMBs that are too suspicious or remote to support their workflows being sent to the cloud… we ought to make that decision based on rationality rather than stubbornly sticking to old ways.

"I observe that old men seldom have any advantage of new discoveries, because they are beside a way of thinking, they have been so long used to.”

--Jonathan Edwards

Friday, March 12, 2010

iPhone FAIL

Click the image to go to the Flickr original.

4426943495_ba70d50d51_o[1]

…but then again, if it supported flash it would be even slower and Safari would crash even more. So maybe it’s for the better.

Tuesday, March 9, 2010

A Flickr group for server rooms from the wrong side of the tracks

UPDATE: I fixed my borked Bit.ly link. This one should work now.


Ever been in one of those server rooms? Ever seen solutions designed by someone who could only use one hand because the other was on a chrome .45? Awww yee-uh. Ghetto IT.


Got any photo evidence of those slipshod solutions? Maybe you would never close circuits with a pair of plyers, but did your predecessor leave you with core switches powered by an exercise bike and servers propped up with broom sticks? If so, I've created the Flickr group for you: "Ghetto IT


The inspiration behind this is a thread at the SysAdmin-Network from a user named Isaac.The thread was named "Isaac? The ghetto is calling, they want their servers back." I figured that we all had our own run-ins with ghetto IT whether we were the originators of it or merely the unfortunate stewards of it.

Got anything to contribute? Want to join the group? Want to be a Thug Operator? Lemme know over at Flick-to-the-r.

Wednesday, March 3, 2010

Free eBook: The Complete Guide to Twitter

We all know that Twitter is a popular social network that has more than its fair share of criticism and parodies. However, I believe that Twitter can be harnessed by progressive IT departments for their own good. I'll explore that possibility in a future post, but until then read and digest this free 40 page PDF eBook from MakeUseOf.com titled "The Complete Guide to Twitter".


If you have an experience with using Twitter in your IT department, drop me a line to give me some ideas for my forthcoming post on the topic.

Tuesday, March 2, 2010

Let's create a groundswell at Dell!

A few weeks back, Shawn Anderson of Admin Arsenal fame posted a blog entry concerning how Dell gets one-upped by Dominos pizza when it comes to a customer's visibility into the build process. In fact, it's more than just one-upped, it's more like completely pwnz0red.

Someone took that idea and posted it to Dell's IdeaStorm website. I'm proposing that all interested admins rally behind this effort to increase the visibility into the hardware build process at Dell. It matters not whether you're an "IBM person", an "HP person" or a [insert-favored-hardware-vendor-here] person. Technical innovation and competition in any industry will (ideally) never hurt anyone.

Consider giving this idea an upvote or a downvote and share your ideas to help better the hardware industry as a whole.