when creating emails, use descriptive names

Some Telco is running an advert to popularize its email service. The advert features a young man who struggles to get clients since his email doesn’t look professional. Now if his email looks like some emails I have come across then clearly even if I were his potential client I would think twice before doing business with him.

Lets start here, various programming languages have their variable conventions. These conventions are an integral part of  development as the number one reason for using them is to ensure that the code is maintainable. Hold that thought right there socrates.

For a developer looking for some naming conventions. Follow these links below.

1. http://msdn.microsoft.com/en-us/library/ff926074.aspx

3. For PHP(my other lady in coding after c#), there is no definitive conventions but this programmers stack exchange question seems to address the various framework conventions. http://programmers.stackexchange.com/questions/196416/whats-the-dominant-naming-convention-for-variables-in-php-camelcase-or-undersc

Ok, now lets get back to maintenance. Maintenance means that code written today by person X should be easily understood by a person Y. The relation of this with selecting a good email address from the popular email providers is that you will need it at some point in time in the future. If this is the case you need your email to portray a serious owner.

One thing that comes out clear  in naming conventions is that  variables should be self  descriptive and so should emails. Below is my  guide on bad and good email naming conventions assuming the emails are created in gmail.