Use the same tools in a team

From WikiContent

(Difference between revisions)
Jump to: navigation, search
(New page: We all love our tools. And many of us think that we use the BEST tools and that our tools are more effective and better than the tools our co-workers are using. But, when you work in a tea...)
Current revision (15:46, 3 February 2009) (edit) (undo)
 
Line 1: Line 1:
-
We all love our tools. And many of us think that we use the BEST tools and that our tools are more effective and better than the tools our co-workers are using. But, when you work in a team, the team often is way more effective if everybody uses:
+
We all love our tools. And many of us think that we use the ''best'' tools and that our tools are more effective and better than the tools our co-workers are using. But, when you work in a team, the team is often way more effective if there is some consistency across the team:
* Exactly the same tool chain
* Exactly the same tool chain
-
** E.g. exactly the same version of the same IDE, etc.
+
** E.g., exactly the same version of the same IDE, etc.
* Exactly the same code conventions and code style
* Exactly the same code conventions and code style
* Exactly the same process of contributing code
* Exactly the same process of contributing code
-
** E.g. cleanup the code using the team's code conventions and styling before checking code in.
+
** E.g., clean up the code using the team's coding conventions and styling before checking code in.
After a while, collaboration of team members will automatically improve.
After a while, collaboration of team members will automatically improve.
 +
 +
By [[Kai Tödter]]
 +
 +
This work is licensed under a [http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]
 +
 +
 +
 +
Back to [[97 Things Every Programmer Should Know]] home page

Current revision

We all love our tools. And many of us think that we use the best tools and that our tools are more effective and better than the tools our co-workers are using. But, when you work in a team, the team is often way more effective if there is some consistency across the team:

  • Exactly the same tool chain
    • E.g., exactly the same version of the same IDE, etc.
  • Exactly the same code conventions and code style
  • Exactly the same process of contributing code
    • E.g., clean up the code using the team's coding conventions and styling before checking code in.

After a while, collaboration of team members will automatically improve.

By Kai Tödter

This work is licensed under a Creative Commons Attribution 3


Back to 97 Things Every Programmer Should Know home page

Personal tools