Bad method names and what it says about code structure

Question

(Apologizes in advance if this is a re-recording, but I did not find similar messages)

What bad method name templates you saw in the code and what he told you about the code.

For example, I continue to see:

public void preform___X___IfNecessary(...);

I think this is bad because operation X has an inverse of conditions. Note that this is a public method, as class methods may legally need private helpers such as

Answer 1

Sometimes developers seem to have a problem using a short wording. I had the one who called the procedure

InsertImportQueueRecord

I hated is the name. I changed it to

ImportItem

, , . , , , - QueueItemImport ScheduleImport, , . , - , , .

Answer 2

(), doThing() reallyDoThing()

, , . , , - , , . ?

. . , , . , , .

Answer 3

, , , .

ValidateFormData_PersistToDB_SendEmail().

#, .

Answer 4

, , :

private void SOMETHINGBecauseOf__a__(..);
private void SOMETHINGBecauseOf__b__(..);
private void SOMETHINGBecauseOf__c__(..);

, OfOf, . switch/if .