Development Cycles
  Home arrow Development Cycles arrow Coding Standards
Iron Speed
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Dedicated Servers  
Download TestComplete 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
IBM Developerworks
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
DEVELOPMENT CYCLES

Coding Standards
By: Gabor Bernat
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 2
    2008-03-05

    Table of Contents:
  • Coding Standards
  • The Advantages and Disadvantages
  • A Taste of Standards
  • More About Standards
  • Conclusions

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT

    Ajax Application Generator Generate database and reporting .NET Web apps in minutes. Quickly create visually stunning, feature-rich apps that are easy to customize and ready to deploy. Download Now!

    Coding Standards
    (Page 1 of 5 )

    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.

    In the pursuit of it, we will start with presenting the advantages and disadvantages of standard coding. For the sake of not just talking into the air, we shall also demonstrate some pure code examples, so you can see the difference(s). We are going to end this short trip into the world of standard codes by choosing the correct and recommended paths as far as "rebel" coding and standard coding are concerned.

    Introducing the Standard Code

    If the 20th century made the spreading of the education at a global scale possible via the schools, then in our era, with the extension of computers and the Internet, the software market has certainly risen. Information is no longer something that demands a great fortune or admission into a well-known college. Everyone can learn almost anything if s/he has the will power to sacrifice her/his free time. The Internet makes all information available and just a click away. Really good guides for programming in different languages are distributed all over the net like mushrooms after a warm summer rain. A multitude of new programmers, after their first contact with this business thanks to the online world, decided to take a share of it and become developers.



    Nowadays coding can be learned by anyone. All you need is time and the right attitude. After passing through several pages of reading and a couple of months, you'll become a great programmer. But after you reach this stage, it is time to learn something else that will take your code to another level. Coding standards' most important benefits show up when you code in a team, but adopting it in your everyday programming is also very useful because this will result in a better understanding of your code by others. But in developer teams, adopting a standard of coding will offer much faster application creation and less effort for  bug-tracking/modifications.

    From time to time it seems like everyone can code, but it's trickier to code the right and beautiful way. To start, we should define what the "right way" is. From the perspective of an outsider, in your code the right way is to write code that is efficient, reliable, and easily comprehensible. These attributes are very important for a few obvious reasons. The value of code increases with its reusability factor. More efficient code can be easily modified and/or extended by other people later on, even if you dug out an older code segment that you wrote a few years back. If you are really in the software programming business, then don't expect to remember every code snippet you wrote throughout your career. This way, code conforms to the Coding Standard, which can spare you time and effort in the future. Understanding foreign code and identifying the issues with it is the nightmare of a developer.

    At its foundation, standard coding is a set of commonly accepted rules by people that make the above mentioned attributes for a code snippet possible. There are quite a lot of them. It depends on the coding language used or it may be a guideline promoted by Microsoft, or maybe not. In the following section, we shall inspect the advantages of a coding standard regardless of the upper sorting criteria.

    More Development Cycles Articles
    More By Gabor Bernat


     

    DEVELOPMENT CYCLES ARTICLES

    - Coding Standards
    - A Peek into the Future: Transactional Memory
    - Learning About the Graph Construct using Gam...
    - Learning About the Graph Construct using Gam...
    - Learning About the Graph Construct using Gam...
    - How to Strike a Match
    - Entity Relationship Modeling
    - Tame the Beast by Matching Similar Strings
    - 5 Web Design Tips You Can't Live Without
    - Practising Best Practises in Your Software D...
    - The Art of Modelling: Part 1
    - Thoughts on the Craft of Programming: Abstra...
    - Hi 5: Part 4
    - Domain Modeling: Leveraging the Heart of RUP...
    - Quality Vs Speed: Paradox Lost?






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway