I've worked on a codebase where objects inherited from a class named "Abstract" which contained, apparently, methods used in more than one class, regardless of

I've worked on a codebase where objects inherited from a class named "Abstract" which contained, apparently, methods used in more than one class, regardless of purpose. Other fun anti-pattern: make a Facade class hiding services. Then: - add logic directly in your facade - make the services using the facade depend themselves on the facade (circular dependencies FTW) This an excellent way of ensuring your code will NOT be reused.