Speaking of programming...
I worked at a company where a similar bug happened but with e-mails. Basically the e-mail notifications had a bug where they'd sometimes send out hundreds of e-mails to a customer who met specific criteria and were not correctly receiving push notifications about in-coming text messages (hmm, running theme). Every 10 minutes. When we cracked open the several-years-old-code, we saw:
* No unit tests.
* No acceptance tests.
* Code that found a way to break almost every SOLID principle,
This code made sense to someone at some point, but now? Needless to say, fun times were had by all.
If you don't practice TDD/ATDD, perhaps now is the time to push it on management? I subscribe to the belief that even the best programmers can make no assurances even to themselves that their code works if the code is not properly and thoroughly tested, that legacy code is code without tests, etc.
And if you do practice (A)TDD, and the code that did this was what you thought properly unit and acceptance tested, then there was a flaw in the overall testing strategy, find it and learn from it.
Maybe you missed something, and everybody misses something sometimes because everybody is human. A good process means many people have to fail for a bug to get through. Programmers miss things for a reason, Peer Review miss catching something for a reason, QA miss catching something for a reason.
The key is to find out what parts of the process caused all these steps to miss the problem, and take steps to ensure that doesn't happen in the future. Otherwise...well, you're just doing the same thing and expecting different results.
And we all know what that's erroneously claimed to be the definition of.Sometimes it takes a major failure for people to acknowledge a problem everybody knows about. Maybe this is, if nothing else, a time to bring up that problem.
*****
Anyway, my sad: My Nexus 4 screen broke. This phone lasted about a year and a half, and survived numerous falls including a fall down two flights of stairs, and did so with barely a scratch. And then it falls off a neck-height shelf onto the toilet seat, bounces and hits the *other side of the toilet seat* before bouncing again and landing on the floor.
Oh well, at least it didn't go in the toilet itself. I was looking for an excuse to update to a Nexus 5 anyway. But still, kinda a kick in the teeth for it to happen a week after my 3-year old laptop screen cracked. Screens hate me right now it seems.
More likely both devices have had rough lives and were reaching the end of their "power usage operating lifespan" and it's just annoying it happened in such a short time-span.