Speeding up code review with `small-change`
Imprint's average engineer is merging 4x more PRs than 2 years ago. Yay.
Aggregated behind the average is something even more interesting:
we have two teams that are merging 10x their PRs over that period.
One engineer is merging 25x the PRs per week of our average engineer two years ago,
and a number of others are closing in on that number.
That's pretty neat, and the slope of the line suggests our average in a year is going to look much closer to
today's p90 than today's p50.
Even more importantly, we aren't just shipping more, our quality has improved:
incidents are down 42% half-over-half, and critical incidents are down 78% half-over-half.
I think we've always known the quality/velocity tradeoff wasn't a particularly useful
construct, but that's undeniable today.
Aggregated behind the average is something even more interesting:
we have two teams that are merging 10x their PRs over that period.
One engineer is merging 25x the PRs per week of our average engineer two years ago,
and a number of others are closing in on that number.
That's pretty neat, and the slope of the line suggests our average in a year is going to look much closer to
today's p90 than today's p50.
Even more importantly, we aren't just shipping more, our quality has improved:
incidents are down 42% half-over-half, and critical incidents are down 78% half-over-half.
I think we've always known the quality/velocity tradeoff wasn't a particularly useful
construct, but that's undeniable today.
Summary
Imprint’s engineers are significantly more productive, merging four times more pull requests (PRs) than they did two years ago. Notably, two teams are merging ten times their previous rate, with one engineer merging 25 times the average from two years ago. The trend indicates that the average PR merge rate is expected to rise, approaching the current 90th percentile within a year.
Comments (9 of ) ⌛