AI-Assisted Assessment of Coding Practices in Modern Code Review

Design and code inspections to reduce errors in program development

M. E. Fagan. 1976 · 1976

Earlier work this paper cites.

Lint, a C program checker

Stephen C Johnson. 1977 · 1977

Earlier work this paper cites.

A systematic literature review of actionable alert identification techniques for automated static code analysis

Sarah Heckman and Laurie Williams. 2011 · 2010

Earlier work this paper cites.

Contemporary Peer Review in Action: Lessons from Open Source Development

Peter Rigby, Brendan Cleary, Frederic Painchaud, Margaret-Anne Storey, and Daniel German. 2012 · 2012

Earlier work this paper cites.

Expectations, outcomes, and challenges of modern code review. In 2013 35th International Conference on Software Engineering (ICSE) . 712–721

Alberto Bacchelli and Christian Bird. 2013 · 2013

Earlier work this paper cites.

Why don’t software developers use static analysis tools to find bugs?. In 2013 35th International Conference on Software Engineering (ICSE) . IEEE, 672–681

Brittany Johnson, Yoonki Song, Emerson Murphy-Hill, and Robert Bowdidge. 2013 · 2013

Earlier work this paper cites.

Convergent contemporary software peer review practices. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering (Saint Petersburg, Russia) (ESEC/FSE 2013) . Association for Computing Machinery, New York, NY, USA, 202–212

Peter C. Rigby and Christian Bird. 2013 · 2013

Earlier work this paper cites.

Analyzing the state of static analysis: A large-scale evaluation in open source software. In 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) , Vol. 1. IEEE, 470–481

Moritz Beller, Radjino Bholanath, Shane McIntosh, and Andy Zaidman. 2016 · 2016

Earlier work this paper cites.

Why Google Stores Billions of Lines of Code in a Single Repository

Rachel Potvin and Josh Levenberg. 2016 · 2016

Earlier work this paper cites.

Modern Code Review: A Case Study at Google. In International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) . 181–190

Caitlin Sadowski, Emma Söderberg, Luke Church, Michal Sipko, and Alberto Bacchelli. 2018 · 2018

Cited alongside, same era.

Code Coverage at Google. In Proceedings of the Joint Meeting of the European Software Engineering Conference and the Symposium on the Foundations of Software Engineering (ESEC/FSE) . 955–963

Marko Ivanković, Goran Petrović, René Just, and Gordon Fraser. 2019 · 2019

Cited alongside, same era.

How developers engage with static analysis tools in different contexts

Carmine Vassallo, Sebastiano Panichella, Fabio Palomba, Sebastian Proksch, Harald C Gall, and Andy Zaidman. 2020 · 2020

Cited alongside, same era.

Software Engineering at Google: Lessons Learned from Programming Over Time

T. Winters, T. Manshreck, and H. Wright. 2020 · 2020

Cited alongside, same era.

Please fix this mutant: How do developers resolve mutants surfaced during code review?. In International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP) . 150–161

Goran Petrović, Marko Ivanković, Gordon Fraser, and René Just. 2023 · 2023

Later among the works it cites.

Scaling up models and data with t5x and seqio

Adam Roberts, Hyung Won Chung, Gaurav Mishra, Anselm Levskaya, James Bradbury, Daniel Andor, Sharan Narang, Brian Lester, Colin Gaffney, Afroz Mohiuddin, et al · 2023

Later among the works it cites.

Google Style Guides

2024 · 2024

Closest in time.

Linux kernel coding style

2024 · 2024

Closest in time.

PEP 8 – Style Guide for Python Code

2024 · 2024

Closest in time.

Rust Style Guide

2024 · 2024

Closest in time.