Sid’s Blog

(life => life.make_it_better)

Does your code communicate with other Dev’s?

| Comments

In a team atmosphere, the personal nature of coding style is a challenge. 

The following example might explain the importance of coding style:

“The situation of a group of musicians trying to form a band. Each one comes in believing that their way of doing things is best (their “method” or “process”). The band will struggle so long as everyone is trying to do their own thing. It’s impossible to create good music unless everyone in the band agrees on the tempo, the style and who should take lead during a song. Anyone who has ever heard a high school band perform knows this to be true. Unless everyone is on the same page, you aren’t going to accomplish much.“Thus, we should start following a style guide. Following are the few style guides that I have in my list and I try to follow them.

  6.  Microsoft - Design Guidelines for Class Library Developers.
  7. CSharp Coding  IDesign C# Coding Standard.
  8. Dan Rigsby C# Coding Standards.
  9. SubMain C# / VB.NET Coding Guidelines.
  10. Lance Hunt - C# Coding Standards.
  11.  DotNetSpider - C# Coding Standards and Best Programming Practices.
  12. Microsoft - C# Programming Guide.
  13. Phillips Medical Systems - Coding Standard C#. You can opt one and start extending it. Also, you might also have some experience or resources under your arsenal :D which you can share with team members.