Comments on: The Forces of Destruction http://blog.franktrindade.com/2009/01/21/the-forces-of-destruction/ Agile, software and some non-sense Thu, 17 Jun 2010 09:41:19 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Getting the best developers available « Absolut Agile http://blog.franktrindade.com/2009/01/21/the-forces-of-destruction/comment-page-1/#comment-1478 Getting the best developers available « Absolut Agile Sun, 03 May 2009 10:44:43 +0000 http://blog.franktrindade.com/?p=180#comment-1478 [...] and rewarded into preferring individual achievements rather than team success. His post is called The forces of Destruction, after a citation by W E Deming. For example, we’re individually graded in [...] [...] and rewarded into preferring individual achievements rather than team success. His post is called The forces of Destruction, after a citation by W E Deming. For example, we’re individually graded in [...]

]]> By: Daniel Cukier http://blog.franktrindade.com/2009/01/21/the-forces-of-destruction/comment-page-1/#comment-287 Daniel Cukier Thu, 12 Feb 2009 13:52:29 +0000 http://blog.franktrindade.com/?p=180#comment-287 Nice point, Frank. For me the benefits of Pair Programming are so clear. I try to stimulate people here in Locaweb to do it, but the cultural barrier is huge! It's been two years I talk about pair programming and still now I see a one-person-per-computer environment. What do you suggest me to do? How can I convince people that collaborating and pairing is better than do it alone? Do you think there's will be a big change, or things will happen slowly, as long as people change their own beliefs? Nice point, Frank. For me the benefits of Pair Programming are so clear. I try to stimulate people here in Locaweb to do it, but the cultural barrier is huge! It’s been two years I talk about pair programming and still now I see a one-person-per-computer environment. What do you suggest me to do? How can I convince people that collaborating and pairing is better than do it alone? Do you think there’s will be a big change, or things will happen slowly, as long as people change their own beliefs?

]]> By: franktrindade http://blog.franktrindade.com/2009/01/21/the-forces-of-destruction/comment-page-1/#comment-265 franktrindade Thu, 22 Jan 2009 12:12:22 +0000 http://blog.franktrindade.com/?p=180#comment-265 Not entering in the communist love-fest discussion (even because I wouldn't join it), I definitely disagree with the XP non-productive part. I'm not saying that people should pair all the time, but work collaboratively brings huge benefits, in my opinion. And when no one on the team knows how to write software, well, than you have much bigger problems that trying to define your methodology. Not entering in the communist love-fest discussion (even because I wouldn’t join it), I definitely disagree with the XP non-productive part.

I’m not saying that people should pair all the time, but work collaboratively brings huge benefits, in my opinion.

And when no one on the team knows how to write software, well, than you have much bigger problems that trying to define your methodology.

]]> By: Anonymous http://blog.franktrindade.com/2009/01/21/the-forces-of-destruction/comment-page-1/#comment-263 Anonymous Wed, 21 Jan 2009 22:54:13 +0000 http://blog.franktrindade.com/?p=180#comment-263 Well, I'll work collaboratively and join the communist love-fest when everyone on the team gets an equal share of the profits. I don't see why everyone is so enamered with conscription at the hands of industrialists when, in reality, they're effectively wage slaves. In addition to the dreadful proletarian aspect of pairing, XP has its technical downside too. Effectively, XP is engineering-specific Lysenkoism. It works well for transferring skills, but it's definitely not productive to do it more than half-of-the-time. This is especially true when no one on the team knows how to write the software. Well, I’ll work collaboratively and join the communist love-fest when everyone on the team gets an equal share of the profits. I don’t see why everyone is so enamered with conscription at the hands of industrialists when, in reality, they’re effectively wage slaves.

In addition to the dreadful proletarian aspect of pairing, XP has its technical downside too. Effectively, XP is engineering-specific Lysenkoism. It works well for transferring skills, but it’s definitely not productive to do it more than half-of-the-time. This is especially true when no one on the team knows how to write the software.

]]>