Jr. front end dev says, "I know enough back end to be dangerous". Literally destroys entire codebase.

Well... he/she wasn't lying lol.

I know enough Git to restore any destruction you can do to the codebase.

Empty threats and what not!

@sterex we got it back up because, ya know, being distributed and all. He had learned about --force after being too impatient to fix a few merge conflicts, after he had tried removing almost the entire repository because he thought that removing everything would "reset" his machine. We lost a few commits. And a team member.

@tytho That is not a reason to lose a person. I'd rather have a person who has learned his lesson than a new one with potential to repeat it again.

Did his actions cause substantial monetary implications to the company? If not, I'm surprised that you let him go.

@tytho Besides, why did he even have access to push to production if he's a junior dev?

It's not entirely his fault.

@sterex he wasn't the one who left. He's still on the team, learned a hard lesson and moved forward. Another team member lost a hard day's work, got frustrated and left. It wasn't a full-time gig, just a side project working with students, so no livelihoods were affected.

Everything turned out for the best. Lessons were learned, rants were ranted, and we all moved on. I do thank you all for your concern, though

@tytho Aah.. All good then! 👍

Sounds a lot like me. Although I'm the senior Dev and was cloning my production site to a local machine. Accidentally started a restore on the production site almost rolling back content a year. (Prod site is a magazine) thankfully nothing was restored and there was no damage (and nobody noticed ;) )

Everyone has that one really really big mistake at the start of their career, it teaches a bit of humility. Personally I ended up taking down a production database I learned to fucking performance test stuff!