this post was submitted on 24 Feb 2024
1509 points (99.3% liked)

Programmer Humor

20778 readers
1390 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
[–] tsonfeir@lemm.ee 4 points 1 year ago (1 children)

For the production environment, not in it.

[–] Knock_Knock_Lemmy_In@lemmy.world 1 points 1 year ago (1 children)

Shouldn't every decision be tested in dev first?

[–] tsonfeir@lemm.ee 1 points 1 year ago (1 children)

Yes. I think you may have misunderstood my meaning. Unless you’re just being pedantic—which I have no interest in.

[–] Knock_Knock_Lemmy_In@lemmy.world 1 points 1 year ago (1 children)

Probably my misunderstanding. The way it is written it sounds like juniors use the dev env and seniors get their decisions implemented directly in prod.

[–] tsonfeir@lemm.ee 1 points 1 year ago (1 children)

What are “decisions” to you?

[–] Knock_Knock_Lemmy_In@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

From what code to write, to what language to use, to how things will integrate.

Even high level architectural decisions need to be tested in dev first.

Basically I can't see what couldn't be run through dev first?

[–] tsonfeir@lemm.ee 2 points 1 year ago

Just because code works in dev doesn’t mean it’s going to be the right thing for production. I caught that little bastard making 1000 db queries in a loop one time, instead of taking the time to make it efficient. Technically it worked. And, because dev has no server load, it was relatively quick.