Kevlin Henney challenges the pervasive practice of suffixing exception classes with 'Exception' in Java and .NET ecosystems. This redundant naming violates the DRY principle and obscures meaningful communication, weakening code clarity. Examining examples from standard libraries reveals how precise naming can expose ambiguities and improve exception handling.