---

Additional Titles

 

By Servando Gonzalez
January 4, 2014
NewsWithViews.com

All the Obama’s Programmers Couldn’t Put Obamacare Together Again

A few days ago, somebody told me a story — most likely a joker’s fabrication — that a true specialist had offered Obama his help to fix the Obamacare website. His name is Mamadú Ubunto, a famous witch doctor from Nigeria. Mr. Ubunto promised Obama that just by killing a white goat, five black chickens and doing some chanting in front of the White House, he would have the Obamacare website fixed in no time.

Well, even though I have my doubts about Mr. Ubunto’s powers to fix the website, I sincerely suggest Mr. Obama to at least give it a try. Otherwise, nobody will be able to fix it. The Obamacare website is like Humpty Dumpty, no computer programmer can put it together again.

Why I am so sure? Because, contrary to common belief, computer programming is not an exact science, but an art. Every computer programmer has his own style and usage, which he is the only one to fully understand.

Even though computer programmers are supposed to document every single line of their programming code, the process takes so much time that is never fully done. Therefore, only the original programmer can fully understand why he did what he did. Sometimes, in the case of long and complicated programs with thousands of lines of code, after some time not even the programmer himself can understand what he did.

According to what I’ve read, the Obamacare website not only has millions of lines of code, but also it was designed by a team of computer programmers. The joke that the camel is actually a horse designed by a team comes to mind. Experience shows that when a computer program becomes too complex, no one can comprehend it entirety. As a result, if the program breaks down, nobody can fix it. This is exactly what is happening to the Obamacare website.

A common joke among computer programmers is that every computer-programming job will take double the time than you initially calculated — even if you initially calculated for double the time! It seems, however, that the programming job for the Obamacare website was not only awarded based on personal contacts (Do I smell corruption here?), not on experience and expertise, but also that it was accomplished in a rush. So, I can safely surmise that it was a sloppy job, with a lot of what in computer programmers’ jargon is called “spaghetti code.”

Therefore, forget about it. The Obamacare website is unfixable. Fubar! Kaput! End! Finito!

So, if you have been fooled to believe that the Obamacare website is now working, or that it has just some minor problems that eventually will be fixed, or that your personal information is secure, it can only shows that you are a very gullible person, to say the least.

But the Obamacare Website programming fiasco is not the first in the history of mankind, and most likely it will not be the last.

Some Other Major Computer Programming Fiascos

The Denver International Airport in Denver, Colorado, is the largest airport in the U.S. It was scheduled to open on May 15, 1994. The best computer programmers at the time designed its fully computerized baggage transport system. The core of this innovative system was the airport’s subterranean baggage-handling system. Like intelligent coalmine cars along 21 miles of track, 4,000 independent, computer-controlled “telecars” would route and deliver luggage between the counters, gates and claim areas of 20 different airlines. A central nervous system of some 100 computers networked to one another and to 5,000 electronic eyes, 400 radio receivers and 56 bar-code scanners orchestrated the safe and timely arrival of every single piece of luggage. It was supposed to be a marvelous technological innovation resulting in cutting airline labor costs and shortening waiting times for luggage.[1]

To everybody’s utter surprise, however, the system never worked. Actually it was a disastrous failure. As a result, the airport didn’t open in May 1994, but not until February 1995, with separate systems for each concourse, with different levels of automation.

The initial cost of the marvelous computerized system was $186 million. As it usually happens, however, the costs grew by $1 million per day during months of modifications and repairs. In a last effort to fix it, the computer code was sent to the Massachusetts Institute of Technology to be fixed. After some extraordinary efforts, however, not even the computer wizards at the MIT were able to disentangle the programming code and fix the program. As a result, they had to trash it.

Another notable case of computer programming catastrophic failure is the California DMV attempt to fully automate its operations.

In 1987, the California Department of Motor Vehicles decided to fully computerize the state’s driver and vehicle registration system. Its goal was to unveil convenient one-stop renewal offices in about a year. Instead the DMV project’s cost exploded to 6.5 times the expected price and the delivery date receded to 1998. Faced with failure after failure to make the system work, in December of that year the DMV pulled the plug and ended the seven-year, $44.3-million investment.

The cases I have mentioned above are not the exception, but the norm. In June 1994, IBM’s Consulting Group released the results of a survey of 24 leading companies that had developed large distributed computer systems. The numbers were unsettling: 55 percent of the projects cost more than expected, 68 percent overran their schedules and 88 percent had to be substantially redesigned or abandoned.[2]

A Silver Lining

As I have mentioned in previous books and articles, Barry Soetoro (a.k.a. Barack Hussein Obama) is nothing but a CFR puppet[3] and Obamacare is actually a Rockefeller concoction.[4] Moreover, being a Rockefeller baby, you can bet your money that some eugenic measures have been allowed to infiltrate into the Obamacare monster — which nobody, even the corrupt politicians who approved it, seem to have read.

Nevertheless, as the saying goes, every dark cloud has a silver lining, and the Obamacare site’s disaster is probably one of the best things that has happened to us, the American people, in the last half-century.

Usually, laws passed by the CFR-controlled politicians in the U.S. government do not have a short feedback time. When we the people finally discover that these laws are wrong and detrimental to our interests, a long time has passed and nothing can be done to reverse them. These are the cases, i.e., of the law that created the Federal Reserve Bank, the law that created the IRS, and the ones that created the National Security Council, the CIA, and later the NSA, just to mention a few of them.

Subscribe to the NewsWithViews Daily News Alerts! Enter Your E-Mail Address:

In this case, however, the CFR conspirators made a big mistake. They linked the Obamacare monstrosity to a Web site, and a web site gives instant feedback. It either works, or it doesn’t.

You don’t have to wait for half a century to realize that Obamacre is a total failure.[5] It is obvious the Obamacare’s website is a total disaster. But the good part of it is that its failure has given most people an unmistakable sign that the whole Obamacare concoction is nothing but a catastrophic failure.

Thank you, Obama. Finally you and your CFR masters have done something good for the American people.

Sometimes the road to Heaven is paved with bad intentions!

� 2013 Servando Gonzalez - All Rights Reserved

Footnotes:

1. The Denver Airport programming fiasco is analyzed in detail in W. Wayt Gibbs, “Software’s Chronic Crisis, Scientific American, September, 1994.
2. Ibid
3. See, Servando Gonzalez, OBAMANIA: The New Puppet and His Masters (Oakland, California: Spooks Books, 2011.
4. Servando Gonzalez, “Why Do They Keep Calling It Obamacare?” See also, Ed Homic, "Will Obama’s Health Care Plan Mirror the 1994 Clinton Failure?", CNN.com, July 22, 2009.
5. See, Jeryl Bier, “$50M Obamacare-Fix: 'Literally a Life-or-Death Situation',” The Weekly Standard, December 26, 2013