I understand that naming conventions are important for a number of reasons, most having to do with making your code more readable and easier to integrate into larger projects, e
I usually ask myself:
What is this method doing?
The answer dictates what the method should be called. It is completely independent of the programmer, of course.
Note: If you can't succinctly describe what the method is doing, it's probably doing too much and should be split up.
Choosing your method's verb:
Now, not all methods begin with a verb; but they really don't need to. If you read:
... myString.length();
or
... myArray.size();
you know exactly what is going on - no verb required. This is true for many class methods higher up in the Java hierarchy; Collections, Math, etc. As long as the name accurately communicates what the method does, it's fine.