3 ms·
While I'm sure you're partly correct, until we know how bad the CMS on up management was for this specifically, can we really say that for sure? What we know i
by hga 13y ago
While I'm sure you're partly correct, until we know how bad the CMS on up management was for this specifically, can we really say that for sure?
What we know is:
The project didn't get seriously started until February/March (e.g. the election created a 3+ month freeze on HHS publicly visible work).
The NYT reported that in the last 10 months, 7 major requirements changes were made.
We've been told the "no window shopping" one was made in August or September.
We've heard from multiple sources that changes were ordered through the week before launch.
Given all the above, how much do you see incompetence, and how much "just not done yet" pre-alpha stuff? I'm mostly a back end developer and am not up to date to judge this, I'm really interested if the above makes any refinements to your judgement.
- twoodfin 13y agoe.g. the election created a 3+ month freeze on HHS publicly visible work That's not precise. There was no legal requirement that HHS freeze publicly visible work around election time. The administration, for campaign reasons, didn't want ongoing work to trigger anything that might get in the way of the re-elect. Remind me again which party is obviously oh-so-serious about governing.
- hga 13y agoI was trying to be polite. But in all seriousness, this is the first major entitlement program passed without bipartisan, widespread political support (more from me here on that: https://news.ycombinator.com/item?id=6622456 https://news.ycombinator.com/item?id=6622456). The Administration was insane not to factor in that there would be all sorts of "glitches" in the development process because of that. Someone deadly serious and competent, like the shivved Tom Daschle (https://news.ycombinator.com/item?id=6622284 https://news.ycombinator.com/item?id=6622284), should have been working on this the day after it was signed, if not before. Then again, very few people seem to have that much power in this Administration ... see again the possible object lesson of Daschle.
- twoodfin 13y agoI'd take Tom Daschle over Harry Reid running the Senate (or at HHS over Sebelius) any day, but I am skeptical of the theory he was "shivved". You're right that the car service issue should not have been enough to sink him, but I think that was a convenient out: IIRC, Republicans were getting ready to ask some uncomfortable questions about his wife's lobbying efforts, and I can understand why neither he nor the President were excited about going down that road. Also keep in mind that his tax troubles came to light after Geithner's and others', so there was less slack left to give.
- hga 13y agoUrk, I left out "possibly" in front of shivved, follow the link and I'm much less certain, and in fact still lean towards my initial opinion which you've fleshed out/reminded me more about. Still, suppose this was the one decision that sinks Obamacare.... Well, that's 20/20 ... erm, forcasting??? And, yeah, Sebelius was a known disaster when picked (I live right across the border from Kansas); I mean, she let the state run out of money one month (http://en.wikipedia.org/wiki/Kathleen_Sebelius#Tax_revenue_crisis http://en.wikipedia.org/wiki/Kathleen_Sebelius#Tax_revenue_c...), rather a surprise as I remember. I strongly suspect she follows in the usual Obama Administration pattern Cabinet members being figureheads and cheerleaders instead of true executives, which we'll likely be about to guess about when she testifies this week. Reid ... I'll just go with a Wall Street Journal writer's description of his coming across like a "slightly overeager undertaker" ^_^.
- jroseattle 13y agoContext is everything, so it depends on the "change". But never ascribe to malice what can be explained by incompetence. Pre-alpha is not an excuse for improper architecture upfront. As I understand it, there is a lot of background integration with various agencies, systems of differing reliability, non-standard interfaces, etc. There are plenty of strategies that can deal with that environment (SOA, asynchronous queueing, etc.) It's quite apparent this first version was not built with much flexibility in mind. Not flexibility regarding requirement changes, but flexibility for dealing with the infrastructure already in place.