3 ms·
Shit happens some time. Who cares who broke it- what matters is they're fixing it. I hope github does make public a official reason tomorrow. Not looking to bla
by ivthreadp110 11y ago
Shit happens some time. Who cares who broke it- what matters is they're fixing it. I hope github does make public a official reason tomorrow. Not looking to blame anyone- I just want to know what they're doing internally to make sure it does not happen again... adaptation. Even if it's from some external hack or ddos attack- how can they plan on building redundancies in. I am pretty sure GitHub's dev team is talented- I'm being such an anti-troll.
- AdamJacobMuller 11y agoMy comment was quite joking in nature. > I hope github does make public a official reason tomorrow I do too, but, mostly I find post-mortems quite interesting to read. If your services are at some 95% uptime or lower, you're doing something (serveral things) very wrong and its probably not that interesting to me. Getting from 95% -> 99% you probably did some interesting things there. Going into multiple .9s beyond that, you're likely doing quite a bit of interesting stuff but what I find more interesting is where you went wrong. Figuring out not just where you went wrong, but, what your incorrect assumptions were and WHY they were wrong. "We believed X could never fail because of Y, and even if X did fail, it would not cause production impact because of Z!"