They had this in 2014. But I guess it wasn't integrated with Earth then.

"Retreating upmarket".....ugh.

Look up what "rereading upmarket" means.

I'm sure for many people it works that way. For me, I got more out of actively listening to the professor in real time than from words scratched on a page. The only class I ever used heavy notes in was linear algebra, because there wasn't really another source for the formulas.

I'm sure you can also see the disturbing historical parallels of the right.

A lot of that is more about imposing homework discipline and patterns of thinking, rather than actually expecting you to remember every detail.

I had the opposite experience with note taking. If I tried to keep up with the professor, I spent so much focus on writing that I didn't have bandwidth left to understand the concepts.

Part of pilot training is risk management. One of those risks is "hazardous attitudes," such as believing oneself immune to error.

Boeing is the builder, not the operator. You can get a pilot license and fly yourself, of course. But statistically, the airlines are much safer.

They're out in stores before the movie is finished!

I've never seen a preview stage here. Weird. Anyway, I understand enough to know that there was a weird combination of circumstances (including insufficient unit testing) that caused this to hit everything at once. Normally, you'd see these crashes during a 1% canary and stop it before it becomes user visible, either during a canary of the binary or of the configuration change that diverted traffic. This somehow missed both.

"Cut in." Not my fault slashdot has no edit function.....anyway, yes, that's exactly the problem. The CODE was rolled out slowly; but that didn't matter because that path was not in use at the time. It began getting traffic hitting that bug all at once. That should not have happened. Usually you gradually divert traffic onto a new code path.

Fired, probably not. But can you think of a better teaching opportunity?

Google uses a blameless postmortem process to identify areas for improvement. It isn't about making an example, it's about making sure it can't happen again. This is pretty good for an external report. The problem here is that the code path with the bug was cut it abruptly rather than gradually; that isn't supposed to happen. A secondary problem was hitting a backend too hard when all the jobs tried to come up at once; probably insufficiently random backoff.

There'll be no escape for the princess this time.