It might look like you are doubling the budget, but some people recognize that the second coder’s job of catching errors, and the exchange of knowledge between the coders means this isn’t the case.
While I have not had a job where I am permanently paired with another developer, there are many occasions that pair programming is used for temporary projects. It makes a lot of sense when the two developers compliment each other well, for example, one has a good conceptual idea of the system, the other knows the language they are working in very well. I have had both really good and really bad experiences with pair programming and it seems to work best when the two programmers are at about equal skill levels.
February 3rd, 2006 at 6:13 am
Some software companies do it.
It might look like you are doubling the budget, but some people recognize that the second coder’s job of catching errors, and the exchange of knowledge between the coders means this isn’t the case.
February 3rd, 2006 at 4:54 pm
While I have not had a job where I am permanently paired with another developer, there are many occasions that pair programming is used for temporary projects. It makes a lot of sense when the two developers compliment each other well, for example, one has a good conceptual idea of the system, the other knows the language they are working in very well. I have had both really good and really bad experiences with pair programming and it seems to work best when the two programmers are at about equal skill levels.