Cocktail Napkin Website Planning and Obamacare
It was the horrible first day load that made the exchange websites fail, right?
October 3, 2013 - 2:00 pm
Just for variety, today’s science column is about something I actually have some professional qualifications to write about.
No, that really hasn’t ever slowed me down, I just wanted to note it.
In fact, my master’s thesis, “A Software Performance Engineering Environment,” was about tools to allow software engineers to develop performance models of software alongside the software. I spent some years in IBM and Sun’s consulting practices, usually dealing in one way or another with web-based businesses. I had a very popular talk, “Capacity Planning on a Cocktail Napkin,” which I later wrote as an article for SmartBear Software.
There really is only one explanation for the meltdown of the Obamacare exchanges since 1 October, and that’s utter incompetence.
Now, lemme ‘splain.
Back in the old days, at the Very Beginning Of The Web, all a web server could do was deliver a static piece of text. It was a brilliant hack by Tim Berners-Lee, who realized that he could build a little editor for a simple markup language and add one little change — a special tag that could address another page of text in the same markup language. To make it work, he needed a program that could return those files and a simple way the editor could ask for the files it wanted. The markup language was a subset of a commonly available commercial standard, SGML, called the Hyper Text Markup Language, HTML, the server program using a very simple text-based protocol called the Hyper Text Transfer Protocol, HTTP, and the rest, as they say was ….
Yes, class, that’s right, “history.”
From this simple hack the whole World Wide Web was made.
Now, with the same foresight that led me to buy Borland stock over Microsoft when they both went public, I thought at the time that it was a mildly amusing notion, but I didn’t see much future in it. I was head-down in category theory working on my dissertation.