一句话：概述代码坏味道作为技术债因素的研究，并指出已有检测与重构建议工具，但未提出新方法或评估结果。
代码坏味道是程序员在软件开发中采用不良设计与实现选择所留下的症状，是技术债的重要来源。研究社区长期关注坏味道在项目中的存续时间，以及它们对源代码非功能属性的负面影响。为此，已有多种工具与技术被提出，用于帮助开发者检测代码坏味道并建议重构机会。本文摘要以这一背景为核心，强调坏味道检测与重构支持的重要性，但并未在摘要中给出具体的新方法、技术细节或实证评估结果。
Code smells, i.e., symptoms of poor design and implementation choices applied by programmers during the development of a software project [2], represent an important factor contributing to technical debt [3]. The research community spent a lot of effort studying the extent to which code smells tend to remain in a software project for long periods of time [9], as well as their negative impact on non-functional properties of source code [4, 7]. As a consequence, several tools and techniques have been proposed to help developers in detecting code smells and to suggest refactoring opportunities (e.g., [5, 6, 8]).
DOI 原文 ·
@inproceedings{paperbot4415,
title = {The scent of a smell},
author = {Fabio Palomba and Annibale Panichella and Andy Zaidman and Rocco Oliveto and Andrea De Lucia},
booktitle = {ICSE},
year = {2018},
doi = {10.1145/3180155.3182530}
}