"Don't Repeat Yourself (DRY)" is one of the most widely accepted principles in software development—but taken too far, it can quietly make systems harder to understand, change, and debug. This talk explores the hidden costs of abstraction: when shared logic becomes tight coupling, when reuse reduces clarity, and when flexibility introduces unnecessary complexity.

We'll look at real-world scenarios where:

1. Abstractions leak and increase cognitive load
2. Generic solutions make simple changes harder
3. DRY conflicts with readability and domain clarity

You'll leave with a more balanced approach to abstraction—knowing when to extract, when to duplicate, and how to design code that is easier to work with, not just "cleaner" on paper.