Avoid Wrong Abstractions

Prefer duplication over wrong abstraction. Wait for real patterns.

Goal

Keep code easy to change. Use abstractions only when they reduce real complexity.

Rules

• Do not abstract before 3 real uses unless there is strong domain reason.
• Similar shape is not enough; behavior must match.
• Prefer clear duplication over parameter-heavy helpers.
• Avoid abstractions that need new flags for every caller.
• Inline bad abstractions before designing new ones.
• Test concrete behavior, not abstraction cleverness.