There are countless situations where suddenly not having a working phone means a serious problem. The article presents an extremely negligent look at the issue.
There are countless situations where suddenly not having a working phone means a serious problem. The article presents an extremely negligent look at the issue.
But sure, "post duck photos". I understand it was perhaps meant as a paraphrase, yet it is indicative of an almost callous level of arrogance at the author's company.
Yes, the part about them overwriting the data from each cycle struck me as odd. I don't think that's good practice even if testing.
To be clear, I'm not saying it's not a bad practice to do that. But the context is that it was a one-off job to do the testing, not a proper test framework, for which this kind of half-assed approach is reasonable.
I think what made me scratch my head is that they didn't consider that generating random phone numbers might lead to collisions. I've been hesitant to publish fake datasets that have randomly generated and validly formatted SIN/SSN numbers in it for that exact reason.
Even if the risk is low, I'd still think keeping indefinite logs of that would be a good idea.