concepts missing from the article: 'staging' and 'commit size'.
People who have worked in code review shops tend to stage their commits, i.e. do a bunch of work but commit it with git commit -p.
Article also doesn't look at deployment frequency, and 'merge' appears only once. We don't know if these 'high impact' devs are in their own branch for 6 weeks cooking up the PR from hell. That's one way to have a high impact.
People who have worked in code review shops tend to stage their commits, i.e. do a bunch of work but commit it with git commit -p.
Article also doesn't look at deployment frequency, and 'merge' appears only once. We don't know if these 'high impact' devs are in their own branch for 6 weeks cooking up the PR from hell. That's one way to have a high impact.