管理开发人员之间的代码转换
确保新雇用的开发人员快速掌握代码的最佳实践是什么？并确保开发人员继续前进不会阻碍正在进行的发布。
一些入门想法：
文档
使用完善的框架
培训/鼓励指导
通知期合同中的通知期
What are your best practices for making sure newly hired developers quickly get up to speed with the code? And ensuring developers moving on don't set back ongoing releases.
Some ideas to get started:
Documentation
Use well established frameworks
Training / encourage mentoring
Notice period in contract
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
从管理的角度来看，最好的（但似乎很少遵循）做法是在培训计划中留出时间，无论是对于新员工还是需要培训的当前开发人员。天下没有免费的午餐。
从人员的角度来看，我见过的新员工入职的最佳方式是让他们与当前的开发人员结对编程。这是向他们介绍团队的编码标准和实践，同时让他们浏览代码的好方法。
如果您的团队不愿意结对，那么拥有一些当前的图表来了解系统关键部分的结构或关键位如何交互确实很有帮助。根据我的经验，对于中等复杂度的程序（0.5m 行代码），可以通过一些文档（可能是一些实体关系文档片段，也可能是一些捕获高信息的序列图）来理解关键点。级交互）。
从代码的角度来看，这就是代码库中积累的垃圾会反过来咬你一口的地方。最佳实践是在开发时积极重构，并遵循足够的编码指南以使代码看起来一致。作为团队中的新开发人员，走进类似沼泽的代码库可能会相当沮丧。
如果有大量具有相关经验的开发人员，那么使用通用框架会有所帮助。如果您属于 Java 阵营，从这个角度来看，Hibernate 和 Spring 似乎是安全的选择。
如果我必须选择一个，我会选择提供足够的粗略地图的图表，以便新开发人员可以找出他们在哪里，以及他们正在查看的大量代码如何融入更大的图景。
From a management perspective, the best (but seemingly seldom-follow) practice is to allow time in the schedule for training, both for the new employee and for the current developer who'll need to train them. There's no free lunch there.
From a people perspective, the best way I've seen for on-boarding new employees is to have them pair program with current developers. This is a good way to introduce them to the team's coding standards and practices while giving them a tour of the code.
If your team is pairing averse, it really helps to have a few current diagrams for how key parts of the system are structured, or how key bits interact. It's been my experience that for programs of moderate complexity (.5m lines of code), the key points can be gotten across with a few documents (which could be a few entity-relation document fragments, and perhaps a few sequence diagrams that capture high-level interactions).
From the code perspective, here's where letting cruft accumulate in the code base comes back to bite you. The best practice is to refactor aggressively as you develop, and follow enough of a coding guideline that the code looks consistent. As a new developer on a team, walking into a code base that resembles a swamp can be rather demoralizing.
Use of a common framework can help if there's a critical mass of developers who'll have had prior experience. If you're in the Java camp, Hibernate and Spring seem to be safe choices from that perspective.
If I had to pick one, I'd go with diagrams that give enough of a rough map of the territory that a new developer can find out where they are, and how the big of code they're looking at fits into the bigger picture.