What is a code smell commonly seen at Level 1?

What is a code smell commonly seen at Level 1?

• A. A well-documented public API.
• B. Long methods or excessive branching.
• C. Short, focused functions.
• D. Comprehensive unit tests.

Answer: (B)

Long methods and excessive branching signal a code smell because they hide the true complexity of what the code is doing and make it hard to read, test, and maintain. When a single method grows long or is stuffed with many nested if/else blocks, it’s usually taking on too many responsibilities. That makes it tricky to understand the intent, harder to verify all paths, and more prone to bugs when you need to modify anything. The natural fix is to break the method into smaller, focused pieces that each do one thing well. Extracting logic into helper methods, reducing conditional complexity, and using clearer flow—like early returns or smaller methods for each decision—helps keep code readable and testable. In contrast, a well-documented public API, short focused functions, or comprehensive unit tests describe good practices and quality, not smells.

Long methods and excessive branching signal a code smell because they hide the true complexity of what the code is doing and make it hard to read, test, and maintain. When a single method grows long or is stuffed with many nested if/else blocks, it’s usually taking on too many responsibilities. That makes it tricky to understand the intent, harder to verify all paths, and more prone to bugs when you need to modify anything. The natural fix is to break the method into smaller, focused pieces that each do one thing well. Extracting logic into helper methods, reducing conditional complexity, and using clearer flow—like early returns or smaller methods for each decision—helps keep code readable and testable. In contrast, a well-documented public API, short focused functions, or comprehensive unit tests describe good practices and quality, not smells.