Home :: Agile-Book :: coding_standards

(book cover)

Order it now!

Welcome to the The Art of Agile Development website. Think of this as the "special features" DVD for the book, only without the DVD. (If you haven't bought the book yet, that's okay... we won't tell if you don't.) Here, you'll find a cornucopia of bonus material, such as downloadable posters, behind-the-scenes material, and new insights.

For more bonus material, see the table of contents. New entries are posted most Wednesdays.

(If there's nothing else on this page, this chapter has yet to be posted. Try the table of contents instead.)

 Print

The Art of Agile Development: Coding Standards

by James Shore

21 May, 2008

in 99 words

In team software development, we create a collective work that is greater than any individual could create on his own. Arguing about style gets in the way.

When creating a coding standard, your most important achievement will be learning how to disagree constructively. To succeed, create the minimal set of standards you can live with. Focus on consistency and consensus over perfection. Remember that few decisions are irrevocable in agile development.

Assume your colleagues are professional and well-meaning. If they deviate from the standard, discuss reasons rather than placing blame. No coding standard can substitute for professional judgement.

as haiku

Fists fly, dust billows--
Tomatoes die, peas cry, as
we choose rose's hue.

Rant

Get a Life!

Inside the Book

  • Coding Standards
  • Beyond Formatting
  • How to Create a Coding Standard
  • Dealing with Disagreement
  • Adhering to the Standard
  • Questions
    • We have legacy code that doesn't fit our standard. Should we fix it?
  • Results
  • Contraindications
  • Alternatives

Loading...

Home :: Agile-Book | Comments (...)

Loading comments...