Hacker News with Generative AI: Monorepos

The Ingredients of a Productive Monorepo (swgillespie.me)
So! Suppose you’re an intrepid engineer in a nascent Developer Productivity team. Your engineering organization has decided that it wants to move towards a monorepo. You’ve heard the stories told of Google, Meta, Uber - each a large technology company with developer productivity organizations consisting of hundreds of engineers - and you want to capture some of their magic in a bottle and give it to your users. You wonder - what work lies ahead of you?
Monorepo – Our Experience (ente.io)
Nine months ago, we switched to a monorepo. Here I describe our experience with the switch so far.
We shrunk our Javascript monorepo git size (jonathancreamer.com)
This isn't click bait. We really did this! We work in a very large Javascript monorepo at Microsoft we colloquially call 1JS. It's large not only in terms of GB, but also in terms of sheer volume of code and contributions. We recently crossed the 1,000 monthly active users mark, about 2,500 packages, and ~20million lines of code! The most recent clone I did of the repo clocked in at an astonishing 178GB.
Show HN: Monogo – Evolve your go workspace to a real monorepo (github.com/nicolasgere)
Stripe's Monorepo Developer Environment (nelhage.com)
Ask HN: Best Tools for Monorepo? (ycombinator.com)
Ask HN: Startups – Are you on a monorepo or multi-repo set up? (ycombinator.com)
Monorepos: Please Don't (2019) (medium.com)