Companies that speak about the subject seem to choose either the monorepo approach or the complete opposite, with thousands of them (several repositories per de

Companies that speak about the subject seem to choose either the monorepo approach or the complete opposite, with thousands of them (several repositories per developer !) Is anyone using one repository per team, in order to share code more easily but without the need for complex tools that can deal with a true monorepository (not everyone can build something like Piper/Blaze)?