You can login if you already have an account or register by clicking the button below.
Registering is free and all you need is a username and password. We never ask you for your e-mail.
Don't fire that person. It is hard to find anyone with enough guts to type commands like that one. Plus, you are guaranteed that they will know that commands proper syntax in the future.
Doubt it. Mistyping a command happens. I don't think that's the real offence here. The real problem is that there was no safeguard in place to prevent the typo from doing so much damage. And the responsibility for that is probably so diffuse that nobody will get fired. Instead they'll just build in the safeguards now, and that's that.
As someone who has done this a few times, you will get fired as soon as the manager knows it was you. There's zero compassion or respect for the wisdom that comes from these types of mistakes.
Errors at my workplace are usually categorized as: that could have been bad, someone got hurt, and someone died. It's always weird to me to remember that you can fuckup royal at work without killing someone.
Sort: Top
[–] jerrykantrell 0 points 11 points 11 points (+11|-0) ago
Someone's getting fired!
[–] p0ssum 0 points 14 points 14 points (+14|-0) ago
Experience: Took down most of the internet in an afternoon.
[–] burns29 0 points 8 points 8 points (+8|-0) ago
Don't fire that person. It is hard to find anyone with enough guts to type commands like that one. Plus, you are guaranteed that they will know that commands proper syntax in the future.
[–] tame 0 points 6 points 6 points (+6|-0) ago
You shouldn't ever be typing that kind of command in production. Your prod environment should be set up so that commands like that aren't typed.
[–] 1812-was-not-a-tie 0 points 6 points 6 points (+6|-0) ago (edited ago)
Doubt it. Mistyping a command happens. I don't think that's the real offence here. The real problem is that there was no safeguard in place to prevent the typo from doing so much damage. And the responsibility for that is probably so diffuse that nobody will get fired. Instead they'll just build in the safeguards now, and that's that.
[–] I_JustFeel_ItsTrue 0 points 2 points 2 points (+2|-0) ago
As someone who has done this a few times, you will get fired as soon as the manager knows it was you. There's zero compassion or respect for the wisdom that comes from these types of mistakes.
[–] tame 0 points 2 points 2 points (+2|-0) ago
Exactly. They're gonna have to redesign their production systems interface so that you can't make this kind of mistake there.
[–] [deleted] 0 points 8 points 8 points (+8|-0) ago
[–] BANGAndTheDirtIsGone 0 points 6 points 6 points (+6|-0) ago
They've been known to take down rockets.
[–] 1nv1ctus 0 points 6 points 6 points (+6|-0) ago (edited ago)
His mistake cost at least $150 million... dude's probably just waiting for the ground to swallow him up at this point.
[–] Vaati 0 points 5 points 5 points (+5|-0) ago
Errors at my workplace are usually categorized as: that could have been bad, someone got hurt, and someone died. It's always weird to me to remember that you can fuckup royal at work without killing someone.
[–] RipeBanana 0 points 1 point 1 point (+1|-0) ago
It's gonna be a tifu post for sure.
[–] 0110001111 0 points 4 points 4 points (+4|-0) ago
Funnily enough my company used this as a justification to not move everything we have to the cloud, especially since our new VP is an Amazon nut
[–] bloodguard 0 points 2 points 2 points (+2|-0) ago
I wonder if they're going to implement some kind of AI buffer between syadmins and their key infrastructure.
[–] Ciscogeek 0 points 1 point 1 point (+1|-0) ago
They're only human. (for now)
[–] SocialJusticePanda ago
What?