Thebobrent.com

Most of programming languages dont allow variable, method, class and functions names to contain spaces to create descriptive variables and methods names from multiple words without a compile time error.

To get rid of from this scenario there are 10 Nomenclature Conventions. But in general in our writing notes, project and other writing material (other than computer programs) there are other Nomenclature word cases. In general idea is that we can use any convention in our writing Materials (eg. project) as long as we are consistent about using it everywhere.

Nomenclture Cases are devided into two categories-

1. Nomenclature Cases In computer Programs
2. Nomenclature Cases In writing Material (eg. notes, project, etc. other than computer programs)

Nomenclature Cases In computer Programs:

A) snake_case (pothole case)
The snake case name is derived from the associated imagery of underscores representing snakes that slither on the ground between words. It is commonl used Naming Convention in computer programming. It refers to the style of writing (in computer programms) in which words are seperated by underscore(_) and first letter of each word written in lowercase. Examples: Variables, Subroutine Names, filenames (general nominclature of fileds and folder)

lowercase_words_separated_by_underscores

Example.    user_name, first_name, last_name

Try it yourself, it is fact that you can easly recognise snake_case values compare to camel case.

It first start using in c-languages when this langauge discovered in 1978 afterthat, when python Language generated at 1991 then snake_case was in its basic nomenclature technique and still using now although it is generally refers as "lower_case_with_underscore" in python guide rule.

Languages which dont derive their syntax from C (such as Python & Ruby) use underscores for almost everything except class names.

Before 2004 the term snake_case was not introduced until in "USENET" (worlds first social networking website, technically that was discussion forum) the Gavin Kistner, an user of Ruby community (in USENET forum) is used it.