abstraction-check

Evaluate duplicated code for extraction by applying the Rule of Three and analyzing speculative generality. Avoid premature abstraction by waiting until code is duplicated at least three times before refactoring it into a shared utility.

Premature abstraction is creating helper functions, base classes, or shared modules before the actual need is established. It introduces unnecessary complexity and cognitive load, making the codebase harder to maintain and understand.

Decide between extracting or inlining code by analyzing duplication, potential leaky abstractions, and cognitive load. Use software design principles like DRY and the Rule of Three to guide your refactoring decisions and prevent over-engineering.

Avoid creating a base class when it introduces speculative generality or a leaky abstraction. If the shared module increases cognitive load without providing immediate, concrete reuse value across multiple instances, inlining the code is preferred.

The Rule of Three applies to code refactoring by suggesting you extract code into an abstraction only after it has been duplicated three times. It helps balance the DRY principle against the risk of premature abstraction and unnecessary complexity.