I added guardrails to myself to make sure I do not accidentally delete anything on production. I would never ever let an intern, a junior dev or a fucking AI onto that database. Not in a thousand cold nights.

[–] Omgpwnies@lemmy.world 16 points 10 hours ago (1 children)

Prod should always be highly "air gapped" with some sort of deployment process which tests not only the code to be deployed but also the deployment itself. I've been doing QA for a good while now, and everywhere I've worked has testers dedicated to testing the actual update process to make sure it will be safe when deployed.

[–] SeductiveTortoise@piefed.social 9 points 10 hours ago

And I won't open the DB without making sure I'm read only. If I need to mutate data or schema, I'll switch roles and have a dry run first.