Michael Hilton

Michael Hilton

Auto-generated profile, based on publicly available information

Michael Hilton

Carnegie Mellon University, Pittsburgh, USA

Research Focus & Metrics

Academic Career Length

15Years (2012-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
25 August 2016
Verified
Conference Paper
Open access
MHMichael Hilton
Michael Hilton
TTTimothy Tunnell
Timothy Tunnell
KHKai Huang
Kai Huang
DMDarko Marinov
Darko Marinov
DDDanny Dig
Danny Dig
Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI rising as a big success story in automated software engineering, it has received almost no attention from the research community. For example, how widely is CI used in practice, and what are some costs and benefits associated with CI? Without answering such questions, developers, tool builders, and researchers make decisions based on folklore instead of data. In this paper, we use three complementary methods to study the usage of CI in open-source projects. To understand which CI systems developers use, we analyzed 34,544 open-source projects from GitHub. To understand how developers use CI, we analyzed 1,529,291 builds from the most commonly used CI system. To understand why projects use or do not use CI, we surveyed 442 developers. With this data, we answered several key questions related to the usage, costs, and benefits of CI. Among our results, we show evidence that supports the claim that CI helps projects release more often, that CI is widely adopted by the most popular projects, as well as finding that the overall percentage of projects using CI continues to grow, making it important and timely to focus more research on CI.

21 August 2017
Verified
Conference Paper
Open access
MHMichael Hilton
Michael Hilton
NNNicholas Nelson
Nicholas Nelson
TTTimothy Tunnell
Timothy Tunnell
DMDarko Marinov
Darko Marinov
DDDanny Dig
Danny Dig
Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI being a widely used activity in software engineering, we do not know what motivates developers to use CI, and what barriers and unmet needs they face. Without such knowledge, developers make easily avoidable errors, tool builders invest in the wrong direction, and researchers miss opportunities for improving the practice of CI. We present a qualitative study of the barriers and needs developers face when using CI. We conduct semi-structured interviews with developers from different industries and development scales. We triangulate our findings by running two surveys. We find that developers face trade-offs between speed and certainty (Assurance), between better access and information security (Security), and between more configuration options and greater ease of use (Flexi- bility). We present implications of these trade-offs for developers, tool builders, and researchers.

7 March 2024
Verified
Conference Paper
Open access
MAMatin Amoozadeh
Matin Amoozadeh
DDDavid Daniels
David Daniels
DNDaye Nam
Daye Nam
AKAayush Kumar
Aayush Kumar
SCStella Chen
Stella Chen
MAMohammad Amin Alipour
Mohammad Amin Alipour

1 November 2016
Verified
Conference Paper
Open access
PDF file
ANAnh Tuan Nguyen
Anh Tuan Nguyen
MHMichael Hilton
Michael Hilton
MCMihai Codoban
Mihai Codoban
HNHoan Anh Nguyen
Hoan Anh Nguyen
LMLily Mast
Lily Mast
DDDanny Dig
Danny Dig
Learning and remembering how to use APIs is difficult. While code-completion tools can recommend API methods, browsing a long list of API method names and their documentation is tedious. Moreover, users can easily be overwhelmed with too much information. We present a novel API recommendation approach that taps into the predictive power of repetitive code changes to provide relevant API recommendations for developers. Our approach and tool, APIREC, is based on statistical learning from fine-grained code changes and from the context in which those changes were made. Our empirical evaluation shows that APIREC correctly recommends an API call in the first position 59% of the time, and it recommends the correct API call in the top five positions 77% of the time. This is a significant improvement over the state-of-the-art approaches by 30-160% for top-1 accuracy, and 10-30% for top-5 accuracy, respectively. Our result shows that APIREC performs well even with a one-time, minimal training dataset of 50 publicly available projects.

12 November 2024
Verified
Conference Paper
Open access
MAMatin Amoozadeh
Matin Amoozadeh
DNDaye Nam
Daye Nam
DPDaniel Prol
Daniel Prol
AAAli Alfageeh
Ali Alfageeh
JPJames Prather
James Prather
AAAmin Alipour
Amin Alipour

1 November 2016
Verified
Conference Paper
Open access
PDF file
MHMichael Hilton
Michael Hilton
Continuous Integration (CI) has been widely adopted in the software development industry. However, the usage of CI in practice has been ignored for far too long by the research community. We propose to fill this blind spot by doing in- depth research into CI usage in practice. We will answer how questions by using using quantitative methods, such as investigating open source data that is publicly available. We will answer why questions using qualitative methods, such as semi-structured interviews and large scale surveys. In the course of our research, we plan on identifying barriers that developers face when using CI. We will develop techniques to overcome those barriers via automation. This work is advised by Professor Danny Dig.