What is the concept of a 'code smell' in software development?

• A. A signal of underlying maintainability problems.
• B. An actual defect that causes incorrect results.
• C. A performance bottleneck identified by profiling.
• D. A deprecated syntax that will never be used.

Answer: (A)

A code smell is a signal that something about the code’s structure may hinder maintainability, readability, or future extensibility. It’s not a defect that causes incorrect results, but a hint that the design or implementation could lead to more effort, bugs, or fragility as the code evolves. Recognizing smells helps you decide where refactoring could improve the codebase, such as extracting large methods, reducing duplication, improving naming, or loosening tight couplings. Examples include long methods, large classes, duplicated logic, or unclear responsibilities. These issues don’t break functionality on their own, but they increase the risk and cost of changes later. A performance issue found by profiling is a separate concern focused on efficiency, and deprecated syntax points to outdated practices rather than the maintainability signals captured by smells.