给编程作业评分的良好标准是什么？
我将向一群 3D 动画师教授脚本和工具开发课程。在教他们编码基础知识时，我计划让他们选择一个他们必须经常执行的重复性任务，并让他们迭代开发一个工具来自动化或简化该任务作为一项任务。
我想知道一些可用于对诸如此类的编程作业进行评分的标准？我提出的一些标准是：
它是否有效 - 该工具是否执行其任务，是否在某些情况下中断，等等。
代码清洁度 - 拥有代码是否正确缩进，它们的编码风格是否一致等。
文档 - 函数是否有详细文档记录，是否有任何“聪明”的代码注释，是否注释不足或注释过多，等等。
效率 - 脚本是否经过优化以快速运行，是否对不经常运行的任务进行了大量不必要的优化，等等。（这个我不会放在非常强调，因为这些不是专业开发的工具，通常工具的工作比速度更重要）
还有其他吗？
I'm going to be teaching a scripting and tool development class to a group of 3D animators. In amongst teaching them coding fundamentals, I plan to have them pick a repetitive task they must perform frequently and have them iteratively develop a tool to automate or simplify this task as an assignment.
What I'd like to know are some criteria that can be used for grading programming assignments such as these? Some of the criteria I came up with were:
Does It Work - Does the tool perform it's task, does it break on certain cases, etc.
Code Cleanliness - Has the code been properly indented, is their coding style consistent, etc.
Documentation - Are functions well documented, are any "clever" bits of code commented, is it under-commented or over-commented, etc.
Efficiency - Has the script been optimized to run quickly, has a lot of unnecessary optimization been done on a task that isn't run very often, etc. (This one I'm not going to put to much emphasis on since these aren't professionally developed tools usually the tool working is more important than speed)
Are there any others?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
清晰度。重要的是，他们的代码对于有机会打开该文件的任何有能力的人来说都是可以理解的。
Clarity. It's important that their code be comprehensible to anyone competent who should chance to open the file.
学生进行练习的方式是否表明他们注意到了课堂上所教授的内容？
你的眼光超越“这有效吗”是正确的；寻找一般方法和“工艺”。
您教导测试的重要性吗？寻找测试用例。
如果他们可以自由选择工具，他们的选择是否明智？
（显然没有抄袭）
Does the way the student went about the exercise indicate that they have paid attention to what was taught in class?
You are right to look beyond "does it work"; look for general approach and "craftsmanship".
Do you teach the importance of testing? Look for test cases.
If they had freedom to choose their tools, did they choose wisely?
(no plagarism, obviously)
是否记录了不变量？有单元测试吗？
整个脚本是否被分成模块或其他大小合适的单元？
（无法分解超过 100 行的代码是新手程序员的一大烦恼。）
Are the invariants documented? Are there any unit tests?
Is the entire script broken up into modules or other units of about the right size?
(The inability to break up codes of over 100 lines is a bugbear of beginning programmers.)
告诉他们它将如何在文件位置等方面工作。提供一组数据供他们测试，另一组数据用于测试他们的解决方案。
Tell Them how it is going to work in terms of file locations etc. Provide one set of data for Them to test ón and another for testing their solutions.