Comment by nihzm

While technically impressive, the number of git commits without looking at the content is either a loose proxy for the speed of change of the codebase or a finer time resolution of the changesets. But this says little or nothing about whether this is useful for anything related to their products. So what is this for? They are not employing the same number of engineers as Google, so what is the point of scaling the number of commits? Flooding with git commit messages as "documentation" until the volume becomes unmanageable? Or changing the code at as speed that makes every single engineer lose the overview? I wonder.