Slashdot Mirror
Shutdown Illustrates How Fast US Gov't Can Update Its Websites
An anonymous reader writes "Despite what we hear about how much the U.S. government is struggling with a website, it is reassuring that most of government entities can update their websites within a day after they are asked to. This conclusion is the result of research done by the Networking Systems Laboratory at the Computer Science Department of the University of Houston. The research team tracked government websites and their update times, and found that 96% of the websites were updated within 24 hours after President Obama signed HR 2775 into law, ending the Government shutdown. Worth noting that two websites took 8 days to update. It is interesting that the team was able to use the shutdown as an opportunity to study the efficiency of the IT departments of various parts of Government."
to take something down than to make something new.
I read TFA and all I got was this lousy cookie
for fscks sake.
Doesn't it make the assumption that there was no lead time? The shutdown had been threatened for weeks.
Did the IT departments wait for the order to be signed before beginning any work on the updated sites or did they start the updates before the order was signed and then just flip the site over to the update version once the shutdown was confirmed?
mv index.html old_index.html ; mv no_longer_block_access_to_static_data.html index.html
The sites that blocked by DNS wouldn't have much more to do.
much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
Should we expect it to take much time to post a new notice or change some text on the front page of a website? How much does that involve the IT department assuming their front page is setup with some CMS that allows content to be posted with minimal technical effort? There is a big difference between changing the functionality of a website and slapping some notice on there with a default "page unavailable" message for none front page stuff. Heck, there can be a big difference between just changing text on a front page, and changing text that has detailed information, with the latter probably having to go through more people to check the actual content.
... if there was a real shutdown, nobody would have been paid to put "shutdown" notices on websites.
Exactly.
The websites were intentionally changed to display a notice they had been "shutdown" . If they had been shutdown, no one would have seen a notice.
What's more, many important sites with automated data feeds that I access stayed up and pumping out data, meaning someone was still taking a measurement too as the process is not automated.
It was nothing more than both fracking parties trying to make the other guy look like an asshole at OUR expense and frustration.
Vote every single one of those pricks out of office over the next two elections. The next president should meet a house and senate with no incumbents at all.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
I noticed that within hours after the shutdown ended, foxnews.com was featuring stories about Benghazi again ("the questions Americans STILL want answers for!") using their rather large top headline font.
Stories about the shutdown/re-opening/GOP infighting were completely buried for days afterwards.
This is a ridiculous comparison. The data are from two completely different proceedures, from a technical perspective.
Taking a functional government website, like say Astronomy Picture of the Day
To make it 'not work' all they have to do is whip up a basic "this site shutdown due to..." with a few HTML tags and its is "taken down due to the shutdown"
That's all...a few lines of HTML and a redirect!
Second, the criticism of the Obamacare website in the media is not representative of the ***ACTUALL*** technical problems.
Politics aside, the website problems were **routine IT work**...its not an excuse, but **management** is to blame for not scheduling testing with enough time before rollout...
So, this data is doubly unusuable...but it makes sense...
**of course** sites like Astronomy Picture of the Day were up in 24 hrs after the shutdown lifted!!!!! It just took a few lines of code!
Thank you Dave Raggett
Vote every single one of those pricks out of office over the next two elections. The next president should meet a house and senate with no incumbents at all.
It feels good to say that but unless you force all of the lobbyists to be just as inexperienced as the incoming Congresspeople it could be a disaster.
There is a great misunderstanding in all these comments. The question isn't "How long does it take to change 3 lines of code", of course that only takes a few minutes. The question is: "How long does permission to change 3 lines of code take to wend its way through the agency from the Secretary to the contractor?" That typically takes weeks or months, but in this case was done quickly because no one between the Secretary and the coder thought to interfere. That is very unusual. Another question (not answered) is how long does it take for a request from the coder to the Secretary? Typically that would be "forever", which is why most things never get done. It would help if someone below the secretary were authorized to make a decision, but typically that isn't the case.