this post was submitted on 14 Jul 2026

600 points (99.0% liked)

Programmer Humor

32286 readers

1663 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 3 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

600

Tech bros having their production environments nuked by AI is never gonna get old (suppo.fi)

submitted 22 hours ago by cm0002@suppo.fi to c/programmer_humor@programming.dev

105 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] placebo@lemmy.zip 9 points 20 hours ago (1 children)

As well as storing production credentials in plan text in an .env file.

[–] The_Decryptor@aussie.zone 3 points 14 hours ago (2 children)

.env files are wild to me, environment variables have never been a good way to pass data to applications, let alone secret data.

So the solution people came up with was to store them in plain text next to the binary, and then have a loader apply them before running the main app.

[–] placebo@lemmy.zip 1 points 3 hours ago

The data isn't supposed to be secret, I think. We use .env files to store creds required for development, like a connection url for my local database. Production apps don't use .env files at all.

[–] dgriffith@aussie.zone 2 points 8 hours ago

But they needed those .env files to transplant an entire software stack from the developer's laptop into production in a reproducible manner! How else were they ever going to get software into prod? By good documentation, broad version requirements, and following the Robustness Principle? Ha! How are you supposed to move fast and break things then?