integra-code-organization

Code organization based on coupling minimizes blast radius by identifying real change patterns and placing related functionality together. Co-locate coupled code rather than grouping by similarity to ensure safer refactors.

Keep single-use helpers with the caller to avoid premature decomposition and needless extraction. Extracting helpers too early breaks cohesion and increases coupling across modules, making future changes harder to track and maintain.

The best way to refactor for cohesion is to organize by what changes together, not by what it is. Apply co-location by coupling to preserve critical relationships and establish boundaries that enable safer, more maintainable refactors.

Grouping similar functions causes maintainability issues because it ignores real coupling patterns. Organizing by what changes, not by similarity, keeps related changes together and prevents blast radius from spreading across unrelated modules.

Premature decomposition harms maintainability by breaking up cohesive modules before real fault lines emerge. Avoid needless extraction and maintain cohesive modules as they evolve to preserve critical relationships and enable safer refactors.

Decide whether to co-locate helpers by analyzing real coupling patterns between the helper and its caller. Keep single-use helpers with the caller to minimize blast radius and avoid introducing unnecessary module boundaries.