Rethinking DRY: Why Shared Logic in UI Components Breaks Scaling

Teams often try to maximize UI component reuse across multiple pages for consistency, but this approach creates fragile architectures when logic is embedded in those components. When unrelated pages depend on the same component, changes meant for one page can silently break another—a problem that cascades as the application grows. The solution lies in a strict boundary: reusable components should be purely presentational, while page-specific logic lives in separate containers, ensuring that improvements in one area don't inadvertently damage another.