Comments on: Pair Programming: Where Teamwork Comes Out http://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/ The personal blog of Brandon Savage. Contains entries of a personal and professional nature focusing on PHP, Apple, LAMP, MySQL and Washington, DC. Thu, 29 Jul 2010 19:10:45 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Brandon Savagehttp://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/#comment-1470 Brandon Savage Sun, 04 Oct 2009 11:10:30 +0000 http://www.brandonsavage.net/?p=783#comment-1470 Another way that I use it is to teach a new developer on a project the ropes. They understand logic, but they might not know the ins and outs of a particular application. Another way that I use it is to teach a new developer on a project the ropes. They understand logic, but they might not know the ins and outs of a particular application.

]]> By: Ernie Leseberghttp://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/#comment-1466 Ernie Leseberg Sun, 04 Oct 2009 04:23:09 +0000 http://www.brandonsavage.net/?p=783#comment-1466 I agree with the comment of Artur. In my experiences of pair programming works well in the early stages of development, when beginning to implement an overall design. It helps programmers confirm they are moving in the same direction with a higher quality foundation. I agree with the comment of Artur. In my experiences of pair programming works well in the early stages of development, when beginning to implement an overall design. It helps programmers confirm they are moving in the same direction with a higher quality foundation.

]]> By: Artur Ejsmonthttp://www.brandonsavage.net/pair-programming-where-teamwork-comes-out/#comment-1428 Artur Ejsmont Fri, 02 Oct 2009 08:52:58 +0000 http://www.brandonsavage.net/?p=783#comment-1428 I only use it from time to time on mission critical stuff but its not a bad way to work.Also important fact is that you get better design and less hacks and less shoddy temporary solutions. People working together have deep inner force to 'prove' themselves so they wont go for shoddy solution as they would locked alone in he basement.And finally you get more knowledge spread around the team. I only use it from time to time on mission critical stuff but its not a bad way to work.

Also important fact is that you get better design and less hacks and less shoddy temporary solutions. People working together have deep inner force to ‘prove’ themselves so they wont go for shoddy solution as they would locked alone in he basement.

And finally you get more knowledge spread around the team.

]]>