Searching for build debt: Experiences managing technical debt at Google

Morgenthaler, J. David; Gridnev,; Sauciuc,; Bhansali,

doi:10.1109/mtd.2012.6225994

Cited by 54 publications

(43 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our prior work on enforcing direct dependencies [27] prepares the foundation for applying REFINER. The direct dependencies of a target define the symbols that the target references directly.…”

Section: Dependency Refinementmentioning

confidence: 99%

“…In our prior work [27], we discussed several code smells specific to build specifications, including under-declared dependencies, zombie targets, and visibility debt. We introduced a tool called Clipper that takes a binary target as input and ranks the libraries in the transitive closure of the dependencies of the binary by their utilization rates, i.e., the percentage of the symbols of the library that are used by the binary.…”

Section: Rq 4 : How Receptive Are Programmers To the Changes That mentioning

confidence: 99%

“…Research suggests that build maintenance accounts for 27% and 44% of code and test development, respectively [24]. Our prior work [27] showed that build specifications are prone to code smells such as unneeded and missing direct dependencies. This paper focuses on a specific code smell, which we call underutilized targets.…”

Section: Introductionmentioning

confidence: 99%

“…Dedicating more compute resources to the CI system is not sufficient to keep up with this growth rate. Thus, advanced technologies are needed to ensure that build and test results are delivered to programmers correctly and in a timely manner [5], [8], [15], [19], [25], [27], [37], [52].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Automated Decomposition of Build Targets

Vakilian

Sauciuc

Morgenthaler

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

Self Cite

View full text Add to dashboard Cite

Abstract-A (build) target specifies the information that is needed to automatically build a software artifact. This paper focuses on underutilized targets-an important dependency problem that we identified at Google. An underutilized target is one with files not needed by some of its dependents. Underutilized targets result in less modular code, overly large artifacts, slow builds, and unnecessary build and test triggers. To mitigate these problems, programmers decompose underutilized targets into smaller targets. However, manually decomposing a target is tedious and error-prone. Although we prove that finding the best target decomposition is NP-hard, we introduce a greedy algorithm that proposes a decomposition through iterative unification of the strongly connected components of the target. Our tool found that 19,994 of 40,000 Java library targets at Google can be decomposed to at least two targets. The results show that our tool is (1) efficient because it analyzes a target in two minutes on average and (2) effective because for each of 1,010 targets, it would save at least 50% of the total execution time of the tests triggered by the target.

show abstract

Section: Dependency Refinementmentioning

confidence: 99%

Section: Rq 4 : How Receptive Are Programmers To the Changes That mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Automated Decomposition of Build Targets

Vakilian

Sauciuc

Morgenthaler

et al. 2015

2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Due to the complexity and fast evolution of software, the coupling between modules can deviate from the original design, which hurts software maintainability. A recent study shows that intermodule dependencies can be a significant source of technical debt in long-term software development [7].…”

Section: Introductionmentioning

confidence: 99%

Generating precise dependencies for large software

Wang

Yang

Tan

et al. 2013

2013 4th International Workshop on Managing Technical Debt (MTD)

View full text Add to dashboard Cite

Abstract-Intra-and inter-module dependencies can be a significant source of technical debt in the long-term software development, especially for large software with millions of lines of code. This paper designs and implements a precise and scalable tool that extracts code dependencies and their utilization for large C/C++ software projects. The tool extracts both symbollevel and module-level dependencies of a software system and identifies potential underutilized and inconsistent dependencies. Such information points to potential refactoring opportunities and help developers perform large-scale refactoring tasks.

show abstract

Technical debt (TD) through the lens of Twitter: A survey

Alfayez

Winn

Ding

et al. 2023

J Software Evolu Process

View full text Add to dashboard Cite

Technical debt (TD) is a metaphor used to refer to the added software system costs acquired from taking shortcuts. Unfortunately, large amounts of TD can lead to serious consequences, and, thus, the management of TD is essential. Due to TD being a relatively new subject of study, many aspects of TD remain ambiguous. Fortunately, Twitter has been proven to hold a wealth of information on many subjects. As such, this survey study aims to gain a better understanding on how interest in TD has evolved over time and how TD is addressed on Twitter. A total of 128,897 TD‐related tweets were scrapped from Twitter and analyzed using a number of proxy measures and Latent Dirichlet Allocation (LDA). The results revealed that interest in TD on Twitter has been generally increasing since the platform's early stages. Furthermore, TD‐related tweets were found to revolve around 11 distinct categories. The TD in games category was discovered to be the most popular category, followed by TD communication and TD repayment. The results highlight that TD is a diverse and overarching topic that contains many potential avenues for further exploration. Software engineering researchers, practitioners, and educators can utilize this study to help steer their TD‐related future efforts.

show abstract

Searching for build debt: Experiences managing technical debt at Google

Cited by 54 publications

References 4 publications

Automated Decomposition of Build Targets

Automated Decomposition of Build Targets

Generating precise dependencies for large software

Technical debt (TD) through the lens of Twitter: A survey

Contact Info

Product

Resources

About