专业人士和学生的项目组织
我正在作为一名博士生,开发科学/工程模拟和在这些模拟中进行测试的算法。这些天,第一个学生开始从事我的项目(他的学士论文),我想知道:我现在应该如何组织该项目?
我认为我有一些很好的 C++ 知识(尽管我仍然想每天提高),并且代码包含一些设计模式、大量模板化类等。这些技术对学生来说是新的,我想知道让他来是不是一个好主意直接在项目的主干中工作。
如果编程新手和更有经验的程序员混在一起,你有没有经历过会发生什么?代码会变得混乱吗?还是新手可以通过这个学到更多东西?为学生建立一个分支来测试他的算法并稍后将它们合并到主干中是否明智?我应该先给他一本《实用程序员》之类的书来读吗(更好的建议?)?
I am working as a PhD student developing scientific/engineering simulations and algorithms to be tested in these simulations. These days the first student started to work on my project (for his Bachelor thesis) and I am wondering: how should I organize the project now?
I think I have some good C++ knowledge (although I still want to improve every day) and the code contains some design patterns, lots of templated classes etc. These techniques are new to the student and I wonder if it's a good idea to have him work directly in the trunk of the project.
Do you have any experiences what happens if programming newbies and more experienced programmers are mixed? Does the code get messed up or do the newbies learn more by this? Is it wise to have a branch for the student to test his algorithms and maybe merge them into the trunk later? Should I first give him a book like The Pragmatic Programmer for reading (better suggestions?)?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
持续的代码审查是 a) 提高提交代码的质量和 b) 帮助新程序员加快速度、集成和快速学习的绝佳方法。
我们使用代码审查,它确实在很多方面都有帮助。
编辑:代码审查的另一个优点是,它让人们有机会描述为什么他们这样做——代码审查是一个双向过程,双方都可以从中受益。请记住,仅仅因为他们是新的,并不意味着他们没有东西可以教你。
只要学生们明白代码审查是一种被广泛接受的行业实践,并且有大量的研究支持它,它并不是为了照顾新手,而且即使是经验丰富的程序员也会使用代码审查,那么它应该会取得很好的效果。
如果有帮助,请让他们参加更有经验的程序员的代码审查。
Constant code reviews are an excellent way of a) improving the quality of committed code and b) helping the newer programmers get up to speed, integrate and rapidly learn.
We use code reviews and it really does help in so many ways.
Edit: Another advantage of code reviews is that it gives people a chance to describe why they did something the way they did - code reviews are a two-way process, and both parties can benefit from them. Remember, jsut because they're new, doesn't mean they don't have something to teach you.
So long as the students understand that code reviews are a well-accepted industry practice with no small amount of research backing it up, that it isn't intended to babysit newcomers, and that even experienced programmers use code reviews, it should work out fine.
If it helps, have them take part code reviews of more experienced programmers.