The 11th round involves identifying a correct Nigel Tufnel quote from "This Is Spinal Tap".

Damn I wish I thought of that. But, hey, way to go taking care of business!

The reminds me of Rocky's Boots(https://en.wikipedia.org/wiki/Rocky%27s_Boots) taken up a few levels.

Do you know about Robot Odyssey? Which was a same era sequel which took Rocky's boots up a level. Great game and even more the spiritual ancestor of this game it seems.

The outage took out at least some of their aviation services. If they are unable to update routes and IFR approach procedures then lives could indeed be at risk.

Not quite. The onus is on the pilots to never fly with out-of-date navigation information (it's actually illegal), so if they can't get that from Garmin, they'd just have to get it from somewhere else instead. Garmin's data services being unavailable isn't endangering anyone.

Yep, Plenty of planes flying out there without any electronic maps.

The attack happened about a week after the FAA’s last update went into force. And I believe they’re distributed a week before that.

So the only groundings would’ve been those that have been parked for a while (I guess. I don’t know how they do updates).

https://www.faa.gov/air_traffic/flight_info/aeronav/aero_dat...

—armchair aviator

It's crazy to think that airplanes fly by wire over a cloud computing service.

They don't. Garmin's cloud services supply map/chart data updates and backend services for their mobile app (which is separate from installed avionics) to support flight planning functionality.

"The determined Real Programmer™ can write FORTRAN in any language."

Real Programmers write machine code in any language, thank you very much. (Which TFA rather nearly is, actually, though it's a bit macro-assemblery for a proper example.)

http://www.catb.org/jargon/html/story-of-mel.html

I often tell people to assume the TCP stack's buffering is arbitrary & capricious and will do the most inconvenient thing for your code. That can mean ether a) dribbling data in one byte at a time per recv() call, or b) buffering multiple megabytes and returning it all in a single recv() call.

I've seen sites that specifically deny @example.com email addresses.

Which is perfectly reasonable. They're looking for an email address that they can reasonably expect to deliver mail to, not just an address that is technically valid.

A few years ago we had a nightmarish resource leak in our server. The code in question was reading and parsing HTML, looking for a handful of specific tags (title, description, etc). Under heavy load the server would be stable for a few hours, then memory would suddenly explode and kill the NodeJS process.

The problem was caused by the HTML parser we were using. The parsing results appeared to be a POJO but apparently there was much lurking under the surface.

The fix: `parseResults = JSON.parse(JSON.stringify(parsedResults))`

Which library was that?

Maybe the'll trim it down and call it COPRA LITE.

I vaguely felt that with the meh name the bill's not gonna pass. But now, seeing as I'm not a native speaker of English, I have a definite need for someone to explain the pun.

Coprolite is the name for fossilized poop

Copro- is a suffix that generally applies to poop-related things.

You are the wind beneath my wings.

I have a double hit of tinnitus.

The first hit started in 2010, a neurological "gift" from the swine flu.

The second hit happened in 2013 while mounting a new tubeless mountain bike tire. The tire blew off the rim and caused permanent hearing damage in my right ear.

I have to sleep with a fan or white noise machine now -- the "sound" I hear in a silent room is enough to keep me awake.

This is one of the many reasons I love bike commuting. I solve many work-related problems while I'm riding.

My bike commute was anything but routine. Cars making unsafe right turns one day, pedestrians in the bike lane the next, black ice the third day...