Last Wednesday night at about 1850 EDST, a national US Customs and Border Protection computer crashed causing major delays for arriving international passengers across the US. According to this story from WFTV Channel 9 in Orlando, Florida, arriving passengers at Orlando International Airport had to wait for several hours to clear customs even after the computer was back in operation at about 2055.  Passengers also could not call relatives or friends to tell them what had happened, because you can't use your cell phone while waiting to clear customs.

What I found interesting was that only three television stations in Florida (the two others being WSVN Channel 7 and WFOR Channel 4 both in Miami) carried the news story at all. There has been no print or web-only reporting that I can find. The Customs and Border Protection website has nary a word on it either.

In August of 2007, a computer meltdown at LAX caused problems with about 11,000 arriving passengers and that hit the national news across the country. At least that many passengers were affected across the country, I would guess. Some 2,000 were stuck Wednesday night at Miami International, and another 800 at Orlando International as well just for starters.

Is this a case that if a computer crashes in the woods, and no one is there to see it, it doesn't really happen?

Or did the August 2007 episode just happen on a slow news day?

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less