I had a fiat like that some years ago....
FIAT does indeed stand for Fix It Again Tony
the website echoes the issues of the program's functionality....to a t!
No problem. It’s all going to be finished within 24 business hours of midnight, November 30, 2013.
“Iterative process” is a term of art in software development. You establish a plan for a chunk of work, execute the development work, test, repeat. It’s about breaking a huge task into a series of smaller more manageable ones.
The website is not relevant; there won’t be doctors and hospitals worth a darn even if anyone is able to sign on and enrolls. Liberal RATs on Fox keeping talking about the superior/better plans the exchanges are offering. How is that when you don’t have quality doctors and hospitals? Perhaps they’re offering quality hospice care.
They still han’t called the GEEK SQUAD.
So they fix the entry into the system. Maybe.
Then people will discover, as Ms Pelosi said, what’s in it.
Fixing the website isn’t going to significantly add any number of paying enrollees.
All this for a product no one wants, and no one can afford. Too bad Obamacare can’t rollover, and go bankrupt, like all of Obama’s green energy experiments.
What does “fixed” mean? There are no finite definitions for this administration. Whatever the status of the website come then end of the month, it will be declared Fixed. It depends upon what your definition of “keep” and “period” is. I have never seen such a flexible definition of words, well, not since Slick anyway.
Don't worry, we have a list of 50 things to fix, and then cars like this will be ready for everyone.
Obama to software geek: “I want this website fixed by November 30.”
Software geek to Obama: “And I want a girlfriend by November 30. That ain’t happening either.”
I’m still trying to wrap my head around 500,000,000 lines of code in 2013 and failing badly.
An “army” of techies” and a top 50 problems list, plus dozens more “minor” problems to address... Am I the only one that gets the impression that they are trying to make it look like a massive issue, when there really isn’t one?
Zients has twenty years business experience and specializes in advising companies on business practices.
According to Obama, his assignment was to help “streamline processes, cut costs, and find best practices throughout” the U.S. government.
Zients replaced Nancy Killefer who withdrew from her nomination to this position in February 2009 to avoid controversy about her personal income taxes.
As the Chief Performance Officer, Zients leads the Obama Administration’s “Accountable Government Initiative”. Zients outlined the Initiative in a memo to the government’s Senior Executive Service in the fall of 2010.
One primary area of focus is reforming how the government buys and manages information technology. To bring outside expertise into government, Zients organized a Forum on Modernizing Government at the White House in January 2010 that brought 50 private sector CEOs together with senior government managers and CIOs to discuss best practices in large-scale IT project management.
This session informed subsequent actions, including ordering a halt on all major government financial system projects until a review was completed to eliminate long-standing problems, reduce costs and accelerate the delivery of functionality to end users.
In November 2010, Zients announced an execution plan for overcoming the long-standing structural challenges that plague government
"We clearly need the system to perform reliably with fast response times at higher volumes," he said.
There is a venerable admonition that, if your wants are "good, fast, and cheap," you can "pick any two."
What are the chances of perfecting "reliable, fast response, and high volume?"
No problem. Obama will give a speech proclaiming the web site fixed. The assumption is that his phenomenal oratory will save the day.
“So who are you going to believe - me or your lying eyes?”
50 Shades of Gray.
50 Ways to Leave Your Lover.
50 Obamacare Priority Fixes.
One of those things is not a hit.
“iterative process.”
In this case he does not mean the normal iterative process that some posters have explained.
He means an iterative process of diagnostics / debugging; by which, he means the next bug surfaces when a previous bug has been fixed. The first bug prevented getting far enough into the process for the subsequent hidden bugs to present themselves.
Your car won’t start. Using diagnostics 101, nothing is cranking and you realize you have a dead battery. Until the battery is replaced, you don’t know you have a bad starter too. OK now you hear that the battery and starter are operating, but the car still won’t start. Next step . . . is it getting fuel? You discover the tank is empty, you fill the tank. Still no fuel. Fuel pump, etc. etc.
THIS is what they are doing iteratively. Each “fix” exposes the next level of hidden problems.
PLUS changing code on the fly, they have to be introducing MORE bugs with the fixes. Has to happen with a mis-managed system like this. Using the automobile analogy, “maintenance-induced failure”.
FIFTY TOP issues?? This thing is a rolling train wreck! The faster they fix it, the more bugs they will find and the more bugs they will create. It will be a hundred next time, unless they shove all those into the minor problems category.
GIVES A WHOLE NEW MEANING TO BLACK FRIDAY! which is the 29th.
“I don’t envy the army of geeks”
I just hope that a bunch of these geeks are loading in their own viruses and backdoors.
How many people realize out there (I know just about everybody on FR does) what happens when you find bugs in software? It leads you to more than one new bug each, until you’ve gone from top to bottom several times. There’s mention of this being a multiple iterative process, and that’s the truth. This is extremely complex, and with so many independent parts in motion it’s going to take years of intensive work, costing billions.
Gawd, it would have been cheaper to have gotten it right in the first place rather than just shipping the work out to Obastard’s cronies.
