I’m going to come right out and say it: Best. Ending. Ever.
Jack Hitt wrote a fabulous article in Rolling Stone last month about missile defense, made all the more fabulous because it contained information relating to a defense or aerospace project that was new to me. As they say, read the whole thing. If you’re like me, though, and have spent a significant portion of your life around computers and the open source movement, the most striking this about this article is the horror you’ll feel when you realize that the United States Department of Defense has adopted the CADT model of weapons system development.
I’m not joking. Hitt might as well have been writing about any large scale OSS project:
This kind of thinking does wonders for the speed with which you can deploy weapons. Take the shield’s interceptor missiles. In the old way of building things, a few missiles would have been built and tested repeatedly until it was clear they could reliably launch, sync up with central command, interact with radar, intercept a test missile that shrouded itself in decoys, make the necessary discriminations and blow the proper target from the sky. But under the new way of building things, all you have to do is have the whole thing worked out on paper, in simulated computer run-throughs and a few limited real-world tests. That’s why fields of interceptor missiles are already up and, in a capability-based way, running in both Alaska and California.
Of course, the “deploy now, test later” approach has its drawbacks. During a 2005 run, the interceptor couldn’t get out of the silo because the retraction arm — which hadn’t been tested properly in real-world conditions — didn’t fully retract, causing the entire system to shut down. In the old knowledge-based world, that probably would have been worked out before deployment. But in the capability-based world, each interceptor had to be removed, a new retractor system designed and installed, and the interceptors put back into the silos. …
If the old question was whether or not the technology worked — and it still has not been satisfactorily answered — there now appears to be a new question: Even if the technology is found to work, given the current schedule, will missile defense be fully operational anytime in the next half-century? …
That’s not the best part, though:
Last year, three weeks of heavy rain did what no invading army could pull off: It penetrated Fort Greely’s defenses and took out a quarter of the missiles. The silos and the electronics vaults adjacent to them were flooded — one silo was filled with sixty-three feet of water. Boeing blames the military, the military blames Boeing. According to the Missile Defense Agency, it is not cost-effective to repair the damage. Moreover, it is now considered too dangerous to work near missiles in the undamaged silos. The latest budget has a line in it to start from scratch: The government plans to build a completely new field of twenty missiles.
Tell me there’s a difference between this mentality and:
This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch — and the new maintainer can’t be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version.
Let’s see. Obsession with new and shiny stuff? Check! Belief that technology will conquer all? Check! More interested in releasing product than actually having a product that works? Check! Complaints from other developers about fundamental flaws in methodology unsound ignored? Check! Poorly articulated design goals with no clear roadmap to achieve those goals? Check! Wow, that’s really disturbing — the new and improved Department of Defense really does look like a CADT software project.
I weep, but I don’t know why.
(We will, for the sake of politeness, ignore the geopolitical implications of missile defense. Gwynne Dyer had it right almost a generation ago: “Star Wars won’t help people survive, only missiles.” The issue isn’t — and has never been — one of defending friendly lives, but ensuring that American weapons can be delivered without fear of retaliation; back in the cold war this was more about preventing a counterforce first-strike, today it probably has more to do with having the ability to blow the shit out of Tehran or Pyongyang without worrying a hidden launch site might get overlooked.
On a totally unrelated note, Jack Hitt is a fantastic writer who desperately needs a frickin’ Web site or something so he can point to his latest articles and say, “hey, go read!”)