Anti-patterns, Smells & Refactoring

Software design degrades through unplanned change, local optimization, architectural erosion, and duplicated decisions. This module studies diagnosis and controlled repair.

Module objectives

• Distinguish anti-patterns from smells and ordinary defects.
• Use smells as hypotheses that require contextual evidence.
• Plan behavior-preserving refactoring sequences.
• Transform a design toward a pattern only when the pattern resolves an actual force.

Working method

For each concept, move between code, design structure, change scenarios, and evidence. Avoid pattern-name matching without explaining the underlying design problem.