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!
Posted on 11/16/2013 10:40:59 AM PST by SeekAndFind
I don't envy the army of geeks who are engaged in trying to salvage something from the healthcare.gov debacle. They've been at it for six weeks with still no clear prospects of when the site might be usuable - even barely.
Jeff Zients, the Obama administration's point man riding herd on the army of techies who are frantically working to repair the glitches that are constantly showing up, says they've established some priorities; a top 50 list of the most important fixes for the website. Of course, that doesn't include more dozens of minor issues that need to be addressed.
Politico:
Jeff Zients, the Obama administration's point man in the repair mission, joined the daily update for reporters Friday and said there is a top priority punch list - with "50 priority fixes as we enter this week."
And that doesn't count the lower priority fixes in what Zients called an "iterative process."
In the conference call he said the system is getting better - but it's not where it needs to be.
"We clearly need the system to perform reliably with fast response times at higher volumes," he said.
The administration is aiming to get the site working smoothly for the "vast majority" of users by the end of this month - but they've also noted that "smoothly" doesn't mean perfect. Zients said he expects "intermittent periods of suboptimal performance."
Not quite sure what he means by an "iterative process." He may be referring to some elements of the of the website that have repeat failures for certain functions that would need to be addressed. It sounds as if fixing the minor stuff will be a long, laborious process - a matter of finding and fixing a lot of code.
(Excerpt) Read more at americanthinker.com ...
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.
Right now the website is like a SF homosexual bath house with bad plumbing that’s down for repairs. Once it’s up and running and forcing its patrons to frolic without benefit of condoms is when the real fun starts.
Yup. With emphasis on "development". I would not normally consider the period directly after release to be terribly "iterative".
If the system is released, and you find yourself with a "top 50" list of things which require fixing, then you've really screwed up. Normally, you might have 5 or 10 things which could be patched in short order. That's not iterative. That's just fixing things that you got wrong. Your real iterative process at this point ought to mean that enhanced functionality is planned for the next release (in a year) with even more functionality planned in the release after that (in two years). That's iterative.
My guess is that Obamacare is badly architected. It cannot be patched. It probably can't be fixed. They'd be better off tearing it down and starting over.
As they approached release, I wonder if they had a list of Top 5 Risks. That would make interesting reading.
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.
Thats a lot of Gigabytes.
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.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.