Best Practice – Follow the defined standards, don’t create it

Most of the standard software organizations maintain their coding standards. These standards would have been setup by well experienced software developers and after spending years with software development. This is equivalent to following footsteps of great people left behind them.


If your organization does not have any standard then I would suggest to search for internet for coding standard for different programming languages and you will find many. A coding standard would fix the rules about various important attributes of the code, few are listed below:

  • File Naming convention

  • Function & Module Naming convention

  • Variable Naming convention

  • History, Indentation, Comments

  • Readability guidelines

  • List of do’s and don.ts

But once defined, start following the defined standard instead of creating or changing them everyday. I would definitely say:

Source code is your BABY!

So keep it clean, consistent, and beautiful. When I say beautiful, it really means beautiful. If your code looks beautiful then it would be easy for others to ready and understand it. If you will keep changing coding rules everyday then after few days you, yourself would not be able to read and understand the code written by you.

If standard is not set, then create the standard but you have to follow some standard, else without any guideline or standard, it would become a mess over the period of time.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.