Skip to main content

View Diary: Sebelius resigning as Health Secretary (125 comments)

Comment Preferences

  •  Thank you. New systems are always bound to (4+ / 0-)
    Recommended by:
    eztempo, doroma, Loose Fur, skohayes

    have issues.  Heads don't have to roll over expected issues.

    •  Agree about new systems, but most of the bugs (4+ / 0-)
      Recommended by:
      wader, BentLiberal, janemas, betelgeux

      should have been ironed out before it went live. It should have been rolled out by birthdate or age or whatever. Expecting a new system to not fail when a gazillion people try to use it all at once shows no planning/knowedge.

      Also, the PR sucked. The message should have been to start slow and expect some problems - but as I said above, most should have been ironed out before start date.

      It’s the Supreme Court, stupid! Followed by: It's always the Supreme Court! Progressives will win only when we convince a majority that they, too, are Progressive.

      by auapplemac on Thu Apr 10, 2014 at 05:45:00 PM PDT

      [ Parent ]

      •  Unfortunately, that's not how I've seen (4+ / 0-)
        Recommended by:
        eztempo, BentLiberal, Loose Fur, skohayes

        government contracts work, in many cases.

        There are deadlines to meet and you get there by hook or crook, else penalties hit.

        They knew long before the deadline that there were problems, I'm sure.  Still, they had a deadline to meet, one which was highly public, and they put forth a gargantuan effort to bring back-end systems in line with a front-end that had not previously been done in the manner desired.  With late funding for the overall project, thanks to Congress.

        They tried their best and hoped it could stand up for a time, while they fixed the biggest holes in their larger design.  I have few doubts that much of the initial rollout was running on compromised implementations against the original design, because what I saw were sessions being dropped due to back-end synchronization issues in the early stages.  Seems like they were hoping for simple user scenarios to save the early rollout, but the overload of sessions made even less likely against the compromises already made.

        This was a late project in many respects and should have been delayed before rollout, in order to make the essential flows battle-ready.  But, due the highly political nature of getting it going in time for registrations to occur for 2014, they took a chance.  It was a bad move.

        They've since learned and brought the federal website implementation to where it was more or less meant to be, but expecting them to have ironed out all the bugs up-front in this particular situation was unfortunately never an option provided to the team, I feel.

        None of this speaks to the quality of project leadership in getting to Opening Day, as I have no insight to that aspect of the work.

        "So, please stay where you are. Don't move and don't panic. Don't take off your shoes! Jobs is on the way."

        by wader on Thu Apr 10, 2014 at 06:42:36 PM PDT

        [ Parent ]

      •  I remember when the Navy switch their (0+ / 0-)

        computer system to the Army's.  Glitches were expected and perfection was made as we rolled along.  Any changes needed were taken from the input of admin and payroll personnel until it worked perfectly.  

        Suddenly the Dems have to provide a spotless, glitch-less project or else the republicans and media are going to scream until someone is fired.  The worst part is the Dems who are too coward to say "shut up and stop the whine".  Surely the republicans have not done one thing for the american worker, so who gives a hoot on what they cry over.

        Dems need to stop throwing innocent people under the bus just to satisfy the republicans, who btw laugh every time one gets fired.

Subscribe or Donate to support Daily Kos.

Click here for the mobile view of the site