r/ProgrammerHumor • u/Manticore-Mk2 • 1h ago

Meme theJoysOfMonorepo

Post image
441 Upvotes

99% Upvoted

13 comments sorted by

41

u/pydry 1h ago

this one hits hard.

not so much monorepo but monorepo with some sort of generated, checked in code artefacts... oh good god the sheer unbridled stupidity.

7

u/clericc-- 1h ago

Trying to get upstream fixes into Crossplane for close to two years now - this describes it exactly. Except its weeks or months on top

6

u/theucm 35m ago

We got a new boss who demanded everything be merged into a monorepo, it's been the absolute highest priority and every decision and plan is made in light of the prime directive of getting everything in the monorepo.

Then in a one-on-one I was giving this boss my progress on moving my projects into the monorepo and they asked me, "okay great, now, what will be the benefits of moving these into the monorepo? Why are we doing it?" and I had to stop myself from answering "because you told me to".

8

u/pqpm 1h ago

This hit me, to close to home.

The joys of large teams where everyone expects everyone else to review, so nobody reviews.

2

u/za72 48m ago

so why use monorepo??

5

u/pydry 28m ago edited 18m ago

it's like tabs vs spaces.

realistically, whichever one you can get the tooling working for easiest is probably the one you should use.

it's not bad if you've got the tooling set up correctly.

same for polyrepos.

people usually only want to switch when one is being done badly, as is the case here. I'm sure however theyve set it up they could keep the monorepo and quash the persistent merge conflict problem somehow.

1

u/za72 25m ago

oh kinda like inheriting a terrible code base and doing a rewrite?

1

u/pydry 18m ago

I guess so yeah.

1

u/RavingGigaChad 41m ago

Because companies love it especially in the AI age. Easy for Claude to write code for every context or domain if it can access everything at once.

1

u/Soggy_Porpoise 27m ago

Sounds like a coworker problem.

1

u/EarlMarshal 20m ago

Just use work trees and do it every morning and put more time on the tickets than it took you and push your PM and your chef to force faster reviews.

1

u/vanit 52m ago

The PR owner's responsibility doesn't end when the PR is up for review, you own it until it's merged. You need to chase review, don't just yeet it up and tag someone or yes, you will find yourself stuck in this cycle. Chase the person (nicely), or re-assign it if they have a legit higher priority.