👨‍💻 I dropped a staging table on a Friday evening and my lead only asked one thing

Last Friday around 6:40 pm, I was cleaning up some test data on the staging server and ran a delete command on the wrong table. It was a Friday, my bus was in twenty minutes, and the office was almost empty, so I thought I would finish quickly. I had two windows open, one for staging and one for the real thing, and in the rush I picked the wrong tab. Luckily it was staging, but it was the table the testing team was using for their Monday demo. My stomach dropped. I have been working for only eleven months and I was sure I would hear about it in the morning in front of everybody. I sat for ten minutes looking at the screen before I messaged my lead, and I wrote the message three times because the first two sounded like excuses. His reply was, "Do we have last night's backup?" We did. He restored it himself in about fifteen minutes, then asked me to add a coloured border to my terminal prompt so staging and the real system never look the same again. I said sorry twice and he waved it off. That was all. No lecture, no meeting. I did it the same evening, red for the real one and yellow for staging, and now I almost enjoy looking at it. What surprised me was not that he stayed calm, but how much more careful I felt afterwards compared to how I would have felt after being shouted at. I have been trying to remember this for the day I have juniors of my own. I also started reading my commands out loud before pressing enter, which sounds silly, but it works.

Did your lead ever tell the testing team, or did the Monday demo just run like nothing happened? I ask because my old manager quietly fixed one of mine and I only found out a year later.

I tried the coloured prompt idea at my last job in Gachibowli and it worked for about two months. After that my eyes stopped seeing the red, the same way you stop hearing a ceiling fan. What stuck was making the real database ask for a separate login that expires every hour. Annoying on busy days, but the extra step makes me stop and read which server I am on. Might just be how my brain works, though.

Friday at 6:40 with a bus in twenty minutes is when every one of my worst commands has happened.

This is such a refreshing story. Your lead handled it exactly how a good manager should focused on the fix, not the blame. The coloured terminal borders and reading commands aloud are simple but brilliant habits. It’s lovely that the experience made you more careful without leaving you scared. Your future juniors are lucky to have you.

Your lead asking about the backup first is exactly how a calm team behaves. In my first year I wiped the wrong table on a shared database, and my manager asked about restore time. The coloured prompt is a great fix, I also put the environment name in my terminal title. Reading commands aloud has saved me twice, so keep that habit even when you are senior.