Pattern Design Anti-Patterns and Refactoring

Question 1

The 'God Object' anti-pattern refers to a class that:

Accepted Answer

Knows too much or does too much, violating the Single Responsibility Principle

Answer

A God Object accumulates so many responsibilities and so much knowledge about other classes that it becomes a maintenance nightmare and a central point of failure.

Question 2

The 'Lava Flow' anti-pattern describes:

Accepted Answer

Dead code that is too risky to remove because its purpose is unknown

Answer

Lava Flow refers to code that has solidified (like cooled lava) and is no longer understood — developers fear removing it in case it breaks something.

Question 3

The 'Magic Numbers' anti-pattern is resolved by refactoring them into:

Accepted Answer

Named constants or enumerations

Answer

Replacing magic numbers (unexplained literals like 86400) with named constants (SECONDS_PER_DAY) makes code self-documenting and easier to maintain.

Question 4

The 'Spaghetti Code' anti-pattern results from:

Accepted Answer

Lack of structure, excessive control flow jumps, and unclear responsibilities

Answer

Spaghetti code has tangled, convoluted control flow with no clear structure, making it nearly impossible to follow, test, or maintain.

Question 5

Extract Method refactoring is applied when:

Accepted Answer

A code fragment can be grouped and named as its own method

Answer

Extract Method improves readability by pulling a code fragment into a well-named method, making the original method shorter and easier to understand.

Pattern Design Practice Test

Pattern Design Practice Test

Pattern Design Anti-Patterns and Refactoring