>>I get the impression that you're focusing on the problem of replacing old names/classes in old apps and libraries by new ones. My personal opinion is that such an action is too ambitious.
>
>As for the naming convention, yes, it's an insufficient reason. I replaced controls because there were more pressing reasons for replacement.
>
>> Rather, I advocate that NEW classes are properly named. And team members should not (no longer) have the freedom to invent any name they personally prefer.
>>
>>For some of us, and for closed projects, it is probably too late. For new projects, and for those who are still willing to improve the methods and techniques, there is a chance for improvement here.
>
>Ah, but how often do you get to write a completely new project, on a new framework? For me, there were only four of these over the last seven years. The rest of the time, it's the existing stuff, or new apps done within the existing framework - which has its naming conventions already.

If an existing app or 'framework' indeed *has* a naming convention, and if it's consistent, then I agree. But all too often an app appears to show no real sign of a naming convention. Rather, it was the developer who needed a name and any name would be fine, because no one did complain, because there was simply no review mechanism in place.

Anyway, I hope some others will see usage in *their* working environment.