Is there an antipattern to describe this method of coding?

Posted by P.Brian.Mackey on Programmers See other posts from Programmers or by P.Brian.Mackey
Published on 2012-11-14T14:32:21Z Indexed on 2012/11/14 17:29 UTC
Read the original article Hit count: 243

I have a codebase where the programmer tended to wrap things up in areas that don't make sense. For example, given an Error log we have you can log via

ErrorLog.Log(ex, "friendly message");

He added various other means to accomplish the exact same task. E.G.

SomeClass.Log(ex, "friendly message");

Which simply turns around and calls the first method. This adds levels of complexity with no added benefit. Is there an anti-pattern to describe this?

© Programmers or respective owner

Related posts about design-patterns

Related posts about anti-patterns