Meaningful names for variables, methods, and classes go a long way to making uncommented code possible. However, meaning is not conveyed simply by length.
Consider this snippet (a real example, with the class name changed). It’s just a variable declaration in a method that’s only a few lines long, but it conveys the point:
DamnThatIsAVeryLongClassName damnThatIsAVeryLongClassName = new DamnThatIsAVeryLongClassName();
This manages to tell me the same thing three times: it’s a very long class name (with emphasis!). It tells me precisely what the variable is, but gives no hint to what it is going to be used for.
When you keep method lengths short (I advocate under 25 lines, to ensure that the entire method is visible on screen, including any explanatory comment for the method), you shouldn’t have to worry about preserving “type” information in a variable name. The reader shouldn’t have had time to forget it. Convey “what”, “which”, and “why” information instead.
 Believe it or not, it’s actually a longer class name in the original.