6 ms·
That's basically what happened with S3 a couple years back. Mistyped command caused an outage for large parts of the internet in the US. Now, I dunno if they co
by stone-monkey 8y ago
That's basically what happened with S3 a couple years back. Mistyped command caused an outage for large parts of the internet in the US. Now, I dunno if they could make a big enough mistake that would bring down the whole company, but certainly it's been proven that a single mistake can affect major portions of the internet.
- antt 8y agoI always find it funny how I'm designing with best practices in mind on top of infrastructure someone out of university build as their first project.
- nostrebored 8y agoThis is not the case with S3 and not the case with that incident.
- lugg 8y agoPretty sure there are first year grads who have worked on S3 as their first project.
- StavrosK 8y agoSo what? You're saying it as if they gave them root access to the servers and went "go nuts".
- karlkatzke 8y agoYeah, that's pretty much what major companies I've worked for will do with summer interns.
- StavrosK 8y agoI don't know, that hasn't been my experience at all in the companies I've worked for (maybe because there's no way I'd let it happen).
- lugg 8y agoBugs in code happen. You don't need write access to cause irreparable damage when the app you're working on has it.
- StavrosK 8y agoThis applies to everyone, juniors and seniors, and that's why we have code reviews, tests and tooling.
- antt 8y agoYou can't prove me wrong since it's source is not available.