Computer Code Changes to Obamacare

I worked most of my career with a major oil company.  I managed a group of computer analysts and programmers.  We developed and implemented user friendly computer systems for the petroleum engineers, geologists, and seismologists.  One of our systems was for the seismic mapping of the substructure formations of the Williston Basin in the Dakotas and part of Montana.  These programs enabled the users to interactively look at the various formations and the various characteristics of these formations with the ability to rotate substructure images and selectively color saturate various characteristics of the different formations.

This system was a series of complex programs.  I would have had heart failure if one of my analysts suggested we implement the system without end-to-end testing.  It was incredible to think we would even consider implementing the system and change code on the fly.  That would be like trying to change the tire on a car speeding 70 mph.  Even small changes made in the code of one module almost always impacts several other modules.

Yet, this is exactly what our government is doing with Obamacare.  They did not do complete end-to-end testing, and they are making daily changes to the code to the system.  That is why the system is down so much.  They stop the "car" to change the "tire", and then speed down the highway 70 mph until they hit another "speed bump".  No way to develop and implement a computer system, even a small one.  It's obvious the people in control of Obamacare have only a vague idea of what they are doing.