code-architecture-wrong-abstraction

Abstract only after the same code appears in at least three places and the pattern has stabilized. Two occurrences should stay duplicated, since early abstraction often locks in a wrong design before requirements are clear.

Inline the abstraction back into each caller, delete the portions each caller does not need, and accept temporary duplication. Re-extract a proper abstraction later only when genuine shared patterns emerge.

DRY means don't repeat yourself and applies after patterns stabilize. WET means write everything twice and is the default starting point. AHA means avoid hasty abstractions and serves as the guiding principle between them.

Use a facade when hiding complex logic like date pickers or enforcing design system constraints like button variants. Skip it for simple HTML elements like small or mark tags, where the facade just adds props for every edge case.

Each new requirement adds conditional parameters to the shared function, creating spaghetti logic that couples unrelated callers. The abstraction obscures bugs behind indirection and organizational inertia makes teams reluctant to refactor it.