Understanding Code Smells in Software

What is a "code smell" in software development?

• A syntax error in the code

• A security vulnerability in the system

• An indicator of a deeper problem in the codebase

• A runtime exception

Which of the following is a common cause of "Duplicate Code" smell?

• Using polymorphism to extend functionality

• Copying and pasting the same logic in multiple places

• Using inheritance to share behavior

• Applying encapsulation principles

What is the recommended approach to eliminate "Long Methods"?

• Increase the number of parameters to make the method more flexible

• Split the method into smaller, single-responsibility methods

• Use global variables to manage method complexity

• Store all logic in a single utility function

Which of the following is a characteristic of "Shotgun Surgery"?

• One class has too many responsibilities

• Changing one functionality requires modifying multiple classes

• A class inherits unnecessary methods from a parent class

• A class contains too many instance variables

How can "Feature Envy" be resolved?

• Move the method to the class that contains the data it heavily interacts with

• Create additional helper methods to access the required data

• Use global variables to reduce dependency on specific classes

• Convert the method into a static utility function

What is the primary issue with "Long Parameter Lists"?

• They make it difficult to call the method correctly

• They improve code readability

• They enhance encapsulation

• They reduce code duplication

Which principle helps avoid "Divergent Change"?

• Separation of Concerns

• Law of Demeter

• DRY (Don't Repeat Yourself)

• Singleton Pattern

"Parallel Inheritance Hierarchies" occur when...

• One class inherits multiple classes simultaneously

• Every class in one hierarchy requires a corresponding class in another hierarchy

• A class contains too many fields and methods

• The inheritance chain is too deep

How can the "Data Class" smell be improved?

• Add methods that operate on its data

• Remove encapsulation to allow better access to data

• Use it only for storing primitive types

• Convert it into a Singleton

What does "Speculative Generality" refer to in code smells?

• Making code more flexible than necessary in anticipation of future needs

• Using too many global variables

• Writing overly specific code with no flexibility

• Using switch-case statements excessively