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

CODODN: What's New in the ASP.NET 3.5 Extensions: Resources

Thanks for attending my presentation. Resources I referenced: .Net 3.5 Enhancements Training Kit Download Overview of ASP.NET 3.5 Extensions Preview ASP.NET 3.5 Extensions Preview (unrelated) Central Ohio Application Lifecycle Management Group: COALMG Update 4/22/2008 : Props to Dan Hounshell for finding this CODODN video . I'm in there 2-3 times. Nice!

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft