The Code Expert Documentation for Teaching
This documentation was adapted from Vytautas Astrauskas Feedback Guidelines.
This Feedback Guidelines are suggestions from our side how to provide feedback. You should always ask your lecturers or head TA about the guidelines for your course.
Grading should not start before the deadline is over. You should decide and communicate how late submissions are handled.
For coding tasks, the autograder should be the king. This means:
In these two cases, you should also inform the head TA with the description of the situation and ask the head TA or the lecturers whether we should accept such a solution. If the answer is that the solution in question is not acceptable, please set the score to 0.
Note: it is important to always inform about the cases in which you are planning to decrease the score such that the student loses XP to ensure that all teaching assistants grade in the same way.
For free text tasks the following grading scheme is suggested:
Students will earn XP if they get at least 1 point. The head TA should provide the TAs with a more concrete grading scheme.
In the Ready to review tab, you will see the exercises ready for review. The tasks that still have some unreviewed submissions have a red counter next to the Review button:
Click on the Review button to start reviewing the task. This will open the IDE with a panel on the left that allows choosing the student submission to review (click on the image to see the explanations):
Enter the feedback for the student in the Feedback for … box:
Please use Markdown formatting when providing feedback. You can find a Markdown reference here: https://commonmark.org/help/. You can also write code and math see here. To see how the feedback will be displayed to the student, click on Preview.
For the free text exercises set the score by using the slider:
The pass marks the score that awards experience points.
Note: This section is based on this handout. The purpose of feedback is to communicate to students:
Provide a comment on the autograder result:
If the submission was correct, but you nevertheless think that the submission has critical issues not related to functional correctness, point out to the student:
If student’s code is hard to read, point them to your style guide.
If the student’s submission has many issues, point out the most important ones, so that the student can focus on these. However, do not forget to mention that you are describing only the most important issues, so that the student does not assume that these are the only issues.