Code Smell 26 - Exceptions Polluting

Subscribe to my newsletter and never miss my upcoming articles

It is very nice to have lots of different exceptions. Your code is declarative and robust. Or not?


  • Over Design

  • Namespace Pollution


  1. Avoid creating anemic exceptions as globals.

  2. Create exceptions only if they behave differently.

  3. Model exceptions with objects. Classes are handy for lazy programmers.

Sample Code



New exceptions should override behavior methods.

No. code, description, resumable, etc are not behavioral.


  • Abuser

  • Naming


You would not create different classes for every Person instance, so they return different names. Why would you do it with exceptions.

How often do you catch a specific exception?.

Go out and check your code.

Is it necessary to be a class?

You are already coupled to the class. Couple to the description instead.

Exception instances should NOT be Singletons.



Photo by Nick van den Berg on Unsplash

You will fall to ruin because you believe that exceptions to the rule make new rules.

Pierce Brown

This article is part of the CodeSmell Series.

No Comments Yet