Identifying code smells

Is a boolean parameter a sign of a deeper problem? Learn to spot common code smells before they lead to technical debt.

#1about 3 minutes

Defining code smells and their importance in development

A code smell is a surface indication of a deeper problem, and identifying them improves communication, testability, and reduces technical debt.

#2about 6 minutes

Identifying bloaters, code that has grown too large

Bloaters are classes or methods that are too large, such as long methods, large classes, primitive obsession, long parameter lists, and data clumps.

#3about 5 minutes

Recognizing OOP abusers that misuse object-oriented principles

OOP abusers are code smells that incorrectly apply object-oriented concepts, including switch statements, temporary fields, refused bequest, and different interfaces.

#4about 4 minutes

Understanding change preventers that hinder future development

Change preventers are code structures that make modifications difficult, such as divergent change, shotgun surgery, and parallel hierarchies.

#5about 4 minutes

Spotting dispensables, the unnecessary parts of your code

Dispensable code smells are unnecessary elements that can be removed, including lazy classes, data classes, duplicate code, dead code, and speculative generality.

#6about 4 minutes

Analyzing couplers and issues with class relationships

Couplers are code smells related to excessive or improper coupling between classes, such as feature envy, inappropriate intimacy, message chains, and the middle man.