I’ve worked in operational environments over the years as a systems administrator.  When I worked at IBM one of my responsibilities was ensuring uptime for the semiconductor design environment in Austin.  One of the most valuable lessons I learned there was about panic.

Downtime in that environment could cost millions (the rough planning figure I used was in the vicinity of a quarter of a million dollars an hour in lost productivity with the first 15 minutes of the outage losing between 4-24 hours of work.  Lots of money was on the line, and I had plenty of senior management at IBM regularly telling me how criticial it was.  I even got a phone call once from the VP in charge of the Server group to let me know how critical uptime was for a particular chip build.

Needless to say, in that environment it would be easy to panic.  Most times I didn’t because I had a strong team backing me.  The few times I did panic were very instructive.  Here are some of the lessons I learned:

  1. Panic will not make the solution better.  It usually prevents the solution.
  2. Panic will not get anything done any sooner.
  3. Choices made while panicking will almost universally prove to be the wrong ones.
  4. Panic immobilizes.
  5. Panic equals FAIL.

Panic is what I see going on with the bailout.  We don’t know what to do, so we gotta do *something*.   And we do need to do something.  But does it need to be so panic driven?  What will change between today and tomorrow that will make such a huge difference?

Bold and decisive action does need to be taken, but it should also be deliberate action, not the panic driven need to do anything to show we are doing something.

Rudyard Kipling (under read in our politically correct society said this:

If you can keep your head when all about you are losing theirs and blaming it on you; If you can trust yourself when all men doubt you, but make allowance for their doubting too; . . . If you can meet with Triumph and Disaster and treat those two impostors just the same . . . yours is the Earth and everything that’s in it.

We forget this to our peril.

Blog Traffic Exchange Related Websites one

Just as I am about to embark on learning OpenSer for work, the project forks.  What a pain.

Apparently, the mainline fork is now known as http://www.kamailio.org and the other fork seems to be just one of the founders at http://www.opensips.org.  I’ll probably stick with Kamailio for now.

Blog Traffic Exchange Related Websites
  • Click for pronunciation keyWhat is a Legacy? Are you at the top? Does that feel heavy when you ask yourself, what impact are you having on the culture, attitude, thoughts, mind, social influence, future behavior, etc. on others? As I approach mid-life...
  • blog traffic exchangeBoot Linux Over HTTP With boot.kernel.org (BKO) Bookmark this category    Boot Linux Over HTTP With boot.kernel.org (BKO) This tutorial shows how you can boot Linux over HTTP with boot.kernel.org (BKO). All that users need is Internet connectivity and a small program...
  • blogwritingHow to Increase Traffic to Blog There are a myriad of different ways that you can learn how to increase traffic to blog. Some of them are really straight forward and easy to implement, and others will take time and effort...
none

So one of the things I splurged on for myself is an AlphaSmart Neo.

I like the fact that it is very light, portable, and doesn’t connect to the internet.  It doesn’t have any distraction potential.  I can just write.  Plus, it will be hard to edit more than a sentence or two back, which should help keep me from letting the evil bastard who wants to keep me from writing internal editor out.

Blog Traffic Exchange Related Websites none

Categories

Blogroll

Amazon Links