4 ms·
> Studies on pair programming show significant advantages in many circumstances But do these studies take into account employee happiness (and thus potentially
by frostmatthew 13y ago
> Studies on pair programming show significant advantages in many circumstances
But do these studies take into account employee happiness (and thus potentially losing good developers)? In other words, is it better to have five mediocre engineers pair programming or having five stellar engineers working normally?
- ggreer 13y agoFrom section 6.4, titled "Work enjoyment": All agreed that PP promoted the formation of good team spirit in the beginning of the project. The information radiator and the open workspace were also mentioned as contributors to good team spirit. Two of the developers liked PP more than solo programming and two found no difference. Please at least skim references before calling them into question.
- frostmatthew 13y agoThank you, FWIW I had read the abstract...I don't normally read (or skim) the entirety of every study somebody cites. But taking your advice I noticed 7.2 contains: All the developers were recruited based on their interest in using agile practices including PP Personally I would prefer not working in a paired programming environment, though I'm not sure it would be a deal-breaker. But I know developers (more introverted than me) who I imagine it might be.
- ggreer 13y agoWhile it probably biases the numbers a bit, I don't fault the study for picking people who were receptive to new practices. Picking people randomly and forcing them to change practices would just cause resentment. Even though I enjoy pairing, I also doubt I would enjoy working at a place that required people to pair. Rules like that irk me. They're often a symptom of other, bigger problems.