given the administration’s previous efforts to sabotage the insurance markets, it’s not paranoid to view this maintenance schedule as a plan to keep down enrollment
We're all technical folks here. What possible reason could there be to close the site every Sunday morning for 12 hours? In what situation would that ever be the best answer for users?
Sometimes the reason isn't always purely technical. Especially in the government, there could be bureaucratic reasons that cause really un-intuitive behavior that's pretty much unheard of in the commercial world.
They could be exercising migrating to their COOP site and when asked "how long does it take for the site to FULLY come up?" the contractor said 12 hours to be on the safe side. If you account for things like acceptance testing done by government employees, 12 hours is unfortunate but not unreasonable for the government.
Database compaction?
There's no excuse for doing slow, blocking maintenance operations on a live user-facing database.
You can't judge a government system against the best-of-class standards of the private sector (note that I did not say the typical standards, just the top-of-line).
Government systems are rarely built or staffed by the top talent, often outsourced to lowest-bid contractors, and may not even have people on call for issues. It's not unusual for government sites to be scheduled to function only during standard business hours.
So yeah, it sucks that this site is going to be down during some of the least likely times for people to use it (midnight to noon on Sunday), but that's not at all unusual for government sites.
Except that's not what happened, the Obama administration set up The US Digital Service to fix Healthcare.gov and specifically staffed it with top talent.
Anyway, you're are making general platitudes about "government systems" without regard for the level, department, or any other factor that would influence the quality. And you think, "not unusual for government sites to be scheduled to function only during standard business hours". It would be a genuine shock to anyone knowledgeable about these sort of things if this were truly technically necessary.
You can, but you couldn't be further from the truth.
> Anyway, you're are making general platitudes about "government systems" without regard for the level, department, or any other factor that would influence the quality.
I guess, but that's not really relevant to my point, which is to refute the statement "There's no excuse for doing slow, blocking maintenance operations on a live user-facing database.". There is an excuse in government systems for this. You may not like it, and you may think it's an excuse that they should avoid, but that's one reason, and these sorts of issues are pretty common in government systems.
You're correct that healthcare.gov is actually one of the better-functioning sites in that regard, but even if some aspects of it mitigate the shortcomings, that doesn't mean it's not subject to some of the other same limitations.
> It would be a genuine shock to anyone knowledgeable about these sort of things if this were truly technically necessary.
I'm emphasizing that what people on HN think of as "necessary" is different from what the government thinks of as "necessary". The example that I gave was that, if you don't have anyone on-call after hours (which is incredibly common), it makes sense to keep an important system offline during those hours, rather than risk a silent failure.
When I say knowledgeable about these things, I mean these contracted, designed-to-spec, CMMI level 5 projects. Even one of those would be unlikely to require this sort of maintenance. Again, open to correct if you can offer specifics.
Quit lying to yourself and get some ethical standards.
>As part of its mission to translate the false narrative that the Affordable Care Act is failing into reality, Tom Price’s Health and Human Services Department has already announced massive cuts to the navigator programs that fund Obamacare outreach, as well as the budget for ads that alert Americans to the existence of the open-enrollment period.
It just seems like a strange coincidence they need to shutdown the site during open enrollment.
"Expected (planned) maintenance" outside of normal working hours, and during expected high volumes of usage = WTF.
See https://www.theatlantic.com/technology/archive/2015/07/the-s...
From the article:
> No explanation was given for the outages, but given the administration’s previous efforts to sabotage the insurance markets, it’s not paranoid to view this maintenance schedule as a plan to keep down enrollment. At a minimum, it displays an indifference to the needs of the population it is supposed to be serving.