Dan Abramov's talk, "The Wet Codebase," discusses the challenges and lessons learned from creating abstractions in coding.

He narrates a scenario where attempts to follow DRY (Don't Repeat Yourself) principles led to overly complex and less maintainable code due to forced abstractions and unintended coupling. Dan emphasizes the importance of considering the trade-offs of abstractions, like accidental coupling and the difficulty in removing entrenched abstractions.

Also has good advices over testing concrete code and resisting premature abstractions, suggesting that sometimes duplication is preferable to the wrong abstraction.

PD: For the past years, this has been my go-to talk to share with people that might be too strict with DRY!