Nick here, CEO/Founder of AutoDevTech. The team and I are proud to release AutoDev Analytics: reports and benchmarks measuring dev processes based on thousands of big, popular projects on GitHub. We want to share what we’ve learned about the dev process and code review, get feedback, and open up free analytics that compare your team against thousands of other code bases.<p>We’ve got stats showing most code doesn’t get any feedback in code review[1], unreviewed code is twice as likely to churn out over a year than reviewed code[2], and teams spend about 3 hours per week reviewing code[3]. And we’ve got benchmarks for dozens of other metrics like code review turnaround and monthly codebase churn.<p>Take a look, sign up for analytics and let us know what you think.<p>[1] <a href="http://www.autodevtech.com/benchmark/scorecard/denoland/deno/" rel="nofollow">http://www.autodevtech.com/benchmark/scorecard/denoland/deno...</a>
[2] <a href="http://www.autodevtech.com/benchmark/scorecard/nodejs/node/churn/" rel="nofollow">http://www.autodevtech.com/benchmark/scorecard/nodejs/node/c...</a>
[3] <a href="http://www.autodevtech.com/benchmark/scorecard/puppeteer/puppeteer/engagement/" rel="nofollow">http://www.autodevtech.com/benchmark/scorecard/puppeteer/pup...</a>
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.