Although the author of the post obviously did a huge mistake, he is far from being the actual responsible for the problem that follows his mistake. It's the job of the CTO to make sure no one can harm the company main product this way, accidentaly or not.
He could never write code against the production database when developing new features. And if he was doing it, it wasn't his fault, considering he was a junior developer.
And who the hell is so stupid to don't have any recent backup for the database used by a piece of software that provides millions of revenue?
In the end, when you do such a shity job protecting your main product, shit will eventually happens. The author of the post was merely a agent of destiny.
He could never write code against the production database when developing new features. And if he was doing it, it wasn't his fault, considering he was a junior developer.
And who the hell is so stupid to don't have any recent backup for the database used by a piece of software that provides millions of revenue?
In the end, when you do such a shity job protecting your main product, shit will eventually happens. The author of the post was merely a agent of destiny.