有人有过在混合 IDE 环境中进行结对编程的团队经验吗？我是 IntelliJ 的长期用户，其他人使用 Eclipse，您可能听说过。
在我看来，结对编程涉及程序员之间大量传递键盘。但每次我拿到键盘时，我都会停下来，因为我不知道还能做什么。 （就好像我突然变成了一个白痴！）
现在我可以，也许应该，学习 Eclipse 的方法。 （不是在这里开始一场关于相对优点的圣战。）但我想知道是否还有其他人有意见？
Anyone got any experience of teams doing pair programming where there is a mixed IDE environment? I'm a long time IntelliJ user, others use Eclipse, which you may have heard of.
In my mind pair programming involves a lot of passing the keyboard between the programmers. But every time I get the keyboard I grind to a halt as I don't know to do anything anymore. (It's like suddenly I'm an idiot!)
Now I could, probably should, learn my way round Eclipse. (Not starting a holy war here about relative merits.) But I wonder if anyone else has got an opinion?
发布评论
评论（6）
我认为没有必要传递键盘。在我看来，你的一部分在工作，而另一半则在你的身后看着。有时我想您必须开车，但通常不是每 10 分钟一次。如果他打字4个小时，那你就换地方，到时候换IDE就可以了。
我同意你应该学习所使用的工具，如果有实际发布或记录的标准，你应该遵循它，但如果你被允许使用任何你想要的 IDE，那么我没有看到问题。但如果它抑制了您的交付能力，那么您可能会与使用与您相同的 IDE 的人配对。
I don't see the need for passing the keyboard around. In my view, you work on part while the other half of your pair looks over your shoulder. Sometimes I imagine you would have to take the wheel, but generally not every 10 minutes. If he types for 4 hours, then you switch places, just switch IDEs at that time.
I agree you should learn the tools that are used, and if there is an actual published or documented standard you should follow it, but if you are allowed to use any IDE you want, then I don't see an issue. But if it inhibits your ability to deliver, then maybe you pair up with someone using the same IDE as you.
对于OP来说已经晚了大约10年，但是这个问题在搜索引擎中仍然排名很高，因此其他对远程混合环境结对编程感兴趣的人可以尝试 一起编码。它可用于 IntelliJ、Eclipse、VS Code 和基于它们的 IDE。
参与者通过浏览器加入，但可以通过 IntelliSense、验证、参考搜索、导航等获得类似于 IDE 的完整体验。CodeTogether 简单、快速、免费、匿名且加密。插件/扩展程序位于您期望的正常市场/注册表中，也可以在网站。
全面披露：我为 CodeTogether 的开发者 Genuitec 工作，我们真诚地希望您喜欢它。对 Gitter 或 GitHub 始终受到赞赏。
About 10 years too late for the OP, but this question is still highly ranked in search engines, so others interested in remote mixed environment pair programming can try CodeTogether. It's available for for IntelliJ, Eclipse, VS Code and IDEs based on them.
Participants join in a browser, but get a full IDE-like experience with IntelliSense, validation, reference searches, navigation, etc. CodeTogether is simple, fast, free, anonymous, and encrypted. The plugins/extensions are in the normal marketplaces/registries you'd expect and are also available on the website.
Full disclosure: I work for Genuitec, the makers of CodeTogether, and we really hope you enjoy it. Any constructive feedback on Gitter or GitHub is always appreciated.
我还没有在多 IDE 环境中这样做过。但在我看来，结对无疑是学习 IDE 功能的最佳方式。因此，您应该快速熟悉 Eclipse，同样，您的同事也应该很快掌握 IntelliJ。你们俩都将更加熟悉这两种环境 - 如果您选择这样做，那么这是选择团队 IDE 的好位置。
与其他学习方式相比，结对学习对您（或您的搭档，他们可能有类似的需求）有用的功能。你几乎是通过潜移默化来学习的；当你的搭档使用某个功能时，你可能会问自己：“你是怎么做到的？”或“你刚刚做了什么？”这是在您需要时教您所需的功能。
根据您的情况，可能还有额外的价值：您可能会发现自己需要 IDE 提供的功能；您的搭档可能从未遇到过它（但也可能在 Eclipse 中遇到过）。因此，您花了一分钟时间跟踪该功能，现在你们俩都已经了解了 IDE 的新（且有用）功能。
I have not done this in a multi-IDE environment. But pairing is, to my mind, far and away the best way to learn IDE features. So you should come up to speed quickly on Eclipse, and your colleagues, likewise, should get a handle on IntelliJ in short order. Both of you will become better versed in both environments - and that's a good position from which to settle on a team IDE, should you choose to do so.
By comparison with other means of learning, pairing teaches you the features that are useful to you (or your pair, who probably has a similar set of needs). You learn almost by osmosis; as your pair uses a feature you may find yourself asking, "how did you do that?" or "what did you just do?" This is teaching you the features you need, exactly when you need them.
In your situation, there may be additional value: you may find yourself wanting a feature that your IDE offers; your pair may never have encountered it (but it might be in Eclipse, too). So you spend a minute tracking down that feature, and now both of you have learned new (and useful) functionality of the IDE.
标准化您的环境！尽管您需要通用的源代码样式，但我认为您还需要通用的工作方式，包括拥有通用的 IDE。各种设置、知识、插件等都更容易分享，包括你关于结对编程的例子。
Standardize your environment! As much as you need a common source style, I would argue you also need a common way of working, including having a common IDE. All kinds of settings, knowledge, plugins, etc. is much easier to share, including your example about pair programming.
在结对编程中，结对应该在 IDE 上进行标准化。
我的建议是要么与另一个 IntelliJ 用户结对，要么如果小组中的其他人都在使用 Eclipse，则开始学习 Eclipse。
为了提高结对编程的效率，您将花费太多时间在 IDE 之间切换。
In pair programming, the pair should standardize on an IDE.
My suggestion would be either to pair with another IntelliJ user or, if the rest of the group is on Eclipse, start learning Eclipse.
You're going to lose too much time switching between IDEs to gain the efficiencies of pair programming.
您可以将两个 IDE 都加载到配对计算机上，并根据需要在它们之间切换，但我建议您与配对伙伴一起标准化 IDE。您可能想在下一次回顾中提出这个问题，看看团队的共识是什么。
You could have both IDEs loaded on the pairing machine and switch between them as needed, but I'd recommend standardizing IDEs with your pairing partner. You might want to bring this question up in your next retrospective and see what the team consensus is.