Skip to main content

CIO: What Will You Do When the Cyber-Levee Breaks?

What would you do in the event of the failure of the Internet?

I used to think about this kind of thing more often but maybe I've become too accepting of the distributed nature of the Internet as a safety measure. This article got me thinking about an EMP pulse or a small nuke knocking out a major portion of the Internet...say a few backbones in Chicago or something. Not having an Internet connection often brings my work to a complete halt...let alone operations at most businesses.

I'm growing weary of complete communication failures during traumatic homeland events: 9/11, Katrina, etc. Shouldn't local or state government contract with private industry to get satellite phones to major incidents within 4-6 hours? I mean, how hard can this be? C'mon. Or portable Wi-Fi / cellular towers. Whatever.

Technology aside, I think the bigger problem is lack of leadership. The average person lacks a sniff of a clue about what actions to take during a crisis situation. Politicians, who typically assume "control" during a crisis, are arguably the very worst folks to be in charge. They spend their careers assuaging constituents and trying to keep office rather than getting things done, organizing projects, and leading people.

I think we should train and maintain a network of "incident commanders" within our cities. These folks would know how to re-establish communications, would be aware of all their resources, would have ties to the federal government but would be based locally, and they would know how to lead people and solve problems. They wouldn't necessarily assume control but would work with local government to truly manage the crisis.

Rudy G. performed brilliantly during 9/11 but only because he had consciously put himself through leadership and contingency planning for years prior. We need more folks with leadership talents on the front lines during major incidents and we need to better utilize the smart folks and advanced technologies at our disposal.

Comments

Popular posts from this blog

TFS Reports Out of Date

You may have noticed it takes a while for Team Foundation Server (TFS) reports to reflect changes you've made to work items or builds. Let me guess...about an hour, right? Out of the box, TFS is set to refresh the data warehouse from its transactional store every 60 minutes. How do I change the frequency of the data warehouse refresh? Browse to the TFS Controller Web Service on your TFS application tier server within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx Select the ChangeSetting option Enter RunIntervalSeconds for the settingId and the desired number of seconds for newValue (300 for 5 minutes...5*60) Select Invoke How do I force a data warehouse refresh? Two methods here: either via the above web service or using SQL Server Management Studio. Via the web service: Browse to the TFS Controller Web Service within IE at: http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx Select the Run option Click Invo...

VSTS Tester Demo Follow-ups

Last week, I delivered a VSTS 2008 Tester Edition demo to a prospective client. Following up on a few questions to which I didn’t know the answer: Q. Can I use Subversion with TFS? A. I get this question all the time from developers. It’s a perfectly valid question. The answer is no…but yes…sort of. The version control repository (and all data) must remain SQL Server. Yes, it’s proprietary. Further, if you plan to use TFS in your software development environment, but choose not to leverage it for version control, it severely limits the usefulness of the information elicited from TFS (because you’re not feeding in the crucial VC data). If you’re not leveraging VC in TFS, you’re probably not leveraging Team Build either. That said, while a fully-integrated TFS for ALM and SCM is the ideal, there’s a compelling argument to leverage TFS as a repository for requirements, scenarios, test cases, functional and load testing as well as defect tracking. TFS is an excellent repository to s...

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...