default search action
Peter C. Rigby
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
- [j9]Vijayaraghavan Murali, Chandra Shekhar Maddila, Imad Ahmad, Michael Bolin, Daniel Cheng, Negar Ghorbani, Renuka Fernandez, Nachiappan Nagappan, Peter C. Rigby:
AI-Assisted Code Authoring at Scale: Fine-Tuning, Deploying, and Mixed Methods Evaluation. Proc. ACM Softw. Eng. 1(FSE): 1066-1085 (2024) - [j8]Fahimeh Hajari, Samaneh Malmir, Ehsan Mirsaeedi, Peter C. Rigby:
Factoring Expertise, Workload, and Turnover Into Code Review Recommendation. IEEE Trans. Software Eng. 50(4): 884-899 (2024) - [c45]Samaneh Malmir, Peter Christopher Rigby:
Predicting the Lifetime of Flaky Tests on Chrome. FTW@ICSE 2024: 5-13 - [c44]Samaneh Malmir, Peter C. Rigby:
Predicting the Lifetime of Flaky Tests on Chrome. FTW@ICSE 2024: 5-13 - [c43]Omer Dunay, Daniel Cheng, Adam Tait, Parth Thakkar, Peter C. Rigby, Andy Chiu, Imad Ahmad, Arun Ganesan, Chandra Shekhar Maddila, Vijayaraghavan Murali, Ali Tayyebi, Nachiappan Nagappan:
Multi-line AI-Assisted Code Authoring. SIGSOFT FSE Companion 2024: 150-160 - [i7]Omer Dunay, Daniel Cheng, Adam Tait, Parth Thakkar, Peter C. Rigby, Andy Chiu, Imad Ahmad, Arun Ganesan, Chandra Shekhar Maddila, Vijayaraghavan Murali, Ali Tayyebi, Nachiappan Nagappan:
Multi-line AI-assisted Code Authoring. CoRR abs/2402.04141 (2024) - [i6]Chandra Shekhar Maddila, Negar Ghorbani, Kosay Jabre, Vijayaraghavan Murali, Edwin Kim, Parth Thakkar, Nikolay Pavlovich Laptev, Olivia Harman, Diana Hsu, Rui Abreu, Peter C. Rigby:
AI-Assisted SQL Authoring at Industry Scale. CoRR abs/2407.13280 (2024) - [i5]Rui Abreu, Vijayaraghavan Murali, Peter C. Rigby, Chandra Shekhar Maddila, Weiyan Sun, Jun Ge, Kaavya Chinniah, Audris Mockus, Megh Mehta, Nachiappan Nagappan:
Moving Faster and Reducing Risk: Using LLMs in Release Deployment. CoRR abs/2410.06351 (2024) - 2023
- [c42]Emad Fallahzadeh, Amir Hossein Bavand, Peter C. Rigby:
Accelerating Continuous Integration with Parallel Batch Testing. ESEC/SIGSOFT FSE 2023: 55-67 - [c41]Will Shackleton, Katriel Cohn-Gordon, Peter C. Rigby, Rui Abreu, James Gill, Nachiappan Nagappan, Karim Nakad, Ioannis Papagiannis, Luke Petre, Giorgi Megreli, Patrick Riggs, James Saindon:
Dead Code Removal at Meta: Automatically Deleting Millions of Lines of Code and Petabytes of Deprecated Data. ESEC/SIGSOFT FSE 2023: 1705-1715 - [c40]Audris Mockus, Peter C. Rigby, Rui Abreu, Parth Suresh, Yifen Chen, Nachiappan Nagappan:
Modeling the Centrality of Developer Output with Software Supply Chains. ESEC/SIGSOFT FSE 2023: 1809-1819 - [i4]Emad Fallahzadeh, Amir Hossein Bavand, Peter C. Rigby:
Accelerating Continuous Integration with Parallel Batch Testing. CoRR abs/2308.13129 (2023) - [i3]Peter C. Rigby, Seth Rogers, Sadruddin Saleem, Parth Suresh, Daniel Suskin, Patrick Riggs, Chandra Shekhar Maddila, Nachiappan Nagappan:
Improving Code Reviewer Recommendation: Accuracy, Latency, Workload, and Bystanders. CoRR abs/2312.17169 (2023) - [i2]Fahimeh Hajari, Samaneh Malmir, Ehsan Mirsaeedi, Peter C. Rigby:
Factoring Expertise, Workload, and Turnover into Code Review Recommendation. CoRR abs/2312.17236 (2023) - 2022
- [j7]Mohammad Javad Beheshtian, Amir Hossein Bavand, Peter C. Rigby:
Software Batch Testing to Save Build Test Resources and to Reduce Feedback Time. IEEE Trans. Software Eng. 48(8): 2784-2801 (2022) - [c39]Emad Fallahzadeh, Peter C. Rigby:
The Impact of Flaky Tests on Historical Test Prioritization on Chrome. ICSE (SEIP) 2022: 273-282 - [c38]Qianhua Shan, David Sukhdeo, Qianying Huang, Seth Rogers, Lawrence Chen, Elise Paradis, Peter C. Rigby, Nachiappan Nagappan:
Using nudges to accelerate code reviews at scale. ESEC/SIGSOFT FSE 2022: 472-482 - [c37]Lawrence Chen, Peter C. Rigby, Nachiappan Nagappan:
Understanding why we cannot model how long a code review will take: an industrial case study. ESEC/SIGSOFT FSE 2022: 1314-1319 - [c36]Lawrence Chen, Rui Abreu, Tobi Akomolede, Peter C. Rigby, Satish Chandra, Nachiappan Nagappan:
Leveraging test plan quality to improve code review efficacy. ESEC/SIGSOFT FSE 2022: 1320-1330 - [c35]Yifen Chen, Peter C. Rigby, Yulin Chen, Kun Jiang, Nader Dehghani, Qianying Huang, Peter Cottle, Clayton Andrews, Noah Lee, Nachiappan Nagappan:
Workgraph: personal focus vs. interruption for engineers at Meta. ESEC/SIGSOFT FSE 2022: 1390-1397 - 2021
- [c34]Amir Hossein Bavand, Peter C. Rigby:
Mining Historical Test Failures to Dynamically Batch Tests to Save CI Resources. ICSME 2021: 217-226 - [c33]Louis-Philippe Querel, Peter C. Rigby:
Warning-Introducing Commits vs Bug-Introducing Commits: A tool, statistical models, and a preliminary user study. ICPC 2021: 433-443 - [c32]Maaz Hafeez Ur Rehman, Peter C. Rigby:
Quantifying no-fault-found test failures to prioritize inspection of flaky tests at Ericsson. ESEC/SIGSOFT FSE 2021: 1371-1380 - 2020
- [j6]Andrey Krutauz, Tapajit Dey, Peter C. Rigby, Audris Mockus:
Do code review measures explain the incidence of post-release defects? Empir. Softw. Eng. 25(5): 3323-3356 (2020) - [c31]Ehsan Mirsaeedi, Peter C. Rigby:
Mitigating turnover with code review recommendation: balancing expertise, workload, and knowledge distribution. ICSE 2020: 1183-1195 - [i1]Andrey Krutauz, Tapajit Dey, Peter C. Rigby, Audris Mockus:
Do Code Review Measures Explain the Incidence of Post-Release Defects? CoRR abs/2005.09217 (2020)
2010 – 2019
- 2019
- [j5]Md Tajmilur Rahman, Peter C. Rigby, Emad Shihab:
The modular and feature toggle architectures of Google Chrome. Empir. Softw. Eng. 24(2): 826-853 (2019) - [c30]Musfiqur Rahman, Dharani Palani, Peter C. Rigby:
Natural software revisited. ICSE 2019: 37-48 - [c29]Anunay Amar, Peter C. Rigby:
Mining historical test logs to predict bugs and localize faults in the test logs. ICSE 2019: 140-151 - [c28]Armin Najafi, Weiyi Shang, Peter C. Rigby:
Improving test effectiveness using test executions history: an industrial experience report. ICSE (SEIP) 2019: 213-222 - [c27]Aindrila Sarkar, Peter C. Rigby, Béla Bartalos:
Improving Bug Triaging with High Confidence Predictions at Ericsson. ICSME 2019: 81-91 - [c26]Musfiqur Rahman, Peter C. Rigby, Dharani Palani, Tien N. Nguyen:
Cleaning StackOverflow for machine translation. MSR 2019: 79-83 - [c25]Armin Najafi, Peter C. Rigby, Weiyi Shang:
Bisecting commits and modeling commit risk during testing. ESEC/SIGSOFT FSE 2019: 279-289 - 2018
- [c24]Yue Cai Zhu, Emad Shihab, Peter C. Rigby:
Test Re-Prioritization in Continuous Testing Environments. ICSME 2018: 69-79 - [c23]Anh Tuan Nguyen, Peter C. Rigby, Thanh Nguyen, Dharani Palani, Mark Karanfil, Tien N. Nguyen:
Statistical Translation of English Texts to API Code Templates. ICSME 2018: 194-205 - [c22]Md Tajmilur Rahman, Peter C. Rigby:
The impact of failing, flaky, and high failure tests on the number of crash reports associated with Firefox builds. ESEC/SIGSOFT FSE 2018: 857-862 - [c21]Louis-Philippe Querel, Peter C. Rigby:
WarningsGuru: integrating statistical bug models with static analysis to provide timely and specific bug warnings. ESEC/SIGSOFT FSE 2018: 892-895 - 2017
- [j4]Shams Azad, Peter C. Rigby, Latifa Guerrouj:
Generating API Call Rules from Version History and Stack Overflow Posts. ACM Trans. Softw. Eng. Methodol. 25(4): 29:1-29:22 (2017) - [c20]Anh Tuan Nguyen, Peter C. Rigby, Thanh Van Nguyen, Mark Karanfil, Tien N. Nguyen:
Statistical translation of English texts to API code templates. ICSE (Companion Volume) 2017: 331-333 - 2016
- [c19]Peter C. Rigby, Yue Cai Zhu, Samuel M. Donadelli, Audris Mockus:
Quantifying and mitigating turnover-induced knowledge loss: case studies of chrome and a project at avaya. ICSE 2016: 1006-1016 - [c18]Md Tajmilur Rahman, Louis-Philippe Querel, Peter C. Rigby, Bram Adams:
Feature toggles: practitioner practices and a case study. MSR 2016: 201-211 - [c17]Thanh Van Nguyen, Peter C. Rigby, Anh Tuan Nguyen, Mark Karanfil, Tien N. Nguyen:
T2API: synthesizing API code usage templates from English texts with statistical translation. SIGSOFT FSE 2016: 1013-1017 - 2015
- [j3]Md Tajmilur Rahman, Peter C. Rigby:
Release Stabilization on Linux and Chrome. IEEE Softw. 32(2): 81-88 (2015) - [c16]Latifa Guerrouj, David Bourque, Peter C. Rigby:
Leveraging Informal Documentation to Summarize Classes and Methods in Context. ICSE (2) 2015: 639-642 - [c15]Samuel M. Donadelli, Yue Cai Zhu, Peter C. Rigby:
Organizational Volatility and Post-release Defects: A Replication Case Study Using Data from Google Chrome. MSR 2015: 391-395 - [c14]Latifa Guerrouj, Shams Azad, Peter C. Rigby:
The influence of App churn on App success and StackOverflow discussions. SANER 2015: 321-330 - [p1]Peter C. Rigby, Alberto Bacchelli, Georgios Gousios, Murtuza Mukadam:
A Mixed Methods Approach to Mining Code Review Data. The Art and Science of Analyzing Software Data 2015: 231-255 - 2014
- [j2]Peter C. Rigby, Daniel M. Germán, Laura L. E. Cowen, Margaret-Anne D. Storey:
Peer Review on Open-Source Software Projects: Parameters, Statistical Models, and Theory. ACM Trans. Softw. Eng. Methodol. 23(4): 35:1-35:33 (2014) - 2013
- [c13]Peter C. Rigby, Earl T. Barr, Christian Bird, Premkumar T. Devanbu, Daniel M. Germán:
What effect does distributed version control have on OSS project organization? RELENG@ICSE 2013: 29-32 - [c12]Peter C. Rigby, Martin P. Robillard:
Discovering essential code elements in informal documentation. ICSE 2013: 832-841 - [c11]Murtuza Mukadam, Christian Bird, Peter C. Rigby:
Gerrit software code review data from Android. MSR 2013: 45-48 - [c10]Peter C. Rigby, Christian Bird:
Convergent contemporary software peer review practices. ESEC/SIGSOFT FSE 2013: 202-212 - 2012
- [j1]Peter C. Rigby, Brendan Cleary, Frédéric Painchaud, Margaret-Anne D. Storey, Daniel M. Germán:
Contemporary Peer Review in Action: Lessons from Open Source Development. IEEE Softw. 29(6): 56-61 (2012) - [c9]Earl T. Barr, Christian Bird, Peter C. Rigby, Abram Hindle, Daniel M. Germán, Premkumar T. Devanbu:
Cohesive and Isolated Development with Branches. FASE 2012: 316-331 - 2011
- [b1]Peter C. Rigby:
Understanding open source software peer review: Review processes, parameters and statistical models, and underlying behaviours and mechanisms. University of Victoria, Canada, 2011 - [c8]Peter C. Rigby, Margaret-Anne D. Storey:
Understanding broadcast based peer review on open source software projects. ICSE 2011: 541-550
2000 – 2009
- 2009
- [c7]Christian Bird, Peter C. Rigby, Earl T. Barr, David J. Hamilton, Daniel M. Germán, Premkumar T. Devanbu:
The promises and perils of mining git. MSR 2009: 1-10 - 2008
- [c6]Peter C. Rigby, Daniel M. Germán, Margaret-Anne D. Storey:
Open source software peer review practices: a case study of the apache server. ICSE 2008: 541-550 - 2007
- [c5]Peter C. Rigby, Ahmed E. Hassan:
What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List. MSR 2007: 23 - 2006
- [c4]Margaret-Anne D. Storey, Li-Te Cheng, R. Ian Bull, Peter C. Rigby:
Waypointing and social tagging to support program navigation. CHI Extended Abstracts 2006: 1367-1372 - [c3]Margaret-Anne D. Storey, Li-Te Cheng, R. Ian Bull, Peter C. Rigby:
Shared waypoints and social tagging to support collaboration in software development. CSCW 2006: 195-198 - [c2]Daniel M. Germán, Peter C. Rigby, Margaret-Anne D. Storey:
Using evolutionary annotations from change logs to enhance program comprehension. MSR 2006: 159-162 - 2005
- [c1]Peter C. Rigby, Suzanne Thompson:
Study of novice programmers using Eclipse and Gild. eTX 2005: 105-109
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-11-18 20:43 CET by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint