122-java-type-design

Fix primitive obsession in Java by creating domain-specific value objects and type-safe wrappers to replace raw primitives. This refactoring approach establishes clearer type structures, reducing ambiguous hierarchies and preventing subtle bugs for better long-term maintainability.

The best way to establish clear Java type hierarchies is by applying typography-inspired principles to structure and naming. This involves refactoring nested structures and creating domain-specific fluent interfaces to safely express intent and improve API usability across the project.

Improve Java generics and fluent interfaces by refining them to express clear domain intent and improve API usability. Refactoring generics ensures compile-time safety checks while fluent interfaces make the API design more readable and user-friendly.

Yes, this type design refactoring works with Maven projects. It ensures the project can compile with Maven before applying changes, making it suitable for medium-to-large Java projects that require compile-time safety checks and naming consistency.

You need to refactor Java type design when your codebase suffers from ambiguous hierarchies and primitive obsession, leading to harder maintenance and subtle bugs. Applying type-safe wrappers and clear nested structures resolves these issues and improves overall readability.