code smell

programming

A surface sign in code that hints at a deeper design problem, without being a bug itself.

Long methods, duplicated logic, and giant classes are classic smells: the code runs, but something is off and likely to cause pain later. Kent Beck coined the term and Martin Fowler popularized it as a prompt to consider refactoring, not an automatic verdict.

Also known as: smell, bad smell in code

← All glossary entries