this post was submitted on 27 Mar 2026
486 points (99.2% liked)

Programmer Humor

30680 readers
1636 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
486
Please don't delete the production DB (lemmy.zip)
submitted 4 days ago by favoredponcho@lemmy.zip to c/programmer_humor@programming.dev
33 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Xerxos@lemmy.ml 53 points 3 days ago (2 children)

Human developers should not develop with the production DB, why the hell would you give an AI the rights to touch the prod DB?

[–] favoredponcho@lemmy.zip 12 points 3 days ago (2 children)

You don’t test in production?

[–] qaatloz@lemy.nl 7 points 2 days ago

Everyone has a test environment, some are lucky to have a separate production environment.

[–] VibeSurgeon@piefed.social 0 points 3 days ago (2 children)

Dangerously-skip-permission is carte blanche for the model to do whatever it pleases with your system. If you happen to have access to a production database on your system, then the model also has access to it, should you use that option.

[–] eager_eagle@lemmy.world 7 points 3 days ago (1 children)

that assumes

  1. the user does have access to a production db;
  2. the agent has access to a terminal from which they can reach the production machine (not in a container, different network, or similar);
  3. access does not require interaction (like entering password);
  4. the agent deliberately decides to access a production database to solve a development problem, and that was not the user requesting it;
  5. the agent manages to find the database credentials in production;
  6. the agent is left unattended.

Possible? Sure. It's also possible that I drink half a bottle of vodka on a Friday night and mess up with production.

[–] VibeSurgeon@piefed.social 1 points 3 days ago

Naturally.

You should still probably not use dangerously-skip-permissions, though.

[–] minfapper@piefed.social 6 points 3 days ago* (last edited 3 days ago) (3 children)

Yes, but the question is why the hell do you have access to a production database in the first place?!

And if so, how is it on the same machine you can run Claude code on?!

[–] boonhet@sopuli.xyz 5 points 3 days ago

I've worked at places where senior devs have access to prod for emergency fixes but usually the procedure is to use a VPN AND an ssh key with a passphrase. Usually.

[–] firelizzard@programming.dev 3 points 3 days ago (1 children)

Startups and small companies where there simply aren’t enough resources to set up proper operational controls

[–] Bakkoda@lemmy.world 4 points 3 days ago

No no no I'm not running Dev ops on the production system. I'm running prod ops on the developer system.

[–] VibeSurgeon@piefed.social 1 points 3 days ago

I've worked at several places where I've been able to access production databases.

No need to be so dramatic about it, really.