Missing Clean Code Acceptance and Support in Practice - An Empirical Study

Rachow, Paula; Schröder, Sandra; Riebisch, Matthias

doi:10.1109/aswec.2018.00026

Cited by 6 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since then its publication in 2009 there have been several research studies assessing its benefits (e.g., [11,17]), how to support it (e.g., [18]), analyzing challenges and hindrances to its adoption in practice (e.g., [27]), or different aspects of refactoring and how it impacts on Clean Code or code quality (e.g., [2,3,4,5,36,6,9,10,15,26,28,30,33]).…”

Section: Related Workmentioning

confidence: 99%

“…However, we know very little about the practitioners' perceptions of the Clean Code and whether and how they use it in practice [27]. It is still unclear how professional developers perceive Clean Code, whether they agree with its principles and practices, and whether they believe that Clean Code can help them be-ing more efficient and effective while reading, understanding, reusing and maintaining code.…”

Section: Related Workmentioning

confidence: 99%

“…Seed S01 [18], S02 [27], S03 [8], S04 [20], S05 [11], S06 [21], S07 [5], S08 [10], S09 [23] Iteration 1 23 references and 6 citations P1 [32], P2 [31], P3 [35], P4 [1], P5 [7], P6 [19], P7 [6], P8 [3], P9 [2], P10 [15], P11 [9] Iteration 2 10 references and 6 citations P12 [28], P13 [30], P14 [26], P15 [33] Iteration 3 0 references and 3 citations P16 [4], P17 [29], P18 [14] Iteration 4 0 references and 0 citations…”

Section: Papers Includedmentioning

confidence: 99%

“…Although there are studies reporting the Clean Code benefits (e.g., [11,17]), how to support it (e.g., [18]), analyzing challenges and hindrances of its adoption in practice (e.g., [27]), or different aspects of refactoring and how it impacts on Clean Code or code quality (e.g., [2,3,4,5,36,6,9,10,15,26,28,30,33]), it is still unclear how professional developers perceive Clean Code. In this paper, we report a Questionnaire Survey study that explores the practitioners' perceptions regarding Clean Code.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

"To Clean-Code or Not To Clean-Code" A Survey among Practitioners

Ljung¹,

González-Huerta²

2022

Preprint

View full text Add to dashboard Cite

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.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Papers Includedmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

"To Clean-Code or Not To Clean-Code" A Survey among Practitioners

Ljung¹,

González-Huerta²

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…-The invitation of non-experts to participate in the SDP, allowing the problem space to be jointly explored crossdisciplinarily [6][29] [32]. Also, when employing a usercentric approach contextual awareness is crucial, including culture, gender, class and accessibility aspects [43][44] -The enforcement of these changes should also involve attitude and behavior changes towards intangible social factors influencing the SDP [13][45] [46] and the inclusion of social, behavioral and management sciences in the software engineering curriculum [11].…”

mentioning

confidence: 99%

Blinded by Simplicity

Gustavsson

Penzenstadler

2020

Proceedings of the 7th International Conference on ICT for Sustainability

View full text Add to dashboard Cite

The software development process is a complex human, intellectual and labor-intensive activity and human related factors have shown to be the most significant contributors to software system failures. Lacking the ability to identify or quantify these factors, software practitioners will not learn from the failures caused by them. Although, social factors give rise to high failure rates in software development projects they tend to be ignored. Business continues as usual. The inability for software engineers to attain a holistic and inclusive approach will leave the social dimension out and undermine the realization of a fully sustainable software development process. This paper builds on the master's thesis with the same title completed in December 2019 at Stockholm University. The thesis demonstrates how research literature on software development processes addresses (or not) the social dimension of sustainability from a holistic point of view. The results indicate that the practice of dealing holistically with complexity including the social dimension is still underdeveloped. Further research is suggested regarding the development of adequate supporting tools, social skills, and managerial attitudes and behaviors.

show abstract

“To Clean Code or Not to Clean Code” A Survey Among Practitioners

Ljung

González-Huerta²

2022

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Missing Clean Code Acceptance and Support in Practice - An Empirical Study

Cited by 6 publications

References 11 publications

"To Clean-Code or Not To Clean-Code" A Survey among Practitioners

"To Clean-Code or Not To Clean-Code" A Survey among Practitioners

Blinded by Simplicity

“To Clean Code or Not to Clean Code” A Survey Among Practitioners

Contact Info

Product

Resources

About