improve-codebase-architecture

To identify shallow modules for refactoring, analyze where module interfaces mirror their implementations and where seams leak complexity to callers. The architecture review discovers deepening candidates by applying a deletion test to determine where complexity should concentrate.

Categorize dependencies for reliable testing by classifying them across in-process, local-substitutable, ports and adapters, and mock scenarios. This categorization determines how a deepened module should be tested and where to place seams for maximum leverage.

Ports and adapters architecture improves testability by isolating external dependencies behind boundaries that allow reliable local substitution. This pattern classifies dependencies so deepened modules can be tested without leaking implementation details through seams.

Yes, you can generate a self-contained HTML architecture review report with before and after diagrams. The report includes a clear problem and solution statement, visual diagrams, and recommendation strength for each deepening candidate.

Use module deepening instead of adding more tests when shallow modules cause duplicated understanding across callers and weak test coverage through seams. Deepening concentrates complexity at the interface, creating leverage that makes testing more effective.

Explore alternative interface designs for a refactored module through an interactive grilling loop that proposes parallel design options. This design it twice pattern examines constraints, seam placement, and which tests survive to crystallize the testing strategy.