According to the dictionary, "standard" stands for “something considered by an authority or by general consent as a basis of comparison; an approved model.” Now you may ask why we need to complicate our lives with the adoption of some coding standards. The answer to this question lies in the following pages.
The code snippet presented on the previous page is only a few lines long, but imagine it as part of a million lines of code. Now, which do you think is more appreciated? Which usage is easier, more straightforward, and certainly easier to debug? If you decided to read the previous pages, then surely the answer will be the second one. And you are right! You should be convinced that regardless of the language you code in, you can and should use coding standards. Each of them is slightly different, and any standard can be modified by the team adopting it. But the results are obvious.
(Photo courtesy of <enerjy.sys-con.com>)
The Department of Commerce's National Institute of Standards and Technology (NIST) estimates that software bugs cost the U.S. economy nearly $60 billion annually and that improved testing could eliminate more than one-third of software failures. So for your own sake, stop wasting cash and your own valuable time. Adopting a good coding standard is the next crucial step for you. Out there in the online world you can find quite a lot of standards that apply to your language, just use Google.
If you managed to reach this part of the article and you are a coder, then you are probably already seeking a coding standard guideline. There are hundreds of rules encapsulated in a guide, but once you get the idea and you catch its drift, this will be one of those steps that you won't regret.
Thanks for reading my article and for any further questions that you might have don't hesitate to visit our friendly community at the DevHardware Forums.
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.