Naming Classes – How to avoid calling everything a “Manager”? [closed]

by

I asked a similar question, but where possible I try to copy the names already in the .NET framework, and I look for ideas in the Java and Android frameworks.

It seems Helper, Manager, and Util are the unavoidable nouns you attach for coordinating classes that contain no state and are generally procedural and static. An alternative is Coordinator.

You could get particularly purple prosey with the names and go for things like Minder, Overseer, Supervisor, Administrator, and Master, but as I said I prefer keeping it like the framework names you’re used to.

Some other common suffixes (if that is the correct term) you also find in the .NET framework are:

  • Builder
    A type that use some parameters to construct an instance of a special type. Builder is usually a throwaway. It may not even need to allocate a variable.
    If the type needs to repeatedly create objects, please use Factory.
    if the type responsible for create multiple different type objects, please use Factories.
  • Writer
    Write some variable into something.
  • Reader
    Read something as variable.
  • Handler
    Designed to deal with a situation or something.
  • Container
    Can put something into it.

More Related Contents:

  1. In a PHP project, what patterns exist to store, access and organize helper objects? [closed]
  2. How will I know when to create an interface?
  3. Dependency Injection & Singleton Design pattern
  4. Is global constants an anti-pattern?
  5. How do you know when to use design patterns? [closed]
  6. Examples of GoF Design Patterns in Java’s core libraries
  7. Difference between static class and singleton pattern?
  8. Is ServiceLocator an anti-pattern?
  9. Design Patterns: Abstract Factory vs Factory Method
  10. What is the facade design pattern?
  11. Design Pattern for Undo Engine
  12. How to implement the activity stream in a social network
  13. What is the basic difference between the Factory and Abstract Factory Design Patterns? [closed]
  14. Variable naming conventions in Java
  15. Can you create instance properties dynamically in PHP?
  16. Best design pattern for “undo” feature [duplicate]
  17. How to explain dependency injection to a 5-year-old? [closed]
  18. How does the Strategy Pattern work? [closed]
  19. Is it bad practice to make a setter return “this”?
  20. Interface Segregation Principle- Program to an interface
  21. Business logic in MVC [closed]
  22. What is the Page Object Pattern in Selenium WebDriver? [closed]
  23. A way of casting a base type to a derived type
  24. What is composition as it relates to object oriented design?
  25. What is an anti-pattern?
  26. Can you explain the Context design pattern?
  27. Switch statements are bad? [closed]
  28. anti-if campaign
  29. What are `optimistic updates` in front-end development
  30. Why doesn’t generic ICollection implement IReadOnlyCollection in .NET 4.5?

Leave a Comment