I’m also opposed to redundant information that isn’t required due to the surrounding context. For example, a method signature like this:

public void removeItem(Item itemToRemove);

has redundancy. I know I’m removing an Item (I’m passing an Item in), so why not just call the method remove(Item itemToRemove)? And it’s obvious that the parameter is the item being removed, so why not just have make it remove(Item item) or remove(Item theItem)?

A lot of people still live in terror of conventions like:
lpstrWndTitle and lphwndMain and so on…

Perhaps longer classnames are more useful in cases like:

SomeInterface something = new WhizBangThingThatDoesItThisWayImpl();

So the really long name is only really visible when it counts (when you are injecting the specific implementation of choice).

Or just use better names.