3 ms·
A config change gone bad? That’s like failure scenarios 101. That should be the second on the list, after “code change gone bad”.
by mynameisvlad 5y ago
A config change gone bad?
That’s like failure scenarios 101. That should be the second on the list, after “code change gone bad”.
- jfrunyon 5y agoExactly! Obviously they have extremely robust testing and error catching on things like code deploys: how many times do you think they deploy new code a day? And at least personally, their error rate is somewhere below 1%. Clearly something about their networking infrastructure is not as robust.
- pupdogg 5y agoRight? Especially on global scale. Something doesn't add up!
- TheOtherHobbes 5y agoCurious/unfortunate timing. The day after a whistleblower docu and with a long list of other legal challenges and issues incoming.