Megacorporation Repos vs Cargo Cult

Repos at Megacorporations We put all of Windows in one git repo so developers only need 1 PR to make changes. We put all 2 billion lines of our webservices in a single repo to make life easy for developers. All 20 million lines of Linux kernel are in one git repo so every developer can have their own copy. Repos at small, cargo culting companies Every library and executable should have its own repo for scalability. Added a function to a library? Bump the semver and make a PR into every repo that depends on it to update the requirement. Changing one thing needs PRs into 5 repos with 2 Approval each. This is just how it’s done in the real world. Having everything in its own repo will enable code reuse (AKA legacy crap that will never die).

A comparison contrasts centralized repositories at huge technology companies with excessive repository fragmentation at small cargo-culting companies. The top panels portray confident, powerful Wojak figures, while the bottom panels show distressed and decaying figures surrounded by needless complexity. The joke mocks copying enterprise practices without understanding their context, resulting in maintenance overhead, redundant pull requests, and legacy code.

• @profunctor_io / 10219 2024-07-14