The biggest thing I take away from this is that users have learned to tolerate minor problems in software. I always make it a personal goal to have 0 bugs, but never succeed. It is good that users cut us some slack, because it means we can spend some time pushing the featureset forward, rather than making everything 100% perfect 100% of the time. (Be more careful if you're working on life-critical software, though. Features are not necessarily the most important thing there ;)
"We hope people who love %s will find comfort in the things others share to remember and celebrate %s life." is one of the most insincere code commits of that day. Let others write about a lost loved one, not robots.
I find it strange when I microwave a sock full of dry beans to use as a hand warmer, or a piece of metal that I need to make slightly larger though. My other microwave displays a generic "EnJ0Y!" blinking a few times which is much more applicable in those situations.
You know, I bet it was something to do with `memorializeUser` again (see https://www.columbia.edu/~ng2573/zuggybuggy_is_2scale4ios.pd... slide 46). In fact I would go so far as to say this is the kind of thing that should be encoded in the type system so it's a compile error to try to do this.
"It turns out these users had been dead for several years, but due to a glitch in payroll, they had still been physically alive. We, uh, just fixed the glitch."
I feel like Facebook must do a phased roll out of their front-end modifications such that they'd detect that before it was big enough to matter (or perhaps during language normalization which must be huge for them). My guess is they were running something on the back-end to "clean up" dead users and it went haywire.
