您使用什么工具在小组中的开发人员之间共享信息? [英] What tools do you use to share information among developers in your group?

问题描述

我们已经进行了辅导，彼此之间共享信息，并定期举行技术会议.但是，我们希望将这些内容写下来，以备将来记录和供新的团队成员使用.目前，我们大约有30位开发人员.

We already have mentoring, share information among each other, and hold regular technical sessions. However, we want these things written down, for the record and for new team members in the future. Right now we're at around 30 developers.

我们正在考虑内部博客和Wiki.

We're thinking about an internal blog and wiki.

虽然最好在公共博客上共享内容(甚至可能有官方的公共开发人员博客)，但现在我们希望将其保留在内部.我们的商店主要进行定制编程，而不是产品，因此那里会有很多专有的客户信息.公共博客的自我审查只会使我们放慢脚步.

While it would be great to share stuff on public blogs (and maybe even have official public developer blogs), for now we want to keep it internal. Our shop does mostly bespoke programming, and not products, so there will be a lot of proprietary customer information there. Self-censorship for a public blog will just slow us down.

Wiki在概念上很不错，但是它们需要更多的组织和编辑，因此我不认为它具有可持续性.

Wikis are nice in concept but they need more organization and editorial, so I'm not convinced that it will be as sustainable.

您的组织如何做到这一点.

How does your organization do it.

推荐答案

好吧，无论您决定使用哪种技术或产品，都不会成为问题.所有在咖啡机上共享不足的知识都需要引起注意.

Well, whatever technology or product you will decide to use, they will not be the problem. All knowledge which is not sufficiently well shared at the coffee machine needs attention.

• 实际编写时的注意事项(例如网络驱动器上的文档，Wiki页面，SharePoint服务器等).
• 注意对其进行分类(通过链接，标签，网页等).
• 请注意保持最新(通过个人按需或计划的工作).

无论您使用什么，都没有任何技术可以帮助您解决此问题.为此，您需要激发团队写下来的东西，先打电话给存储库中的东西，然后打电话给(和打断)一群其他团队成员，并在他们错了的情况下更正错误.

Whatever you use, no technology will help with this. For this you need to motivate the team to write things down, read up things in the repository up first before phoning (and interrupting) a bunch of other team-members, and correct things if they are wrong.

根据我的经验，SharePoint和Wiki的性能大致相同.您需要打败人们使用它，直到他们体验他们想要使用它，因为他们有时会体验到这种类型的信息共享可以节省时间- -他们的时间.

From my experience, SharePoint and Wikis perform about the same. You need to beat people to use it, until they experience that they want to use it, because they will at some point experience that such type of information sharing can save time -- their time.

由于您已经有共享信息的习惯，所以这对您来说并不是一个难题.我建议一个(或几个，少于太多)提供一些(备用)初始结构，然后开始填写.由于不存在完美的分类，因此您不必为此担心太多.

As you have already a habit of sharing information, this may not be so much of a hard problem for you. I'd recommend that one (or a few, better less than too many) provide some (spare) initial structure, and then let the fill-in begin. As no perfect categorization exists, you should not worry too much about it.

这篇关于您使用什么工具在小组中的开发人员之间共享信息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！