CodingStandards

UserPreferences

XP uses Coding Standards. Code is shared among the team, and therefore shouldn't contain individual's coding conventions. This makes coding egoless and prevents unnecessary work reformatting code.

Programmers write all code in accordance with rules emphasizing communication through the code.

-- GregHouston - 26 Apr 2001

• I don't like it
• I didn't select it
• lack of discipline (habit, ego?)
• lack of personal consequences for not following
• no enforcement
• no industry standard (for some languages)
• smacks of control/dictatorship

How is it any different if done "eXtreme"?

• it's actually followed, 100%
• enforced
• enjoyed (really)
• self documenting code (really)
• still have comments for class responsibilities, non obvious algorithms, business processes

What other practices support this practice?

• CommonVocabulary helps with naming
• PairProgramming is the enforcement

What other practices are supported by this one?

• reduces distractions so we can focus on SimpleDesign, Refactoring, UnitTesting, PairProgramming
• makes CollectiveOwnership more effective

How do I get started?

• pair program
• adopting one may be more successful than rolling your own
• use the ide's code formatter
• Then evolve/enhance the standards with feedback from pairprogramming and from your use of your metaphor, design patterns, etc.

That it! This is the end. Back to the start: FuquasXpPresentation

It's much easier to adopt a coding standard when the code is well refactored and self documenting (small methods, descriptive names) and therefore has few comments.

-- AndrewFuqua - 27 Mar 2002