> But Gitlab is an example of a company that is moving too fast I've studied GitLab's code history for a while, and they have been moving at a very fast pace f

> But Gitlab is an example of a company that is moving too fast I've studied GitLab's code history for a while, and they have been moving at a very fast pace for years now. Below is a one year window (from today) into to their gitlab repo. https://imgur.com/HOh5Zrr https://imgur.com/HOh5Zrr https://imgur.com/snU8UfY https://imgur.com/snU8UfY https://imgur.com/DDxD3lN https://imgur.com/DDxD3lN Some points of interest are: 1) 15k commits are merge commits. 2) The vast majority of the code churn is ruby, which is expected. 3) Based on the bus factor, a lot of files that are iterated on, have less than 10 unique contributors. And there are a handful of files that are iterated on a lot, by a lot of people. 4) A lot of the code changes are 10 lines of churn (lines added, changed, deleted) or less, which indicates incremental improvements/bug fixes/etc., as opposed to adding new functionality. Something that I'm not doing right now, is mapping the churn, to the number of unique contributors. It would be interesting to see if there is a pattern to their churn vs number of contributors. GitLab is definitely moving at a very fast pace, and it would be interesting to map this to their issues, but their API is extremely slow, so I've never bothered trying. Edit: For the scatter charts, the x-axis represents the number of files. And the y-axis is number of contributors (bus factor chart) and churn size (churn chart)