This is fantastic; this was always a hunch I had but you've put metrics behind the cost of unreviewed code. We just signed up two more of our repos for analysis.
This is just the beginning for sharing metrics like this. We're looking forward to feedback on this batch of results which will help form other analyses that would be interesting to see about the dev process in general.
We believe there's a lot of information locked in dev tools like code review that can shed quantitative light on how those processes lead to successes or failures in development. This is in partnership with the kind of anecdototes and best practices experienced devs and managers already frequently share.
We believe there's a lot of information locked in dev tools like code review that can shed quantitative light on how those processes lead to successes or failures in development. This is in partnership with the kind of anecdototes and best practices experienced devs and managers already frequently share.