this post was submitted on 10 Jul 2025
460 points (96.2% liked)

memes

16483 readers
2911 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 2 years ago
MODERATORS
 

Rolling, rolling, rolling back nothing I love more than communicating why we had to roll back again (⁠ノ⁠ಠ⁠益⁠ಠ⁠)⁠ノ

all 35 comments
sorted by: hot top controversial new old
[–] ViatorOmnium@piefed.social 71 points 2 weeks ago (1 children)

Question 1: Where's the CI/CD pipeline?
Question 2: Why can one person change production alone without peer review (outside of an emergency)?

You don't have a job, you have a ticking time bomb.

[–] ComfortableRaspberry@feddit.org 22 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

It's internal development (Portugal) developing something for an internal department (Germany). There's nothing professional going on here so we are far from any ci/cd pipeline. One person can change everything, because it's just two developers (1 frontend, 1 backend).

Plus things are busy and we (team in Germany) are way more interested in this thing working well than they (team in Portugal) are since they have higher priority tasks..

Of course I can say fuck it and live with the poor quality caused by circumstances that were partially caused by poor management decisions of the company but I'm not able to care little enough.

[–] JackLSauce@lemmy.world 16 points 2 weeks ago (2 children)

Pre-commit hooks don't require a pipeline nor any money. In most cases it's one line of code to make the tests run every commit

[–] dejected_warp_core@piefed.world 4 points 2 weeks ago

Even better: use pre-commit. It supports all kinds of stuff without a lot of config. This gets you (and GP) a lot of the features of a full-blown CI pipeline, but it all runs locally before anyone breaks anything.

[–] SandmanXC@lemmy.world 1 points 2 weeks ago (4 children)

Stop me from committing my work and I will hunt you down to the ends of the earth.

[–] kkj@lemmy.dbzer0.com 21 points 2 weeks ago (2 children)

Fix your shit and it won't stop you from committing.

It's also usually only on certain branches, so you can make a branch where you break things and then fix them before you merge to testing/main/whatever.

[–] SandmanXC@lemmy.world 6 points 2 weeks ago

TIL precommit hooks can be set per branch. I was being facetious to begin with but this sounds pretty good actually.

[–] chellomere@lemmy.world 1 points 2 weeks ago (1 children)

Nah, at our place it's applied on all branches...

[–] kkj@lemmy.dbzer0.com 2 points 2 weeks ago (2 children)

What do you do if you have code that isn't complete enough to work? Do you have to just leave it untracked?

[–] chellomere@lemmy.world 2 points 2 weeks ago

I don't know what others do, but I personally whip out git commit -n and bypass the hooks in this situation.

[–] 4am@lemmy.zip 3 points 2 weeks ago

Take down prod while I’m on call and seeing my kid and I shall return the favor

[–] JackLSauce@lemmy.world 2 points 2 weeks ago (1 children)

I get that a lot

Getting threats over one line of code is called senior development

[–] SandmanXC@lemmy.world 1 points 2 weeks ago

Don't worry I'm too lazy to hunt you down farther than the coffee shop next to me.

[–] chellomere@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago)

I agree. I absolutely hate when some pesky git hook rejects some debug code I wrote that I want to commit. Mind you, commit, not integrate. This is the situation where I whip out git commit -n.

[–] surewhynotlem@lemmy.world 11 points 2 weeks ago

I demand CI/CD for my scripts. If it runs in prod or against prod or anywhere near prod, it gets a pipeline.

Technical maturity isn't just for big companies and important things. It's a practice. Why half-ass something when you could whole ass it?

[–] folekaule@lemmy.world 32 points 2 weeks ago

It doesn't have to be that way, if you have a CI/CD process that prevents it.

[–] Lulzagna@lemmy.world 23 points 2 weeks ago (3 children)

Why kind of psychos are merging with failing tests?

[–] CosmicTurtle0@lemmy.dbzer0.com 14 points 2 weeks ago (1 children)

The kinds of psychos that work at companies that measure performance by number of commits and PRs, successful or not.

[–] elvith@feddit.org 6 points 2 weeks ago

That explains why vibe coding is so popular… just commit after every iteration the LLM spits out

[–] brezel@piefed.social 2 points 2 weeks ago (1 children)

the real question is why doesn't the CI/CD prevent merging with failing tests in the first place. i have not worked in any company that allowed that for at least 15 years.

[–] fushuan@piefed.blahaj.zone 4 points 2 weeks ago (1 children)

Rn I'm in a project where everyone that has access to the code is given the role of owner of the group so we have permissions to skip any and all measures since owners don't care.

I'm so happy that tomorrow is my last day. So happy.

[–] brezel@piefed.social 1 points 2 weeks ago

haha, i can imagine :)

[–] bleistift2@sopuli.xyz 1 points 2 weeks ago

The kind of psychos that have “nice to have” tests. If it’s red, it’s not critical, but still worthy of attention… sometime.

[–] jatone@lemmy.dbzer0.com 11 points 2 weeks ago

because they know better than your tests obv.

[–] atomicbocks@sh.itjust.works 9 points 2 weeks ago

You guys get to test?

[–] LegitimateEngineer@lemmy.world 8 points 2 weeks ago

Proper procedure would have been the dev updating the uts so that they pass. If all they updated was adding ignore or commenting out code in the ut, even better!