* Inside every large program are a bunch of little programs trying to escape … Thus, instead of writing one large program, sometimes it’s better to have smaller ones based on a specific function.

* Use good naming conventions and comment every major routine. Write this so that anyone can maintain it in the future.

* Before start coding, visualize how it will execute.

* Even a one-line change that is untested can get folks in trouble. So, test test test!

Courtasy:allPM.com

Here is the link to my MVP profile at Microsoft Website. https://mvp.support.microsoft.com/profile/Praveen