Is this type of continuous pair programming good? -

I am working in a company where I have been forced to do a pair programming program with 6 years More than I experienced at the same time, we work on the same PC on the same code, design or some other problem.

Damage.
It takes away the feeling of ownership of the result and starts affecting each other's mood.

Profit.
Well thought outcome and output to the company.

I want to know how other developers deal with this type of situation. / P>

pair programming is like figure skating

• you do not need it Have 24x7 together, when you're on the ice! (I.e., many parts of a project are benefited by being coded separately, the couple again reviews the review / debug for the group, but is not actively "competing" for its completion).
• It all depends on your partner: it can work very well or not, independent of skating (or programming) skills.
• This requires the right balance of honesty and patience (speaking, clearly, but at the right time, a clear lack of ownership, or with some tasks, you have great happiness or any other part With about your obstacles ...)

For these reasons, a little steadfast and mandate programming. I am personally in favor of this practice, but I believe that programmers and management should understand the need for "proper chemistry" and when a couple does not work well together, then There should be no least bit of dissatisfaction or judgment.

To ensure this, the programmer should try this discipline at a large scale and earn a living with specific partners (for a long period of time and for various project types) before declaring personality conflict. Should work. It may also be that a given pair works better on special project types.