Show HN: AutoDev Analytics Dev Measurement and Benchmark(autodevtech.com)
autodevtech.com
Show HN: AutoDev Analytics Dev Measurement and Benchmark
https://www.autodevtech.com/benchmark/
3 comments
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.
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.
Take a look, sign up for analytics and let us know what you think.
[1] http://www.autodevtech.com/benchmark/scorecard/denoland/deno... [2] http://www.autodevtech.com/benchmark/scorecard/nodejs/node/c... [3] http://www.autodevtech.com/benchmark/scorecard/puppeteer/pup...