News for hackers. Stuff that matters.
Re:Updating classic workplace sabotage techniques by zeemonkee3 on Sunday May 15, 2016 @06:02PM (#11702977)
An closed office/cubicle is fine for pair programming. You need room for just 2 people, not 20.
Re:Updating classic workplace sabotage techniques by BurningFrog on Sunday May 15, 2016 @07:38PM (#11703308)
But I want to talk to the rest of the team fairly frequently.
Re:Updating classic workplace sabotage techniques by a3n on Sunday May 15, 2016 @07:45PM (#11703326)
I mean this in the nicest possible way ... Are you sure they want to talk to you ... frequently?
Re:Updating classic workplace sabotage techniques by BurningFrog on Sunday May 15, 2016 @08:44PM (#11703541)
I've worked this way for several years, in a few different teams.

I guess it sounds weird if you've never done it, but it works really well.

Now and then, someone will ask "Hey, does anyone know X?" or something else, and issues will be resolved quickly. One counter intuitive thing that makes this possible is that since you're already engaged in a conversation with your pair, this turns out to not be disruptive.

Re:Updating classic workplace sabotage techniques by home_boi on Sunday May 15, 2016 @09:41PM (#11703723)
i think that type of conversation is better suited for a Slack chat
Re:Updating classic workplace sabotage techniques by prodigal_erik on Monday May 16, 2016 @07:05PM (#11710298)
To me, that suggests pairing would prevent me from ever starting to deeply concentrate on a problem.
Re:Updating classic workplace sabotage techniques by albedoa on Sunday May 15, 2016 @07:59PM (#11703381)
Unless you are also switching pairs frequently, then this is not paired programming.
Re:Updating classic workplace sabotage techniques by douche on Monday May 16, 2016 @06:53AM (#11705486)
That is what chat is for. Bonus, it works whether you and I are breathing the same oxygen, or if we are on different continents.