There is a lot of developer movement between the companies cited and it's not surprising that people take the practices they're familiar with to their new employer.
Companies incentivize people to deprecate feature X and replace it with feature Y and celebrate the win. Much harder without a monorepo.
The counter argument is open source, where the development follows the distributed model and the difficulty of syncing the monorepo with a custom build system. Figuring out a way to leverage the QA work distro people do in coming up with a consistent cut + patches would benefit everyone regardless of repo structure.
There is a lot of developer movement between the companies cited and it's not surprising that people take the practices they're familiar with to their new employer.
Companies incentivize people to deprecate feature X and replace it with feature Y and celebrate the win. Much harder without a monorepo.
The counter argument is open source, where the development follows the distributed model and the difficulty of syncing the monorepo with a custom build system. Figuring out a way to leverage the QA work distro people do in coming up with a consistent cut + patches would benefit everyone regardless of repo structure.