蓝牙配对不弹配对框

Pair programming is two programmers working together at one workstation.

结对编程是指两个程序员在一个工作站上一起工作。

Formally, one programmer is the driver and writes code. The other is the observer or navigator who reviews each line of code as it is typed in.

正式地，一个程序员是驱动程序并编写代码。 另一个是观察者或导航者，他们会在输入的每行代码中进行检查。

Informally, they sit together on one code base and talk about stuff and break problems down. Either of them can write code and neither of them does anything else like checking the phone.

非正式地，他们在一起坐在一个代码库上，谈论东西和分解问题。 他们中的任何一个都可以编写代码，并且它们都不能执行其他操作，例如检查电话。

Pair programming is widely adopted by some organizations and shunned by others. It is always a topic for debate and people will have their preferences. We are all humans and there are times when almost everyone can benefit from pair programming.

结对编程已被某些组织广泛采用，而另一些组织则回避。 这一直是辩论的话题，人们会有所选择。 我们都是人类，有时候几乎每个人都可以从结对编程中受益。

Yet, it seems like an ineffective use of resources. We have two programmers. They could both be building different features for a week, at the end we will have twice as many features. But this isn’t the case and you may well end up with 2 sets of 95% done features that can’t be shipped. Programming together can increase the net amount of actually complete features you ship.

但是，这似乎是对资源的无效利用。 我们有两个程序员。 他们可能都将在一周内构建不同的功能，最后，我们将拥有两倍的功能。 但是事实并非如此，您可能会获得无法交付的两组95％完成的功能。 一起编程可以增加您所交付的实际完整功能的净数量。

好处 (The Benefits)

更少的错误和错误保留 (Fewer Mistakes and Bug Hold Ups)

We’ve all had crazy hard bugs. These can be from fundamental flaws in the entire approach or a typo, an incorrect install or the need for a reboot.

我们都有疯狂的硬错误。 这些可能来自于整个方法的基本缺陷或错别字，安装不正确或需要重新启动。

As a team, the chances are that one of you has made a similar mistake before. Or it is likely that one of you knows someone else that has encountered the problem. And you are more likely to allocate the correct time to a problem before going back to the drawing board.

作为一个团队，很可能你们中的一个人以前犯过类似的错误。 或者您中的某人可能认识其他遇到此问题的人。 而且，您更有可能在返回图纸之前为问题分配正确的时间。

You can discuss better strategies. This is better than keeping the problem hidden all day without sharing it with others.

您可以讨论更好的策略。 这比将问题整天隐藏而不与他人共享更好。

更容易坚持下去—道德支持 (Easier to Keep Going — Moral support)

Often working as a team can increase positivity about a problem. When someone shares a problem you are going through, you feel less defeated and more positive about trying again and again and again…

通常，团队合作可以提高对问题的积极性。 当某人遇到您遇到的问题时，您会感到挫败，而对一次又一次地尝试感到更加积极……

难以拖延 (Harder to Procrastinate)

Working as a team means you can’t stop and check your Email, Slack or Whatsapp for any desired distraction.

团队合作意味着您无法停止并检查您的Email，Slack或Whatsapp是否有任何需要分心的东西。

This seems like a small thing. But you can quadruple the number of hours a coder spends in the editor and coding, instead of sitting at a desk eating up hours of the day until time to go home.

这似乎是一件小事。 但是您可以将编码员在编辑器和编码中花费的时间增加三倍，而不必坐在办公桌前一天要花很多时间才能回家。

共同的最佳实践 (Shared Best Practices)

Coding together is a great way to share knowledge in your company. Coders can give each other tips as they go along to improve their approach and increase their speed.

一起编码是在公司中共享知识的好方法。 编码人员可以互相交流技巧，以改进方法并提高速度。

Working together may uncover knowledge that may not be in your New Employee Handbook.

一起工作可能会发现“新员工手册”中可能没有的知识。

更快的登船 (Faster On-Boarding)

New employees can get up to speed much faster by pairing with an experienced team member.

通过与经验丰富的团队成员结对，新员工可以更快地起步。

识别并减少不良雇佣 (Identify and Reduce Bad Hires)

It can help identify bad hires early on if someone isn’t the right fit for a business or was hired for the wrong role. You can do something about it early on before you waste both parties’ time.

如果某人不适合某项业务或因错误的角色而被雇用，它可以帮助及早发现不良员工。 您可以在浪费双方时间之前尽早采取一些措施。

During a hiring interview, a team familiar with pair programming will be better at assessing if the candidate can program with others. If the normal guy who conducts interview sessions is absent, you can be confident that someone else can replace him and give a fair analysis.

在招聘面试中，熟悉结对编程的团队会更好地评估候选人是否可以与他人编程。 如果没有参加面试的普通人，您可以确信其他人可以代替他并进行公正的分析。

提高员工满意度 (Increase Employee Satisfaction)

Coding together may bring employees closer as they share experiences and have more subjects to talk about. When other people understand what you’re up to you’ll have more in common. This can affect a lot of important business areas. It can even improve the topics of conversation at lunch to reduce employee churn.

在一起编码可能会使员工分享经验和谈论更多主题时离他们更近。 当其他人了解您要做什么时，您将有更多共同点。 这会影响许多重要的业务领域。 它甚至可以改善午餐时的谈话主题，以减少员工流失。

Coding can be a lonely pursuit when you are behind a computer alone and told to produce features. Reducing any alienation in a company is important. This is one reason I’d suggest having a system of pair programming for early-stage start-ups as well as big enterprises.

当您独自一台计算机背后并被告知要产生功能时，编码可能是一个孤独的追求。 减少公司中的疏远感很重要。 这是我建议为早期初创企业以及大型企业提供结对编程系统的原因之一。

问题—配对不良时 (Issues — When Pairing Goes Bad)

Pair programming can mess things up and needs a sensible approach.

结对编程可能会使事情变得混乱，需要明智的方法。

不要过度(或不充分) (Don’t Overdo It (or Under do it))

Forcing people to spend all day together isn’t sensible and they may well end up hating each other.

强迫人们花一整天在一起并不明智，他们最终可能会彼此讨厌。

1.5–2.5 hour bursts usually works best. Less is too short and it’s a waste of time.

1.5-2.5小时的爆发通常效果最好。 少就是太短，这是浪费时间。

奖励共享贡献 (Reward Shared Contribution)

If you’ve given important deadlines to two programmers and then assign one to help the other with his task, you’re heading for a potential disaster. When you review who’s completed their tasks and one feels like they’ve done nothing, the personal metrics suffer. Mentally this is bad. But if it’s linked to any reward system you are shooting yourself in the foot. As a scrum master you need to make sure you account for pairing and assign tasks fairly.

如果您给了两个程序员重要的最后期限，然后分配一个来帮助另一个程序员完成任务，那么您将面临潜在的灾难。 当您查看谁完成了任务并感到自己什么都没做时，个人指标就会受到影响。 精神上这是不好的。 但是，如果将其与任何奖励系统联系在一起，则说明您正在朝自己的脚射击。 作为Scrum管理员，您需要确保您负责配对并公平地分配任务。

累了的编码员 (Tired Coders)

More coffee and pairing up is not always the answer. When you’re tired and stressed you might not be communicating properly.

多喝咖啡和配对并非总是答案。 当您感到疲劳和压力大时，您可能无法正确交流。

This can cause more problems in the code and between each other. Some people perform better this way and some don’t so you may be taking a risk.

这可能会导致代码中以及彼此之间出现更多问题。 有些人以这种方式表现更好，有些则没有，所以您可能会冒险。

复杂代码-配对或讨论 (Complex Code — Pair-up or Discuss)

For more complex code it might be a distraction trying to pair together. Sometimes sitting down and explaining the problem can be more beneficial.

对于更复杂的代码，尝试组合在一起可能会分散注意力。 有时坐下来解释问题可能会更有益。

Formally sitting down together and writing code line by line could actually be distracting.

正式坐在一起并逐行编写代码实际上可能会分散注意力。

其他想法 (Other Thoughts)

但是远程工作者呢？ (But what about Remote workers?)

Employees working remotely can pair program with online screen sharing tools. I’ve debugged friends code in Brussels while sitting in a cafe in Kazakhstan. Trust me it’s possible.

远程工作的员工可以将程序与在线屏幕共享工具配对。 我坐在哈萨克斯坦的一个咖啡馆调试了布鲁塞尔的朋友代码。 相信我，这是可能的。

有证据吗 (Any proof?)

These are reflections from my experiences. I’ve perceived these benefits while working with various businesses and different bootcamps.

这些是我经验的反映。 在与各种企业和不同的训练营合作时，我已经意识到了这些好处。

As a scientist I accept that I’ve never done a double-blind trial on the benefits. Of course it’s never been a big enough priority compared to just getting stuff done.

作为科学家，我接受我从未对这种益处进行过双盲试验。 当然，与仅仅完成工作相比，这从来没有成为一个足够大的优先事项。

But I would love a study with over 100 participants working on the same set of problems. One group of 50 could work in pairs and the other group could work solo. I’d like to see what happens. It could be a nice study for any computer science professors to do.

但是，我希望有100多名参与者研究同一组问题的研究。 50人一组可以成对工作，另一组可以单独工作。 我想看看会发生什么。 对于任何计算机科学教授来说，这都是一个不错的研究。

结论 (Conclusion)

So as you can see I’m a fan of pair programming. Some coders don’t feel it’s an effective use of their time. If you’re a manager it’s up to you to assess the situation and make the most of your team. Either way, it is definitely something all companies should allow for at times.

如您所见，我是结对编程的爱好者。 一些编码人员认为这不是对时间的有效利用。 如果您是经理，则需要您评估情况并充分利用团队。 无论哪种方式，这绝对是所有公司有时都应该允许的。

It should be implemented dynamically rather than enforced. Any boot-camp should incorporate it into their course to build a well-rounded coder.

它应该动态实现而不是强制执行。 任何新手训练营都应将其纳入自己的课程中，以构建全面的编码器。

We use it often in my own dev agency, from tackling our hardest issues to on-boarding new staff. It’s a process we enjoy using to boost performance and knowledge across the company. Of course, we don’t enforce it all day and every day! But we like it and we’re keeping it.

从解决最棘手的问题到新员工入职，我们经常在自己的开发机构中使用它。 这是我们喜欢用来提高整个公司绩效和知识的过程。 当然，我们不是每天都执行它！ 但是我们喜欢它，并且一直保持下去。

As the old saying goes “A problem shared, is a problem halved.”

俗话说“ 一个问题共享，一个问题减半。 ”

I run a podcast on growth mindset and tech start-up. If you enjoyed this you’ll learn more by subscribing.

我在成长心态和科技初创公司上播客。 如果喜欢这个，您可以通过订阅了解更多。

If you’ve used pair programming I’d love to hear your thoughts on it. What practices or tips do you use to decide when to pair or not?

如果您使用过结对编程，那么我很想听听您对此的想法。 您使用什么做法或技巧来决定何时配对？

翻译自: https://www.freecodecamp.org/news/the-benefits-and-pitfalls-of-pair-programming-in-the-workplace-e68c3ed3c81f/

蓝牙配对不弹配对框