Bad method names and what it says about code structure.

Posted by maxfridbe on Stack Overflow See other posts from Stack Overflow or by maxfridbe
Published on 2010-05-24T20:38:41Z Indexed on 2010/05/24 20:41 UTC
Read the original article Hit count: 280

(Apologies in advance if this is a re-post but I didn't find similar posts)

What bad method name patterns have you seen in code and what did it tell you about the code.

For instance, I keep seeing:

public void preform___X___IfNecessary(...);

I believe that this is bad because the operation X has an inversion of conditions. Note that this is a public method because classes methods might legitimately require private helpers like this

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about object-oriented-design