可用于团队项目中远程工作的约定
在团队项目中进行远程工作（例如通过 CVS 或 SVN）时，您会建议采用什么样的约定？更具体地说，可以采取什么措施来避免某人进行可能是必要的大规模更改，并冒着混淆/延误其他团队成员的风险？如果需要进行测试，那么应该如何进行测试，以便代码不会受到在应用程序投入生产之前需要清除的指令的污染？我对与方法论有关的任何事情感兴趣，但也对任何可以增强沟通的小技巧感兴趣，例如在源代码中留下 TODO 注释。
What sort of conventions would you advise when doing some distance work (say through CVS or SVN) on a team project? More specifically, what can be done to avoid someone doing widescale changes, which might be necessary, and running the risk of confusing/delaying other team members? If testing is necessary, how should it be carried out so code isn't polluted with instructions that will need to be cleared out before the application is to go into production? I'm interested in anything that has to do with methodology but also any small tips that could enhance communication such as leaving TODO comments in the source code.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
沟通比约定更重要。我的团队分为两部分，一半在欧洲，一半在美国，我们的成功来自于清晰、定期的沟通：
关键在于，仪式性沟通建立了定期沟通的基本习惯，并使每个人保持同步。这些强制性内容让每个人在每次处理其他人可能需要知道的事情时都能轻松地拿起电话或与同事联系。
另外，请不要在源代码中留下 TODO 注释。抛出 UnsupportedOperationException/NotImplementedException 直到您准备好实现，然后完全实现它。
*正确并不意味着完美。总有更好的设计、更好的编码方式，持续的沟通有助于持续的反馈。
Communication is more key than convention. My team is split, half in Europe and half in the US, and our success comes from clear, regular communication:
The point is that ritual communication establishes a baseline habit of regular communication and that keeps everyone in sync. The mandatory bits make everyone comfortable enough to pick up the phone or approach a colleague every time they work on something the other might need to know.
Also, please don't leave TODO comments in source code. Throw a UnsupportedOperationException/NotImplementedException until you're ready to implement, and then implement it fully.
*Right doesn't mean perfect. There's always a better design, better way to code something, and continuous communication facilitates continuous feedback.