If you have the ability to do this on your first day, it’s 100% not your fault.

It’s fine, just restore the backup.

Every seasoned IT person, devOps or otherwise has accidentally made a catastrophic mistake. I ask that in interviews :D

Ctrl + z.

Thank you for coming to my Ted talk.

I once bricked all the POS terminals in a 30-store chain, at once.

One checkbox allowed me to do this.

It was all a Pentest! The company should have been operating under the Zero Trust Policy and their Security systems should not have permitted a new employee to have that many rights. You're welcome, the bill for this insightful Security Audit will arrive via mail.

Pretend you thought you were hired as disaster recovery tester

"Ah, shit. Oh well. They have backups."

"..."

"They have backups, right?"

It's my last day at work, and I just started to dd my work laptop...but I forgot I was ssh'd into the production database.

Get this monkey a job at Tesla

256,338 rows affected.
when it gives you a time to rub it in. 'in 0.00035 seconds'

I can do one better. Novo Nordisk lost their Canadian patent for Ozempic because someone forgot to fill out the renewal with a $400 admin fee.

They will lose $10B before patent ending.

But they saved $400. Someone needs to talk to HR.

You’re stress testing the IT department’s RTO and RPO. This is important to do regularly at random intervals.

Netflix even invented something called Chaos Monkey that randomly breaks shit to make sure they’re ready.

What’s with the weird vertical artifacts in this image?

Tell them your name is Claude, they'll pay you $200 a month for the privilege.

Reminds me of a major incident I got involved in. I was the Problem Manager and not MIM (Major Incident Management), but I've had years of MIM experience so was asked to help out on this one. The customer manufactured blood plasma and each of the lots on the production floor was worth a cool $1 million. The application that was down and had brought production down was not the app that actually handled production, but an application (service) that supplied data to it.

Of course the customer thought that app was not Mission Critical so it didn't have redundancy. I joined the call and first thing I asked was when did the last change go through on this app... Spoiler: I had the change in front of me and it went in the previous night. The admin of the app speaks up that he did a change the previous night... And NO the MIM team had NOT looked at that change yet... Did I mention this was FOUR FUCKING HOURS into the outage? That is MIM 101. Something goes down, look to see who last fucked with it.

This is why you need experienced MIM people in enterprise environments.

So I took control of the MIM, instructed the App Admin to share his screen and walk us through the change he did the previous night... Two screens in and OH... Look at that... There's a check box that put the app into read only (or something like that, this happened back in 2009 and I don't remember all the details). I'd never seen the application before in my life, but knew that check box being checked, just based on the verbiage, could not be right... So I asked... The Admin, sounding embarrassed, said yeah he forgot to uncheck that box last night...

Fuck me.

He unchecked the box, bounced the app and what do you know... It started to work.

A single damn check box brought down the production line of a multi-billion dollar company.

My investigation for that Problem was a bit scathing to multiple levels of the customer. If a service supports a Tier 1 production app and that Tier 1 app would stop working if that service goes down... GUESS WHAT! That service is MISSION FUCKING CRITICAL and it should be supported as such. My employer was not on the hook for this one, as both applications involved were customer supported.

I would love to say that the above is an uncommon occurrence, but honestly it is the main reason for outages in my experience. Something small and stupid that is easily missed.

I was hired as a backup representative and just wanted to know what I was dealing with and make a clear statement.

the ono-second

The data was a mess and needed to be cleaned up anyway.

...which would make it about 99,9999999% their fault for giving a new employee write access to the DB.

Have you tried turning it off and on again?

All of my bananas are worthless now!

Oh, so that's what the Delete button does.

Right click Recycle Bin --> Restore

Why is the default for some database tools to auto commit after that? Pants on head design decision.