21–26 of 26 posts
Is there any more information about the inner workings of the failed healthcare.gov site? It's quite interesting to read how horribly wrong they got it.
Mikey was the first SRE at the scene of healthcare.gov and is now running the new US Digital Service. He works with the folks mentioned in this article and lots of others trying to fix how the government writes software.
Wow, 30 milliseconds. Subtract out the RTT, and you have app request times on the order of 5ms. Outstanding. And impossible.
Not to take anything away from the "young people" -- who are ages 28+ -- but this article over-sensationalizes their accomplishments. "The MPL team had three great technical accomplishments over its 16- month-long life. First, it served as a crack team which understood the infrastructure of the site and could resolve small issues as they arose. Second, it built an insurance application, called App2, which signed up n…
I think this is true. Governments and corporate's are starting to see that you don't need to go with GenericAdAgency12 anymore to get shit-hot, well-made websites going. This project was a textbook example of this.
For the first time in decades the entire country experienced exactly the government they elected and are paying for. And the beauty of it is that it could not be hidden away, spun or silenced.
What's sad is to see an article such as this one pushing the idea that it was fixed...a "Mission Accomplished" message of sorts. The truth of the matter is that dozens of people should have been fired and a number of them should have ended-up in jail.
Nothing has been fixed. Sure, the website is better but the organization is still being run by he same incompetent morons who created the problem in the first place. That's the problem. And, yes, a bunch of young people can help fix it without writing a line of code by using their brains to vote rather than cargo cult and emotion.
"The old system responded to requests somewhere between two and 10 long seconds; the new one takes 30 milliseconds, on average." Wow, 30 milliseconds. Subtract out the RTT, and you have app request times on the order of 5ms. Outstanding. And impossible.
"The old system responded to requests somewhere between two and 10 long seconds; the new one takes 30 milliseconds, on average." Wow, 30 milliseconds. Subtract out the RTT, and you have app request times on the order of 5ms. Outstanding. And impossible.
For an example of scale, 10,000 nodes with 96GB each costs less than $30M dollars. The government spent billions on the healthcare.gov project.