Choosing routine names is an important skill. The name should give the reader all the information about the routine. In the old days, the length of names were restricted to sometimes as few as five letters. Various conventions have now cropped up. However, most conventions urge the use of strong verbs acting on objects as input and, if a function, output. It is more important to be consistent in the use of whatever convention you adopt than it is to adopt a particular convention.
For a bad example, consider the Unix function for C called atoi. If you already know what it does, then fine; if not, how would you know to use it. A far better name might be convertAsciiToInteger. Now, we can argue about having to write this long name each time; C style programmers would prefer the cognitive overhead of remembering atoi to the long name. In a large project, though, the longer name is probably preferred.