Poor guy is done for! ...

https://thenewstack.io/junior-dev-d...

Not necessarily. It's the companies fault for:
1. Giving the new hire production DB access without training them
2. Not having tested backups
3. Not taking responsibility

The problem was waiting to happen and this Jr. DB Engineer was the tipping point. Shit happens, people make mistakes. That's why Disaster Recovery is a thing. So I know they will be fine. They'll just have to live out the Bobby Tables nickname for a while. :P

@paralegalseagul hahahaha bobby tables!

I remember reading this one :D

Can happen everyone Gitlab even has somebody whose title is "Database (removal) specialist"
He once accidentally deleted the gitlab db. But they solved it on stream so they were really open about it.

Nope, not all. The CTO is the incompetent party in this. Any company that reacts like this to a non-malicious mistake isn't going be very profitable, or last very long. 1 - Always have tested and verified backups. 2 - Don't use production references is a setup guide for a new employee. 3 - Provide an experienced employee to assist with setup and configuration. 4 - Never belittle someone who has made a genuine mistake, no matter how big it is. Instead, ask them what lesson they have learned that will make them a better person.