Searching for build debt: experiences managing technical debt at Google
The DOI matches its OpenAlex record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Abstract—With a large and rapidly changing codebase, Google software engineers are constantly paying interest on various forms of technical debt. Google engineers also make efforts to pay down that debt, whether through special Fixit days, or via dedicated teams, variously known as janitors, cultivators, or demolition experts. We describe several related efforts to measure and pay down technical debt found in Google’s BUILD files and associated dead code. We address debt found in dependency specifications, unbuildable targets, and unnecessary command line flags. These efforts often expose other forms of technical debt that must first be managed. Keywords-build system; technical debt; monolithic codebase; I.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
An empirical study of build maintenance effort
McIntosh, S., Adams, B., Nguyen, T. H. D., Kamei, Y., & Hassan, A. E. (2011) · Proceedings of the 33rd International Conference on Software Engineering · doi:10.1145/1985793.1985813 · Cited by 143
Cited by
(2015) · neural information processing systems · Cited by 912
A systematic mapping study on technical debt and its management
Li, Z., Avgeriou, P., & Liang, P. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2014.12.027 · Cited by 743
Veale, M., Van Kleek, M., & Binns, R. (2018) · Proceedings of the 2018 CHI Conference on Human Factors in Computing Systems · doi:10.1145/3173574.3174014 · Cited by 490
Giray, G. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2021.111031 · Cited by 187
Kruchten, P., Nord, R. L., Ozkaya, I., & Falessi, D. (2013) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/2507288.2507326 · Cited by 87
Metadata
- Authors
- Morgenthaler, J. D., Gridnev, M., Sauciuc, R., & Bhansali, S.
- Published
- 2012-06-05
- Pages
- 1-6
- DOI
- 10.5555/2666036.2666037
- OpenAlex
- W2029482959
- Cited by
- 56
- References
- 1
- FWCI
- 16.60
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.