One of the reasons given for not PairProgramming. Here are some arguments against this.
- Everything we do should be simple.
- Most things that appear to be simple turn out to be icebergs.
- How do you distinguish between "simple" and "not simple"?
In response to this statement from my team, I offered them a compromise. They would be permitted to fly solo on what they considered to be simple changes as long as they agreed to support their code 24/7. In other words, throw
CollectiveCodeOwnership out the window. This didn't seem to be very appealing for some reason. -
KenReigle