#naming guidelines

What options does Microsoft 365 offer for defining Teams naming policies? If Teams is to be introduced in the company, a governance concept must be created beforehand. This concept clarifies, for example, how groups and teams are created, which security rules apply, whether guest access is permitted, how naming is regulated, and much more. In […]

Read the full Article https://activedirectoryfaq.com/2021/02/define-teams-naming-policies/

There are tons of online resources for naming guidelines. I am positive you will be able to find something that fits your organization's needs.

Here are the naming guidelines I most often use. Remember, these are just guidelines, not commandments etched in stone. Use them when appropriate but also be willing to make exceptions if necessary.

1

I camelCase all variable names both public and private. This guideline may not be etched in stone, but definitely some really, really hard dirt.

2

I add suffixes to source file names to better identify what they do.  For example, things that deal with one object are “handlers”, those that deal with multiple objects are called “manager”.  Think of it as:  I handle myself and manage a group.

3

Use meaningful names for variables, spell it out!.  Not ‘eTime’ and ‘sIntr’ but rather ‘elapsedTime’ and ‘sndInterval’.  

Which is clearer:

        if ( elapsedTime > sndInterval )

                OR

        if ( eTime > sIntr )