Code Smell 38 - Abstract Names

Code Smell 38 - Abstract Names

Maxi Contieri
·Nov 30, 2020·

1 min read

Subscribe to my newsletter and never miss my upcoming articles

Play this article

Avoid too abstract names. Names should have real world meaning


  • Implemental Naming

  • Meaningless names

  • Broken MAPPER and Bijection to real world entities.


  1. Choose meaningful names.

  2. Find metaphors.

  3. Avoid words like abstract, base, generic, helper, data, info etc.

  4. Use rules for naming.

Sample Code



We can set up policies and rules warning for certain words like base, abstract, helper, manager, object etc.


  • Naming


Finding names is the last thing we should do on our designs. Unless we have a clear business understanding, good names emerge at the end after defined behavior and protocol boundaries.


More info


Photo by Rodion Kutsaev on Unsplash

There are only two hard things in Computer Science: cache invalidation and naming things.

Phil Karlton

This article is part of the CodeSmell Series.

Share this