Q:

Naming: objectAction or actionObject?

The question, Stored procedure Naming conventions?, and Joel's excellent Making Wrong Code Look Wrong article come closest to addressing my question, but I'm looking for a more general set of criteria to use in deciding how to name modules containing code (classes, objects, methods, functions, widgets, or whatever).
English (my only human language) is structured as action-object (i.e closeFile, openFile, saveFile) and since almost all computer languages are based on English, this is the most common convention.
However, in trying to keep related code close together and still be able to find things, I've found object-action (i.e. fileClose, fileOpen, fileSave) to be very attractive. Quite a number of non-English human languages follow this structure as well.
I doubt that one form is universally superior, but when should each be used in the pursuit of helping to make sure bad code looks bad?

A:

actionObject sounds like a method you'd use in order do to some action with/in the object.
objectAction sounds like an aggregate of information, about the execution/result of the action performed on a object.
So I would generalize and say:

actionObject is appropriate for methods
objectAction, about information aggregation, like simple classes and structs.

One example of that would be:

ReportSecurityFlaw: seems like a method to inform a security flaw
SecurityFlawReport: seems like an object that represents data extracted from already stored Security Flaws

