News for hackers. Stuff that matters.
Re:GitLab Database Incident – Live Report by sschueller on Wednesday February 01, 2017 @02:25AM (#13539021)
There is a neat video[1] where a Swiss flight has to make an emergency landing and just happens to have a film crew in the cockpit.

[1] https://www.youtube.com/watch?v=rEf35NtlBLg

Re:GitLab Database Incident – Live Report by PKop on Wednesday February 01, 2017 @03:20AM (#13539237)
Here's a great documentary [0] by Errol Morris about the United Flight 232 crash in 1989 [1].

"..the accident is considered a prime example of successful crew resource management due to the large number of survivors and the manner in which the flight crew handled the emergency and landed the airplane without conventional control."

I highly recommend it

[0] https://www.youtube.com/watch?v=2M9TQs-fQR0

[1] https://en.wikipedia.org/wiki/United_Airlines_Flight_232

Re:GitLab Database Incident – Live Report by neurotech1 on Wednesday February 01, 2017 @11:30AM (#13542091)
Another recent example is Qantas QF32 had an engine explode (fire then catastrophic/uncontained turbine failure) and the A380 landed with one good engine, and two degraded engines. The entire cockpit crew of 5 pilots did a brilliant job in landing the jet.
Re:GitLab Database Incident – Live Report by ben_jones on Wednesday February 01, 2017 @02:43AM (#13539098)
It's amazing how decisive both pilots are despite the large amount of process going on.
Re:GitLab Database Incident – Live Report by bdcravens on Wednesday February 01, 2017 @03:11AM (#13539197)
It's like frameworks in programming: it frees brain cycles to focus on what's important
Re:GitLab Database Incident – Live Report by emn13 on Wednesday February 01, 2017 @03:47AM (#13539339)
I kind of agree with the conclusion, but I'd look at that from the opposite direction: i.e. just like frameworks, checklists provide a way to avoid some mistakes in repetitive, boring practices. But you'll never avoid them all, and you're going to need a lot of red tape.

Even better to avoid all that and make it idiot proof. I'd rather not be in the situation where my only protection is rigmarole. But sure, as a last resort (just like frameworks) - much better than nothing. Typically in programming, frameworks are premature. A simple api tends to suffice, with checked (or typechecked) inputs and outputs. But sure, if for some reason you can't make that, and you need complex interactions with dynamically generated code, variable number of order-dependant parameters, black-box "magic" base-types, stringly-typed unchecked mini-languages, multiple sequentially dependant calls into the same thing, or any other tricky api you can't (or won't) easily detect misuse for... then a framework is the least-bad amongst bad options.

Re:GitLab Database Incident – Live Report by protomikron on Wednesday February 01, 2017 @06:15PM (#13546418)
Thanks for that, this is amazing.

I speak their language (it's German, but people from Switzerland speak a pretty strong dialect) and they discuss highly technical and serious stuff, but their language is just so adorable when they mix the English and the German. I always thought this communication is English only, nowadays?