Code smell

One way to look at smells is with respect to principles and quality: "Smells are certain structures in the code that indicate violation of fundamental design principles and negatively impact design quality".[6] Code smells are usually not bugs; they are not technically incorrect and do not prevent the program from functioning. Instead, they indicate weaknesses in design that may slow down development or increase the risk of bugs or failures in the future. Bad code smells can be an indicator of factors that contribute to technical debt.[1] Robert C. Martin calls a list of code smells a "value system" for software craftsmanship.[7]

Often the deeper problem hinted at by a code smell can be uncovered when the code is subjected to a short feedback cycle, where it is refactored in small, controlled steps, and the resulting design is examined to see if there are any further code smells that in turn indicate the need for more refactoring. From the point of view of a programmer charged with performing refactoring, code smells are heuristics to indicate when to refactor, and what specific refactoring techniques to use. Thus, a code smell is a driver for refactoring.

A 2015 study[1] utilizing automated analysis for half a million source code commits and the manual examination of 9,164 commits determined to exhibit "code smells" found that:

• There exists empirical evidence for the consequences of "technical debt", but there exists only anecdotal evidence as to how, when, or why this occurs.
• Common wisdom suggests that urgent maintenance activities and pressure to deliver features while prioritizing time-to-market over code quality are often the causes of such smells.

Tools such as Checkstyle, PMD, FindBugs, and SonarQube can automatically identify code smells.

Application-level smells:

• Duplicated code: identical or very similar code exists in more than one location.
• Contrived complexity: forced usage of overcomplicated design patterns where simpler design would suffice.
• Shotgun surgery: a single change needs to be applied to multiple classes at the same time.
• Uncontrolled side effects: very easy to cause runtime exceptions and unit tests can't capture it.
• Variable mutations: very hard to refactor code since the actual value is unpredictable and hard to reason about.
• Boolean blindness: easy to assert on the opposite value and still type checks.

Class-level smells:

• Large class: a class that has grown too large. See God object.
• Feature envy: a class that uses methods of another class excessively.
• Inappropriate intimacy: a class that has dependencies on implementation details of another class. See Object orgy.
• Refused bequest: a class that overrides a method of a base class in such a way that the contract of the base class is not honored by the derived class. See Liskov substitution principle.
• Lazy class / freeloader: a class that does too little.
• Excessive use of literals: these should be coded as named constants, to improve readability and to avoid programming errors. Additionally, literals can and should be externalized into resource files/scripts, or other data stores such as databases where possible, to facilitate localization of software if it is intended to be deployed in different regions.[8]
• Cyclomatic complexity: too many branches or loops; this may indicate a function needs to be broken up into smaller functions, or that it has potential for simplification/Refactoring.
• Downcasting: a type cast which breaks the abstraction model; the abstraction may have to be refactored or eliminated.[9]
• Orphan variable or constant class: a class that typically has a collection of constants which belong elsewhere where those constants should be owned by one of the other member classes.
• Data clump: Occurs when a group of variables are passed around together in various parts of the program. In general, this suggests that it would be more appropriate to formally group the different variables together into a single object, and pass around only the new object instead.[10][11]

Method-level smells:

• Too many parameters: a long list of parameters is hard to read, and makes calling and testing the function complicated. It may indicate that the purpose of the function is ill-conceived and that the code should be refactored so responsibility is assigned in a more clean-cut way.[12]
• Long method: a method, function, or procedure that has grown too large.
• Excessively long identifiers: in particular, the use of naming conventions to provide disambiguation that should be implicit in the software architecture.
• Excessively short identifiers: the name of a variable should reflect its function unless the function is obvious.
• Excessive return of data: a function or method that returns more than what each of its callers needs.
• Excessive comments: a class, function or method has irrelevant or trivial comments. A comment on an attribute setter/getter is a good example.
• God Objects: a class that has lots of responsibilities and is low cohesive.
• Excessively long line of code (or God Line): A line of code which is too long, making the code difficult to read, understand, debug, refactor, or even identify possibilities of software reuse. Example:

new XYZ(s).doSomething(buildParam1(x), buildParam2(x), buildParam3(x), a + Math.sin(x)*Math.tan(x*y + z)).doAnythingElse().build().sendRequest();

• Anti-pattern
• Design smell
• List of tools for static code analysis
• Software rot

• Garousi, Vahid; Küçük, Barış (2018). "Smells in software test code: A survey of knowledge in industry and academia". Journal of Systems and Software. 138: 52–81. doi:10.1016/j.jss.2017.12.013.
• Sharma, Tushar; Spinellis, Diomidis (2018). "A survey on software smells". Journal of Systems and Software. 138: 158–173. doi:10.1016/j.jss.2017.12.034.

• CodeSmell at c2.com
• Taxonomy of code smells
• Overview of many code smells
• CodeSmell
• Boundy, David, Software cancer: the seven early warning signs or here, ACM SIGSOFT Software Engineering Notes, Vol. 18 No. 2 (April 1993), Association for Computing Machinery, New York, NY, USA