ObamaCare Clusterfuck: How bad is it? Megan McArdle gets it right on the exchanges
Six months is an extraordinarily aggressive timetable to start doing an IT project, even one that’s what one of my colleagues used to call “shake and bake”: take it out of the box, add a few of your own ingredients, and serve it up.
Yes, the administration had been working on Obamacare since it passed in spring of 2010. But it seemed to me that just the build phase would take longer than they were allowing, because Obamacare had a lot of complicated parts; it’s basically a giant Rube Goldberg machine that breaks if any of its major pieces goes even slightly awry. ...
On the other hand, it’s now been ten years since I worked on an IT installation, and longer since I worked on a large-scale multi-site project. For all I knew, the process had gotten a lot faster since the long-ago days when I was in the business. And of course, I did oppose the law, so I’m probably naturally predisposed to assume the worst. It wasn’t unfair for my critics to be skeptical of my judgement; I was a bit skeptical myself. Why would the administration lie about being prepared to move on time? Wasn’t it more likely that I was missing something?
I had exactly the same "This can't be happening!" feeling, based on my own IT experience, more like 7 or 8 years ago.
One of two things must be true: the administration knew this was necessary long ago, but concealed it from the public and the congress in order to limit the time they had to react; or the administration is so incredibly inept that it has only just now realized that it wasn’t going to be able to handle any of the complicated bits. Either way, why would we assume that anything else they say about the systems–like, “It’ll be ready next year”–is true? Indeed, why should we assume that this is the last such revelation?