Naming conventions

[no steez]

I know what naming conventions are mentally in my head but I have trouble describing them and identifying features

Can anyone point me in the right direction for answering naming convention questions, any tips?
Cheers

[paulthegreen]

They should describe the purpose and the type of the type of the object.

For example - btnConfirm,

It describes the type of object, it is a button. It also gives an indication of what it may do.

It's a way of maintaining consistency, and like with internal documentation, it helps if the solution is revisited in the future or looked at by other programmers as a way to analyse what specific functions and objects do.

It is a bit tricky to describe them!

[Ya Habibi]

Hungarian Notation: At the start of the naming process, a few letters (usually 3 and in lowercase) are used to describe the element type. Eg: btnButton or lblLabel

Camel Case: After using hungarian notation, the following words used to further describe the element are always capitalised at the start of new words. Eg: btnButtonDoesNothing.