http://blog.kriskemper.com/2008/08/02/pair-programming-a-peer-to-peer-information-system/ Thoughtworker, Agile Philosopher, Hero Wed, 08 Sep 2010 05:24:55 +0000 http://wordpress.org/?v=2.3.2 http://blog.kriskemper.com/2008/08/02/pair-programming-a-peer-to-peer-information-system/#comment-199 Kris Kemper Sun, 03 Aug 2008 02:12:31 +0000 http://blog.kriskemper.com/2008/08/02/pair-programming-a-peer-to-peer-information-system/#comment-199 Well, in theory broadcasting information is a good thing, but I don't think the benefits apply to developing software. An analogy is that I can explain the step by step process of assembling a bicycle. Most people would not be able to assemble a bike after hearing me tell them how to do it, let alone appreciate the often subtle best practices involves. However, doing it with me right next to them would probably result in a well assembled bike and with them very capable of assembling another. Well, in theory broadcasting information is a good thing, but I don’t think the benefits apply to developing software. An analogy is that I can explain the step by step process of assembling a bicycle. Most people would not be able to assemble a bike after hearing me tell them how to do it, let alone appreciate the often subtle best practices involves. However, doing it with me right next to them would probably result in a well assembled bike and with them very capable of assembling another.

]]> http://blog.kriskemper.com/2008/08/02/pair-programming-a-peer-to-peer-information-system/#comment-197 mats Sat, 02 Aug 2008 23:44:20 +0000 http://blog.kriskemper.com/2008/08/02/pair-programming-a-peer-to-peer-information-system/#comment-197 One could argue that broadcasting information is more effective because you only say things once. When you disseminate information pair by pair, the information is often repeated to every developer. Of course I agree with your point. The one-on-one conversations are always more productive and will happen only on a need-to-know basis, which ensures the information is useful. One could argue that broadcasting information is more effective because you only say things once. When you disseminate information pair by pair, the information is often repeated to every developer.
Of course I agree with your point. The one-on-one conversations are always more productive and will happen only on a need-to-know basis, which ensures the information is useful.

]]>