Ever worked in a company with micro services or a company that has a bunch of employees? You'll have hundreds of projects easily if it's a bunch of teams. If someone tells me "it's in our SRE libs package" I'll go ahead and search that. (Usually I can't find it because it's in a separate namespace on our Gitlab instance. Doing that is an Enterprise only feature on Gitlab right now: https://docs.gitlab.com/ee/user/search/advanced_global_searc...)
The point is that search is important and not a social network gimmick.
Yep, same here. We architected our services so that a common layer could be used which reduces service duplication but still we have over 700 projects for just one company doing end-to-end ecommerce and fulfillment. At some point you even start running out of names so you end up with people using acronyms from their specific fields which quickly ends up being unfindable. Not because of search but because you no longer know what to search for.
Actually, it doesn't even have to be microservices. At my current workplace we have over 1000 projects in our Gitlab. And many of those projects are a collection of up to 20 libraries.
Ever worked in a company with micro services or a company that has a bunch of employees? You'll have hundreds of projects easily if it's a bunch of teams. If someone tells me "it's in our SRE libs package" I'll go ahead and search that. (Usually I can't find it because it's in a separate namespace on our Gitlab instance. Doing that is an Enterprise only feature on Gitlab right now: https://docs.gitlab.com/ee/user/search/advanced_global_searc...)
The point is that search is important and not a social network gimmick.