Subscribe (RSS)
Follow Me (Twitter)
Print- Next: Iteration Demo
- Previous: Stand-Up Meetings
- Up: Chapter 6: Collaborating
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!Section Outline
- 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
Full Text
This section will go online later this year. In the meantime, why not buy the book?
- Next: Iteration Demo
- Previous: Stand-Up Meetings
- Up: Chapter 6: Collaborating
Loading comments...