Code smells
Peter Kokol, Milan Zorman, Grega Zlahtic, Bojan Zlahtic

TL;DR
This paper reviews the concept of code smells, their detection, and implications, highlighting that well-managed code smells can positively influence software quality and development practices.
Contribution
It provides a comprehensive overview of code smells research, including detection methods, refactoring strategies, and the potential positive aspects of code smells.
Findings
Research interest in code smells is increasing.
Most research is from developed countries.
Code smells can have positive connotations and serve as development patterns.
Abstract
Code smells as symptoms of poor design and implementation choices. Many times they are the result of so called technical debt. Our study showed that the interest in code smells research is increasing. However, most of the publications are appearing in conference proceedings. Most of the research is done in G7 and other highly developed countries. Four main research themes were identified namely code smell detection, bad smell based refactoring, software development and anti patterns. The results show that code smells can also have a positive connotation, we can develop software which smells good and attracts various customers and good smelling code could also serve as a pattern for future software development.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsPublic Relations and Crisis Communication · Disaster Response and Management
