this post was submitted on 03 Mar 2024
1090 points (97.8% liked)

Programmer Humor

19821 readers
896 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] 1984@lemmy.today 2 points 9 months ago (1 children)

I never worked anywhere where they had this set up. I would push to branches and make pull requests, but always work in the production environment.

I was mainly working as a data engineer though so that's probably why. It's hard to have test environments since you can't replicate all the enormous amounts of data between environments without huge costs.

[–] expr@programming.dev 3 points 9 months ago (1 children)

There are many strategies for maintaining test environments for that kind of thing. Read-only replicas, sampling datasets for smaller replicas, etc. Plenty of organizations do it, so it's not really an excuse, imo.

[–] 1984@lemmy.today 2 points 9 months ago* (last edited 9 months ago)

No I know. But it was "good enough" for the company and we never had any serious issues working that way either. If someone pushed a faulty commit, we just reverted it and reloaded the data from the source system.

A lot of companies have kind of bad solutions for this sort of stuff, but it's not talked about and nobody is proud of it. But it keeps the environments simple to work with.