论文标题
“要清洁代码或不清理代码”从业者中的调查
"To Clean-Code or Not To Clean-Code" A Survey among Practitioners
论文作者
论文摘要
上下文：编写其他合作者可以理解的干净代码对于提高协作和生产力至关重要。但是，关于开发人员是否同意清洁代码原则以及他们如何在实践中应用它们的知识很少。\\目标：在这项工作中，我们调查了开发人员如何感知清洁代码原则，他们是否认为有助于阅读，理解，重复使用和修改干净的代码以及如何处理清洁代码。方法：我们进行了系统的文献综述，其中我们考虑了771个研究论文，以收集39名从业人员的清洁代码原则和一项调查，其中一些具有超过20年的发展经验。\\结果：到目前为止，结果显示了与清洁代码原则及其潜在利益的共同协议。他们还表明，开发人员倾向于编写凌乱的代码以稍后进行重构。
Context: Writing Clean Code understandable by other collaborators has become crucial to enhancing collaboration and productivity. However, very little is known regarding whether developers agree with Clean Code Principles and how they apply them in practice.\\ Objectives: In this work, we investigated how developers perceive Clean Code principles, whether they believe that helps reading, understanding, reusing, and modifying Clean Code, and how they deal with Clean Code in practice. Methods: We conducted a Systematic Literature Review in which we considered 771 research papers to collect Clean Code principles and a survey among 39 practitioners, some of them with more than 20 years of development experience.\\ Results: So far, the results show a shared agreement with Clean Code principles and its potential benefits. They also show that developers tend to write messy code to be refactored later.
