3 ms·
This guy describes a really common antipattern I've seen with pair-programmers, call it "Workstation Chain Gang". This is where all work is done sitting side-by
by blatherard 16y ago
This guy describes a really common antipattern I've seen with pair-programmers, call it "Workstation Chain Gang". This is where all work is done sitting side-by-side at a computer, and the only times you get up are for the bathroom or eating.
The best pair programmers I've worked with will often do things like: say "let's take a walk" and then talk through design problems, get up and use a whiteboard, say "I want to read about this. Let's get back together in half an hour." Or even say, "I need some alone time" They attend to their own needs along with the needs of their pair. This can take a lot of personal courage and honesty sometimes, and requires an environment that encourages attending to yourself.
This guy sounds like he felt like he needed to put on a continuous show for his partner, and that was really hard for him. Which it is!
I bet he was right that he had to be constantly chained to the workstation. The "eight-week sprint" sounds like a pretty awful slog, especially with the set-in-stone up-front design. Overall, it sounded like a lousy, poorly managed setup.
Its too bad that he associated it with pair programming particularly, but oh well. There's many ways of working in the world, and it sounds like he's happier now.
- harringf 16y ago> "let's take a walk" and then talk through design problems. That is the MOST important part and yet every single training fails t mention this.
- deleted 16y ago[deleted]
- aerique 16y agoYours is the first description of pair programming that I have read that makes it sound reasonable. Your description is perhaps just common sense but it really needs to be said.