The media has been a firestorm of ‘glitchy’ reporting since the botched launch of the Obama Administration’s healthcare exchange marketplace, mainly because no one’s quite sure what did or didn’t happened.
If you missed it, the exchange’s Oct. 1st launch was mired with complaints, outages, and glitches. Many pundits and talking heads claimed that this was simply because of the enormous amount of Americans who were all trying to log into the brand new system. But we dived into the code to figure out what was actually going on, and what we found was much more nefarious.
This is only the tip of the iceberg because the source code of the backend is not accessible, but the lack of optimization in the front end shows the overall low code quality.
The first step of the sign-up process is not optimized and it is one reason of the server workload: https://www.healthcare.gov/marketplace/global/en_US/registration#signUpStepOne
A big part of the problem is that nobody was monitoring the technical and structural health of this software as it was being built. That is absolutely essential in a complex, time-constrained project. Now the cost is just going to multiply (and as we know it’s already beyond $170m).
This is a perfect example of what can go wrong when you hire a private contractor and have no way of verifying the quality of the release.
There were also some additional issues reported in the media: duplicate users, data not loading for the security questions, error messages, etc. A lot of these glitches could be easily associated with a backend architecture that is not very robust.
There was also a handful of other errors that we uncovered:
Many pages were slow to load because they required the browser to fetch large custom font and typeface files.
Lastly, many users were seeing blank site pages or pages that weren’t loading correctly.
It was only when you turned on your browser’s developer tools that you could see the error.
Ask any politician what’s the one thing that’ll win you an election, and they’ll tell you a sturdy base of voters to support you. The same holds true for application development -- if you ignore the underlying architecture it doesn’t matter what you put over top of it, eventually everyone will see the rusty and broken machinery lying underneath.
If you want to hear more about the problems plaguing HealthCare.gov and some ways it can be fixed, you can watch us break down the issues for CBS Evening News, PBS NewsHour, Democracy Now!, and Varney & Co on FOX Business.
Erik Oltmans, an Associate Partner from EY, Netherlands, spoke at the Software Intelligence Forum on how the consulting behemoth uses Software Intelligence in its Transaction Advisory services.
Erik describes the changing landscape of M & A. Besides the financial and commercial aspects, PE firms now equally value technical assessments, especially for targets with significant software assets. He goes on to detail how CAST Highlight makes these assessments possible with limited access to the targetâ€™s systems, customized quality metrics, and liability implications of open source components - all three that are critical for an M&A due diligence.