Taken from Naming Tips.
-
Do not name methods
ProcessData(). You only get to use this method name once per career, because you should have been fired immediately afterwards. Be specific about what it's doing inside; call itValidateUserCredentialsorEliminateDuplicateRequestsorComputeAverageAge, etc. -
Use naming to help you design the program. Pretend there's a rule saying "you can never write a
voidfunction", then think about all the steps your program makes to transform input into output, then chose names for those steps so you could make a written sentence with them. These are now your function names and the sentence is your program's structure.