News for hackers. Stuff that matters.
Re:Updating classic workplace sabotage techniques by BurningFrog on Sunday May 15, 2016 @05:46PM (#11702919)
An open office is essential if you're pair programming.

If not, I agree it makes no sense. I guess it can cut down on frivolous browsing.

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.
Re:Updating classic workplace sabotage techniques by kristianp on Sunday May 15, 2016 @08:57PM (#11703597)
This raises an interesting question, how do you become a deep worker if you're pair programming? I guess it's because the pair is both working on the same problem and can both get deep focus on that problem. Implies they should have their own office though.
Re:Updating classic workplace sabotage techniques by bitwize on Monday May 16, 2016 @03:40AM (#11704841)
You don't become a "deep worker".

Concentrating deeply means you're keeping too much state in your head. Write more tests instead. If it's still a problem, bring a co-worker over, or better yet, pair program. It's not the 1980s anymore, this industry is not for solitary special-snowflake hackers. You're a part of a team -- like a node in a cluster -- and the team's productivity is what matters.

Re:Updating classic workplace sabotage techniques by kristianp on Monday May 16, 2016 @07:07PM (#11710309)
At first I thought this was serious, but I'm not sure now. Surprising that a couple of responses to the grandparent say that programming doesn't require deep focus!
Re:Updating classic workplace sabotage techniques by BurningFrog on Tuesday May 17, 2016 @02:55AM (#11711777)
Trust me, it was surprising experiencing it too!
Re:Updating classic workplace sabotage techniques by blub on Monday May 16, 2016 @06:08AM (#11705336)
It would be nice if those pesky humans could somehow be re-programmed to behave more like the nodes/cogs that they truly are instead of being mere... free-spirited individuals. Then our ideal of the pair-programming, cluster-based corporation would become reality, comrade.
Re:Updating classic workplace sabotage techniques by SmellyGeekBoy on Monday May 16, 2016 @08:44AM (#11705897)
Why stop at pairs? Clustered collective consciousness is the clearly the future of programming. ;)
Re:Updating classic workplace sabotage techniques by bitwize on Monday May 16, 2016 @12:06PM (#11707221)
Hence all the meetings.
Re:Updating classic workplace sabotage techniques by BurningFrog on Monday May 16, 2016 @02:32AM (#11704623)
I used to think I needed deep focus and concentration to program. Then I started pair programming. I never got that deep focus, and I became very much more productive!!

Wound not have guessed that!

Now I think that if you need to focus very hard to program, you code and/or design is way to complicated.