按年被提到
20222022 · 1 次2026
软件工程与 AI 编程›软件工程实证研究·arXiv:2203.04374 · cs.SE

Code Red: The Business Impact of Code Quality -- A Quantitative Study of 39 Proprietary Production Codebases

Adam Tornhill, Markus Borg · 2022
开始阅读 ↗PDFalphaXiv 讨论
被提及 · 2 人首次 2022-03-17 · 最近 2024-12-16
2不同的人
2活跃月份
2讨论串
4被引(OpenAlex)
arXiv 摘要(候选层不写导读)

Code quality remains an abstract concept that fails to get traction at the business level. Consequently, software companies keep trading code quality for time-to-market and new features. The resulting technical debt is estimated to waste up to 42% of developers' time. At the same time, there is a global shortage of software developers, meaning that developer productivity is key to software businesses. Our overall mission is to make code quality a business concern, not just a technical aspect. Our first goal is to understand how code quality impacts 1) the number of reported defects, 2) the time to resolve issues, and 3) the predictability of resolving issues on time. We analyze 39 proprietary production codebases from a variety of domains using the CodeScene tool based on a combination of source code analysis, version-control mining, and issue information from Jira. By analyzing activity in 30,737 files, we find that low quality code contains 15 times more defects than high quality code. Furthermore, resolving issues in low quality code takes on average 124% more time in development. Finally, we report that issue resolutions in low quality code involve higher uncertainty manifested as 9 times longer maximum cycle times. This study provides evidence that code quality cannot be dismissed as a technical concern. With 15 times fewer defects, twice the development speed, and substantially more predictable issue resolution times, the business advantage of high quality code should be unmistakably clear.

候选层:至少 2 个不同的人、在 2 个不同月份提到过,还没到主书架的 3 人 3 个月。没有做立场标注,所以只写“被提及”。

HN 书评

推荐在前,同类按时间 · 每篇最多保留 20 条,统计用全部提及
评论nephrenka · 2022-03

“This is indeed something that the academic research paper (see https://arxiv.org/abs/2203.04374) identifies as Future Work. There could be a code familiarity component that explains the large risks and variations. From the paper: "Could it be that changes done by the main author are faster and more predictable than corresponding changes made by a minor c…”

Code quality: measuring the business impact of unhealthy code原评论 ↗
评论gspencley · 2024-12

“> Code quality does not affect final product quality IMHO. What we need, admittedly, is more research and study around this. I know of one study which supports my position, but I'm happy to admit that the data is sparse. https://arxiv.org/abs/2203.04374 From the abstract: "By analyzing activity in 30,737 files, we find that low quality code contains 1…”

Ask HN: SWEs how do you future-proof your career in light of LLMs?原评论 ↗