5 ms·

I’ve heard about how huge companies like google are using a giant monorepo, and I honestly don’t understand how that could work. But I guess it does…

j45 2y ago
It's sometimes important to remind ourselves that just because we can't see understanding in something doesn't mean there isn't understanding in it, and it might take effort on our part. It's not a negative thing as much as an opportunity to grow if we ask ourselves to learn and see it as an opportunity.
inhumantsar 2y ago
with lots of controls and custom tooling
- verdverm 2y ago
  Facebook open sourced theirs https://github.com/facebook/sapling https://github.com/facebook/sapling
  - gladwindos 2y ago
    This looks interesting! I'll check it out and maybe it will help me wrap my head around how they handle the complexity.
    - verdverm 2y ago
      If you aren't worried about partial checkouts & permissions The biggest issue is deciding what to build across developers and their branches & products. You don't want to build the world on every commit, but you do want to ensure that you are building what the code would look like post-merge before the merge.
tail_exchange 2y ago
The company I work at is fairly large, with thousands of engineers, and we use monorepos. It works extremely well. What about them makes you think it can't work?
- gladwindos 2y ago
  We use monorepos in my company too, but we use one for each product, and it works really well for that. But for the whole company to be in a single monorepo just seems like it would require a lot of effort to maintain.
  - tail_exchange 2y ago
    We have several projects per monorepo, and they are massive, currently being merged into a single one. Anything specific about maintainability that scares you?
- CRConrad 2y ago
  > ...we use monorepos. MonorepoS, in the plural?
  - tail_exchange 2y ago
    Yes. We used to have dozens of repos, but started to merge them slowly. Nowadays we have 3 large ones, but the goal is 1.
    - CRConrad 2y ago
      So you have Trirepo, not monorepo.
      - tail_exchange 2y ago
        Looking forward to the birepo.

j45 2y ago

It's sometimes important to remind ourselves that just because we can't see understanding in something doesn't mean there isn't understanding in it, and it might take effort on our part. It's not a negative thing as much as an opportunity to grow if we ask ourselves to learn and see it as an opportunity.

inhumantsar 2y ago

with lots of controls and custom tooling

verdverm 2y ago
Facebook open sourced theirs https://github.com/facebook/sapling https://github.com/facebook/sapling
- gladwindos 2y ago
  This looks interesting! I'll check it out and maybe it will help me wrap my head around how they handle the complexity.
  - verdverm 2y ago
    If you aren't worried about partial checkouts & permissions The biggest issue is deciding what to build across developers and their branches & products. You don't want to build the world on every commit, but you do want to ensure that you are building what the code would look like post-merge before the merge.

tail_exchange 2y ago

The company I work at is fairly large, with thousands of engineers, and we use monorepos. It works extremely well. What about them makes you think it can't work?

gladwindos 2y ago
We use monorepos in my company too, but we use one for each product, and it works really well for that. But for the whole company to be in a single monorepo just seems like it would require a lot of effort to maintain.
- tail_exchange 2y ago
  We have several projects per monorepo, and they are massive, currently being merged into a single one. Anything specific about maintainability that scares you?
CRConrad 2y ago
> ...we use monorepos. MonorepoS, in the plural?
- tail_exchange 2y ago
  Yes. We used to have dozens of repos, but started to merge them slowly. Nowadays we have 3 large ones, but the goal is 1.
  - CRConrad 2y ago
    So you have Trirepo, not monorepo.
    - tail_exchange 2y ago
      Looking forward to the birepo.