So do it. I was thinking college interns. There certainly was no SCRUM, unit testing or load balancing done before launch. And the Q/A team would have already been fired where I work.
I can tell from the errors folks were sending me that it had little to do with heavy traffic. Who builds a web page that downloads 89 javascript files? Google doesn’t even do that. It’s almost like you had folks learning how to build web sites practice on healthcare.gov.
Gee, if only we could get these same guys to redo the irs.gov site...lol
I jokingly said “government bureaucrats” but it seriously looks like it was programmed by beginners
They didn’t even have the sense to consult with any company or companies that handle a huge volume of traffic like Amazon or Google to see what happens when a million people try to access your site all at once.
“89 javascript files”
An average of 3 - 5 javascripts is the norm.
Anything at 8 or above typically means that the website is attempting to learn about you and your computer.
Anything above roughly 20, means that the website is determined to learn and probably collect.
[Inserted a paragraph/carriage return in 2 spots, to make this a little easier to read:]Information technology experts who examined the healthcare.gov website at the request of The Wall Street Journal say the site appeared to be built on a sloppy software foundation and five outside technology experts interviewed by Reuters say they believe flaws in system architecture, not traffic alone, contribute to the problems.
One possible cause of the problems is that hitting 'apply' on HealthCare.gov causes 92 separate files, plug-ins and other mammoth swarms of data to stream between the user's computer and the servers powering the government website, says Matthew Hancock, an independent expert in website design. He was able to track the files being requested through a feature in the Firefox browser. Of the 92 he found, 56 were JavaScript files... '
They set up the website in such a way that too many requests to the server arrived at the same time,' says Hancock adding that because so much traffic was going back and forth between the users' computers and the server hosting the government website, it was as if the system was attacking itself.
The technician is probably using the Firefox / SeaMonkey add-on, NoScript.