code-architecture-wrong-abstraction

Premature abstraction occurs when developers generalize code before patterns stabilize, creating hard-to-maintain codebases. It forces incorrect couplings between unrelated features, making future modifications risky and complex instead of simplifying the architecture.

While DRY reduces duplication, embracing WET (Write Everything Twice) or AHA (Avoid Hasty Abstraction) principles initially is safer. Duplicating code early on prevents wrong abstractions, allowing you to wait until the true pattern emerges before refactoring.

Refactor wrong abstractions by inlining the problematic facade code back into its callers. Once inlined, observe the duplicated logic and re-extract new abstractions only when the design stabilizes and clear patterns re-emerge.

Avoid the facade pattern when underlying subsystems are still evolving or when it prematurely hides logic that hasn't stabilized. Using facades too early leads to wrong abstractions that tightly couple features and hinder future codebase modifications.