Gitlab DELETING Production Databases | Prime Reacts

I was watching this in realtime cause I had a gitlab account. They fixed it on-stream. People wanted him to be fired, and the lead helped him and REFUSED to punish him saying 'we all make mistakes' and they fixed it, implemented a post mortem, and they got it fixed. :)

i do devops and this video stressed me out the entire time

Legend has it: On that day, a site-reliability engineer was born

the amount of anxiety i felt while watching the original video the first time was insane i felt so bad for the guy and imagining my self in that position 🤣

"software engineers hate him... find out this one simple trick a dev used to fix all bugs permanently"

ALWAYS opt to move/rename and not remove/delete. Deleting is one of the most dangerous things you can do.

For production servers we actually alias "rm", "mv" and all installed other tools that delete/rename files so that they ask for confirmation and print the user, host and affected files.

All of the in progress Toy Story 2 got deleted with a rouge rm -rf. The backups failed. The only reason that movie came out was because someone was working from home and had the stuff sync to a remote server

Ok, I'll come clean on my rm -rf ~, but this is really weird so get ready. I work on windows with vim, and I wanted to create a file. I did :e ~/folder/filename The thing is for some reason, (maybe because I used the wrong / instead of \...) a folder ~ was created in my current working directory (project I was working on) I opened a terminal (powershell) and typed "ls" to see that yes, a stupid folder "~" was in my project, then I typed "rm -rf ~"... Then hell let lose... I hit CTRL-C maybe harder than GitLab engeneer 1, because it was taking some time, I didn't expect that... I realized that ~ even in windows powershell, is your current user folder. (since when!?) Basically, I had lost all my dot files, and surprisingly, none of the other files. My bossed helped me to restore my files from a backup of that day, and I was back up and running in 45 min. 20 years of experience in IT, windows and Linux, and that happened...

I find the outcome is not that bad taking into account this chain of disasters!