DEV Community

Cover image for Code Smell 38 - Abstract Names
Maxi Contieri ⭐⭐⭐
Maxi Contieri ⭐⭐⭐

Posted on • Updated on • Originally published at


Code Smell 38 - Abstract Names

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 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

what is in a name


Photo by Rodion Kutsaev on Unsplash

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

Phil Karlton

Top comments (0)

16 Libraries You Should Know as a React Developer

Being a modern React developer is not about knowing just React itself. To stay competitive, it is highly recommended to explore the whole ecosystem. This article contains some of the most useful React component libraries to speed up your developer workflow.