5 ms·

Very offtopic but this caught my eye: > Total repos cloned: 669 How big is this company? All the numbers I can find online suggest well below 100 people, and

by progbits 10mo ago

Very offtopic but this caught my eye: > Total repos cloned: 669 How big is this company? All the numbers I can find online suggest well below 100 people, and yet they have over 600 repos? Is that normal?

rsyring 10mo ago
My org is currently at 7 people and we have 365 repositories associated with our github org. We've been around for a number of years and I'd guess that impacts the number of repos more than the number of team members.
LtWorf 10mo ago
If they have an architect that loves microservices and thinks every microservice needs its own repo that's what happens (insanity).
lmm 10mo ago
Completely normal yes. Repos are cattle not pets.
- voidnap 10mo ago
  > Repos are cattle not pets. What do you mean by this?
  - arkits 10mo ago
    You can have more than a few
  - a_vanderbilt 10mo ago
    A core SRE principle is that "machines/servers are cattle, not pets". They shouldn't be special or bespoke in a way that makes replacement painful or difficult.
    - voidnap 10mo ago
      I've heard the term used for servers before but not version control repositories. I just don't understand what it would mean for a git repo to be a cattle vs a pet. Like what is an example of a cattle repo vs a pet repo. The metaphore just sounds like gibberish to me idk. Unless all it means is that that you can have more than a few like the other commenter said but I didn't think that was what the metaphore meant with respect to servers so again I have no idea lol
      - a_vanderbilt 10mo ago
        To me it would mean that a git repo should not have scripts, runners, etc. configured that we don't have the means to easily and readily replace. It should all be documented and understood well enough that we could kill the repo and init another at will.
SkyPuncher 10mo ago
We have a ratio of roughly 7:1 (repos to engineers). It was probably closer to 12:1 at some point. * Spikes/Demo project * Smaller projects that might have gone live, but have since been migrated elsewhere * Core services * Forks of certain supply chain dependencies that we've made improvements to.

rsyring 10mo ago

My org is currently at 7 people and we have 365 repositories associated with our github org. We've been around for a number of years and I'd guess that impacts the number of repos more than the number of team members.

LtWorf 10mo ago

If they have an architect that loves microservices and thinks every microservice needs its own repo that's what happens (insanity).

lmm 10mo ago

Completely normal yes. Repos are cattle not pets.

voidnap 10mo ago
> Repos are cattle not pets. What do you mean by this?
- arkits 10mo ago
  You can have more than a few
- a_vanderbilt 10mo ago
  A core SRE principle is that "machines/servers are cattle, not pets". They shouldn't be special or bespoke in a way that makes replacement painful or difficult.
  - voidnap 10mo ago
    I've heard the term used for servers before but not version control repositories. I just don't understand what it would mean for a git repo to be a cattle vs a pet. Like what is an example of a cattle repo vs a pet repo. The metaphore just sounds like gibberish to me idk. Unless all it means is that that you can have more than a few like the other commenter said but I didn't think that was what the metaphore meant with respect to servers so again I have no idea lol
    - a_vanderbilt 10mo ago
      To me it would mean that a git repo should not have scripts, runners, etc. configured that we don't have the means to easily and readily replace. It should all be documented and understood well enough that we could kill the repo and init another at will.

SkyPuncher 10mo ago

We have a ratio of roughly 7:1 (repos to engineers). It was probably closer to 12:1 at some point. * Spikes/Demo project * Smaller projects that might have gone live, but have since been migrated elsewhere * Core services * Forks of certain supply chain dependencies that we've made improvements to.