165
submitted 9 months ago by Ephera@lemmy.ml to c/programmerhumor@lemmy.ml
top 13 comments
sorted by: hot top controversial new old
[-] dylanTheDeveloper@lemmy.world 40 points 9 months ago* (last edited 9 months ago)

The worst is when some mfr pushes code that doesn't compile so when you get latest the whole build is broken

[-] astrsk@kbin.social 29 points 9 months ago* (last edited 9 months ago)

CI and basic PR rules should gate this entirely… this should never be a problem.

[-] Sylvartas@lemmy.world 34 points 9 months ago

basic PR rules

My company's code leads :

[-] SpeakinTelnet@sh.itjust.works 18 points 9 months ago

No needs for pull requests when you commit directly to main.

[-] eager_eagle@lemmy.world 9 points 9 months ago

also remember to use --force when pushing, your colleagues will love you

[-] SpeakinTelnet@sh.itjust.works 8 points 9 months ago
git rebase -i --root
git commit --amend --no-edit
git push --force
[-] DmMacniel@feddit.de 5 points 9 months ago

use the force Luke!

[-] dylanTheDeveloper@lemmy.world 2 points 9 months ago

Working in a startup is truly an experience

[-] hex123456@sh.itjust.works 11 points 9 months ago

You owe 2 tokens to the “should jar”.

[-] s12@sopuli.xyz 3 points 9 months ago

I don’t get it. How can we tell this is in prod?

[-] Ephera@lemmy.ml 4 points 9 months ago

You can't tell that from the screenshot, but I can tell you that I took this screenshot on my Linux box, while upgrading my system packages as an end-user.

I believe, the problem comes from a community repo I added, which doesn't have to adhere to quite the same quality standards, but evidently they have some distinction between build envs and production envs, and well, I'm at least hoping that my laptop isn't deemed a build env... 🙃

[-] s12@sopuli.xyz 1 points 9 months ago

Ah! So build implies non-production?

[-] Ephera@lemmy.ml 3 points 9 months ago

My usage of the word "production" was a bit non-standard here, in case that confuses you.

Normally, it's used for hosted services, where you have the three hosted environments "development", "integration" and "production".

In this case, I'm guessing, it's rather the case that they had a build configuration for running it in their "build-env", so probably a CI/CD runner. And then there would be a different build configuration for when they're creating a release distribution.

In a very abstracted sense, the "production" environment is where you roll out your release distribution to, so if you will, my laptop is one of thousands of production environments for this application, but only tongue-in-cheek...

this post was submitted on 17 Feb 2024
165 points (96.1% liked)

Programmer Humor

32483 readers
166 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS