121-java-object-oriented-design

SOLID principles improve Java codebases by ensuring single responsibility, open-closed behavior, and clear dependencies. The skill analyzes class and interface designs to enforce these rules, resolving structural smells and producing actionable refactoring plans.

Refactoring Java for SOLID and DRY requires safe, step-by-step recommendations that preserve compilation and runtime behavior. You review class and interface designs, consolidate duplicated logic, and improve encapsulation to deliver concrete refactoring plans.

Reviewing Java class and interface designs involves analyzing how responsibilities are allocated and checking for clear encapsulation boundaries. You evaluate object creation patterns and method designs to ensure composition is favored over inheritance where appropriate.

Yes, you can apply the YAGNI principle to large Java projects without breaking compilation. The process provides safe, step-by-step recommendations that preserve runtime behavior while removing speculative generality and improving object-oriented design.

You need to address Data Clumps and object creation patterns during Java code reviews when multiple methods share the same group of parameters, indicating poor encapsulation. Resolving this involves refactoring to improve object design and clear responsibilities.