blocks|key|5273380|text|结对编程是基于两个程序员的交互增加价值的思想。如果这不是真的，请更改对...让他们自己选择吧。编程应该是有趣的！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5273381|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Pair programming is based on the idea that the interaction of two programmers adds value. If this is not true, change the pairs... let them choose. Programming should be fun!

blocks|key|5273461|text|如果每周或每次冲刺都轮换一次配对，这样如果两个配对之间出现问题，他们就不会觉得永远都是这样。我认为，如果有一个特定的时间框架，你必须与一个你不能相处的人一起工作，这会让你更容易“接受它”，希望你不会失去任何优秀的人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5273462|如果在几次轮换之后，你注意到一个没有人喜欢的特定个人，那么专注于调整个人与团队交互的方式可能是合适的，或者如果它继续永远将他们从团队中移除。|5273463|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

How about rotating the pairs every week or every sprint so that if there are issues between a couple of pairs they don't feel like it has to be that way forever. I think if there is a specific time frame that you have to work with someone you do not get along with it makes it easier to "suck it up" and hopefully you won't lose any great people that way.

If after a few rotations you notice a specific individual that nobody is enjoying it may be appropriate to focus on adjusting the way that individual interacts with the team or if it continues perpetually removing them from the team all together.

blocks|key|3017518|text|重新评估你的招聘实践，确保你选择的是以团队为导向的员工。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3017519|如果做不到，那就吃薄荷糖吧。|3017520|-Adam|3017521|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Reassess your hiring practices and make sure that you select for team oriented employees.

Failing that, breath mints.

-Adam

blocks|key|3017319|text|他们到底有什么问题？他们是不是相处不好，彼此不理解？他们的编程经验是不同的吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3017320|如果你有一个团队成员可以充当某种“中介者”，这可能会有所帮助。过去成功地完成结对编程的人，可以帮助他们一起度过最初的几次。|3017321|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

What exactly are they having problems with? Do they not get along, not understand each other? Are they at different levels of programming experience?

It may help if you have a team member that can act as a "mediator" of sorts. Somebody who's successfully done pair-programming in the past and can help the two through their first few times together.

blocks|key|3017418|text|解决冲突的第一步是认识到人们是不同的。即使是最温和的程序员的耐心也可以在结对编程中尝试，这可能会非常有压力。一些人在遇到冲突时会退缩，另一些人则变得咄咄逼人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3017419|以我的经验，处理结对编程的最好方法是在您动手编写代码之前，详细讨论您希望在会话中完成的任务。这会让你们两个的思想走到同一条轨道上。当你在某件事上有不同意见时，停止编码，远离计算机进行讨论，试着找到共同点，最重要的是，不要否定你的伴侣可能会有的任何想法。休息一下；不要连续工作两个小时，试着每隔45分钟左右站起来或休息一下。|3017420|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The first step to resolving conflicts is to recognize that people are different. Even the most mild mannered programmer's patience can be tried in pair programming, it can be very stressful. Some people withdraw when they are confronted by conflict, others get aggressive. 

The best way of approaching pair programming, in my experience, is to have a detailed discussion of what it is you want to accomplish for the session, before you lay hands on code. This will put both of your minds on the same track. When you disagree on something, stop coding, discuss it away from the computer, try to find common ground and most importantly don't dismiss any ideas your partner may have. Take breaks; don't work for 2 hours straight, try to stand up or go for a break every 45 minutes or so.

blocks|key|3862574|text|作为一个小组讨论配对问题，并确保小组意识到不同的配对不起作用。这样，小组就可以帮助确保你们的配对不会互相躲避。如果你将一个故障对分开，它们将永远是故障的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3862575|让双方打通沟通渠道；尝试让双方都做新的事情。假设两个人都是真正优秀的开发人员，他们都有很多东西可以相互学习。试着改变他们从老师到学生的态度。|3862576|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Talk about pairing troubles as a group, and make sure the group is aware of different pairings that aren't working. That way, the group can help ensure that your pairs aren't avoiding each other. If you keep a disfunctional pair separate, they will always be disfunctional.

Get the pair to open lines of communication; try to get both sides to do new things. Assuming both people are genuinely good developers, they both have much to learn from one another. Try to alter their attitude from teacher to student.

blocks|key|764758|text|我的第二个问题是--他们对什么东西有问题？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|764759|根据我的经验，这些问题通常(但不总是)是团队结构/技能/关系存在潜在问题的迹象，如果你想最大限度地利用参与其中的每个人，就需要解决这些问题。|764760|玛丽和弗雷德相处不好是因为弗雷德对理智的人如何使用数据库知之甚少吗？是不是因为乔没有像他们预期的那样经常洗澡，所以弗雷德和乔相处得不好？乔和玛丽相处不好是因为玛丽是个粗鲁的混蛋吗？如果是这样的话，你几乎可以保证Fred，Jo+&+Mary也在以类似的方式惹恼团队的其他成员。|764761|仅仅因为一两个人足够推动问题以避免配对，并不意味着问题就消失了。这可能也会惹恼其他人--他们可能有不同的应对方式。例如，寻找替代工作:-)|764762|如果团队不能很好地合作，那就不是一个团队。|764763|出于好奇心--你的配对时间有多长，你多久交换一次配对？我发现，如果人们定期交换配对--一天一到两次，有时处理这类事情会更容易。这样每个人都可以分享团队中每个人的相对优势和劣势-这可以帮助每个人专注于解决一些劣势。|764764|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I'd second muloh's question - what kinds of thing are they having problems with?

In my experience these problems are often (but not always) a sign of underlying problems with the team structure / skills / relationships that need to be addressed if you want to get the best out of everybody involved.

Is Mary not getting along with Fred because Fred doesn't know enough about how sane folk work with databases? Is Fred not getting along with Jo because Jo doesn't bathe quite as regularly as they ought? Is Jo not getting along with Mary because Mary is a rude SOB? If so you can almost guarantee that Fred, Jo &amp; Mary are also annoying the rest of the team in similar ways.

Just coz one or two folk push the issue enough to avoid pairing doesn't mean the problems goes away. It may well be annoying other folk too - they may have alternate ways of coping. Like looking for alternate employment for example :-)

If the team doesn't work well together it isn't a team.

Out of curiosity - how long are your pairing sessions and how often do you switch pairs? I find that it's sometimes easier to deal with this sort of thing if folk are switching pairs on a regular basis - once or twice a day. That way everybody gets to share the relative pros and cons of everybody on the team - which can help everybody focus on solving some of the cons.

blocks|key|5273953|text|另一种方法是在scrum中不断交换配对。有一个计时器，可以设置为1/2/3小时。当铃声响起时，轮换你们的组合。这有几个影响：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5273954|5273955|两个人在一起不会卡在一起很长时间|unordered-list-item|5273956|你的开发人员将可以轮流浏览你当前的故事，熟悉代码的每一个和不同的区域|5273957|如果你的开发人员有一股臭味，你只需要经历一小段时间的恶臭！|5273958|5273959|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|N|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

Another approach is to continually switch your pairs within the scrum. Have a timer which might be set for 1/2/3 hours. When the bell goes off, rotate your pairs. This has a few effects:

<ul>
<li>Two people don't get stuck pairing together for a long time</li>
<li>Your developers will get to rotate through your current stories, getting familiar with each one and different areas of the code</li>
<li>If one of your dev's smells, you will only have to get through a short period of stink!</li>
</ul>

blocks|key|762173|text|配对是敏捷团队的关键实践。首先，最好找出愿意并能够有效地结对工作的开发人员。据我所知，有一家公司做极端面试。也就是说，他们将成对面试候选人，给他们一个要解决的问题。他们感兴趣的是开发人员是否有能力解决问题，但对他们的协作技能感兴趣。只有那些能与他人良好合作的人才会被考虑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|762174|并不要求所有的配对都彼此喜欢。重要的是它们是有效的。考虑到配对频繁轮换(对于每张卡或更频繁)，个性不是问题。如果有人没有跨双人组，并且在接受指导后仍然是一个问题，他或她应该被要求离开球队。|762175|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Pairing is a critical practice for an agile team. To begin with, it is best to identify developers that are willing and able to work effectively in pairs. One company I am aware of does extreme interviewing. That is, they will interview candidates in pairs giving them a problem to solve. They are interested if the developers are ability to solve the problem but are interested in their collaboration skills. Only those that can work well with others are considered.

It is not a requirement that all pair like each other. What is important is that they are effective. Given that pairs rotate frequently (for each card or more frequently), personality is less of an issue. If someone is not across pairs, and after being coached is still a problem, he or she should be asked to leave the team.

Some members of the team are having problems programming together. 
Different gender, different culture, different age. How to deal with those problems?
 - Do not pair them together, or
 - Pair them together and let them come to a "golden middle"

How to deal with pair programming issues?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

团队中的一些成员在一起编程时遇到了问题。不同性别，不同文化，不同年龄。如何处理这些问题？-不要将它们配对在一起，或者-将它们配对在一起，让它们达到“黄金中间”。

问如何处理结对编程问题？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何处理结对编程问题？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何处理结对编程问题？
EN