this post was submitted on 09 Jan 2025
273 points (98.2% liked)

Programmer Humor

19932 readers
2085 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
 
top 18 comments
sorted by: hot top controversial new old
[–] Aceticon@lemmy.dbzer0.com 1 points 12 hours ago

The first sign that the company you just joined is amateur hour, every hour of the day, every day of the year is that they don't have a Staging environment.

[–] sylver_dragon@lemmy.world 47 points 1 day ago

Every site has a dev environment, some are lucky enough to have a separate production one.

[–] slazer2au@lemmy.world 45 points 1 day ago

Oooh, look at Mr fancy with a seperate Dev/prod environment.

[–] Vinny_93@lemmy.world 30 points 1 day ago (2 children)

Dev is a messy playground several months behind prod

[–] ravermeister@lemmy.rimkus.it 35 points 1 day ago (2 children)

Dev is a messy playground several months ahead of prod 😁

[–] SpaceNoodle@lemmy.world 6 points 1 day ago (1 children)

Right? What does OC think dev is?

[–] MajorHavoc@programming.dev 8 points 1 day ago* (last edited 1 day ago) (1 children)

They're referring to the tendency to reload the dev environment from production a couple times each year, while production is being tweaked daily without any record of changes applied.

Remember, however bad our own shop is, someone out there puts up with crap that even our own team doesn't have to put up with.

[–] SpaceNoodle@lemmy.world 3 points 1 day ago (1 children)

My point is that cowboying changes into prod is bad practice.

[–] MajorHavoc@programming.dev 3 points 1 day ago (1 children)

Lol. Yeah. Your point stands.I'm not disagreeing with or trying to correct you. Sorry if my comment came across that way.

I'm just trying to commiserate that cowboying changes into production is so common that it is some folk's work reality, even on well run teams - i.e. when their peer's teams are poorly run.

[–] SpaceNoodle@lemmy.world 2 points 1 day ago

That is when you cast the team into the fire

[–] marcos@lemmy.world 4 points 1 day ago

Well, is some mix of alternative futures that may or may not pan-out on reality.

[–] muntedcrocodile@lemm.ee 3 points 1 day ago

Its terrifying how true this is.

[–] steventhedev@lemmy.world 12 points 1 day ago* (last edited 1 day ago)
When I was a young dev
My senior took me into the city
To push my code to prod
He said "Son, when you promo
Would you be the savior of the broken
The buggy and the OOM'd?"

last place I worked had an environment refered to as poc/staging. poc. staging. these are supposed to be as far apart as possible in a non prod environment not combined.

[–] GissaMittJobb@lemmy.ml 8 points 1 day ago (1 children)

This is what feature flags are for. You can test in production to your hearts content if you use them!

[–] MajorHavoc@programming.dev 10 points 1 day ago

Yeah. Warning - uninvited poetic waxing on feature flags and leadership choices, incoming...

We all agree we inevitably do some live testing at our customers risk, because no test environment is perfect.

With feature flags, we're able to negotiate how many of our customers to test on, at a time.

But some of us prefer to forgo feature flags and risk our entire customer base on every change. It saves money, at least for a little while.

I'm not exactly fun at executive leadership meetings, but somehow I keep getting invited to them. Heh.

[–] MaggiWuerze@feddit.org 5 points 1 day ago

My job is in that picture and I don't like it

[–] Bronzebeard@lemm.ee 2 points 1 day ago

That's what staging is for...