Get useful feedback from your peers on how to improve your project and a simple grade denoting how well you did.
Honesty & politeness
This is constructive. Be polite & helpful. And honest.
Enable Issues on your repoYou
Before we start anything, you need to go to your own repository on GitHub.com and enable the Issues tab.
Find a peerYou
Check the assignment requirements to determine how many peers should critique your work.
Ask the peer politely if they’d like to critique your project. If they accept give them the GitHub URL to the assignment for them to review.
Leave your peer alone so they can have time to consider and look at the project and write valuable feedback.
Evaluate the projectPeer
As a peer evaluator, it’s your job to help the other person succeed. You want to give honest, valuable feedback that will enhance and improve the other person’s project.
Write valuable written feedback & helpful criticism to help your peer improve their project.
Some things to consider:
Create an IssuePeer
Create an Issue on the repository of the person whom you’re critiquing—this is where you’ll write the feedback.
Write valuable and constructive feedback about their project. Be specific and polite. Think about how if this was your project what information you’d want.
- Consider sending screenshots
- Don’t forget about the critique sandwich
- Suggest ways to fix the problems
Website URL to repo conversion
- Cut the username
- Remove the starting dot
- Paste the username before the repository name
Fill out the rubricPeer
In the same Issue, or in a comment, copy and paste the rubric and assign grades for the project you just reviewed.
If your assignment has a more specific rubric in the assignment requirements—use that rubric instead of the one below.
The code will turn into a data table on GitHub when it’s previewed or saved.
| | 0 points | 1 points | 2 points | 3 points | | --- | --- | --- | --- | --- | | **Creativeness** | Bland, boring | Fairly generic, but the colours are nice | Good, works very well and is unique enough | Wow! I never would have thought that would work so well! | | **Effectiveness** | I don’t know what this is trying to do | The message isn’t completely clear and it’s difficult to use | It’s obvious and simple to use | The project is super effective and easy to use | | **Quality** | Non-existent | Acceptable quality, more work could be done | Good quality, up to the expectations of the teacher | Stunning quality, this person rocks! | | **Effort** | Zero effort, incomplete | Decent amount of effort | Goodly amount of effort that shows | Amazing, over-the-top amount of effort | | **Code quality** | Barely started | Indentation is barely existent, lots of validation errors, very poor semantics | Decent indentation, just a couple validation errors, decent semantics | Well indented, fully valid, good semantics |
Sum the rubric and put that value at the bottom.
Confirm that you think this is an appropriate grade for the project you just reviewed.
Write valuable written feedback & helpful criticism to help your peer improve their project. The rubric doesn’t help your peer improve, it’s only a mechanism to guide what you’re looking for. The written feedback is what’s important.
Read the feedbackYou
Carefully read over the feedback from your peer and truely consider what they said.
Try not to take the feedback personally; separate your person from your project. They are trying to help your project succeed and improve.
Respond with a commentYou
Ask any questions of your peer, if anything is unclear. Don’t blame them. Don’t write excuses. Remember they’re trying to help you—trying to make your project better.
Write a comment thanking your peer for their feedback.