Re[2]: Re: Sex Tips for Promiscious Pairs (was Practice: Pair Programming)

Friday, November 12, 2004, 10:37:52 AM, Lowell Lindstrom wrote:

> In this description of pair programming, 20% of the words are
> devoted to the sexual arrousal issue.  For me, this is significantly 
> out of balance and disconnected from what is happening out there.  
> Ownership and recognition issues are much more accute and 
> detrimental to the team in my observation.  

> Are others seeing or sensing that this is a common problem that 
> warrants that level of treatment in the pair programming chapter?

Office romances and sexual politics can be a problem in any
team, with our without pair programming. We had a couple who
became enamored of each other while working on one of our
development teams. I don't know if pair programming together
helped kindle the romance more than working closely together
in another team setting would have. I know some other team
member were at least somewhat bothered by their behavior I
heard the comment "Get a hotel room" a couple of times from
other team members. The male member of the couple has moved 
to another of our developer teams, and there seems to be less
of a problem now, even though the other team is only 50 feet
away.

On the other hand, this hasn't been a noticeable problem
among our other 30+ developers.

I share Kent's concern about sexual tension engendered by the
close physical proximity of pair programming, and I'm glad he
included a reference to it. Although it's not yet been a
problem for me personally, I don't think I'll point out that
paragraph to my wife. I don't know if Kent's solution is
practical, but it is a place to start.



-- 

 Doug Swartz
 daswartz-fuDLTLi4t9nR7s880joybQ@xxxxxxxxxxxxxxxx



------------------------ Yahoo! Groups Sponsor --------------------~--> 
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->