| Tags | close_on_peer_reviews skill/tilde |
The review column causes a lot of confusion for a lot of people. A lot of students do weird things and end up getting bad reviews.
People mess this one up all the time. Focus
Only put your card into the Review column when your main branch is complete. Your main branch needs to hit all the requirements set out in the project brief. If you still have Pull Requests that need to be merged then get those merged before moving forward.
The main branch needs to be complete and demonstrate that you are at least competent.
If you put your repo card into the review column then you are saying “I believe my main branch meets 100% of the project requirements”
This one is simpler. You need to hit these requirements before requesting a review:
You can move topics once you have:
As you progress in your course you’ll start seeing other cards showing up in your review column, cards that look a little weird and link to other people’s work. When that happens then you need to look at the person’s work and add a review.
That’s right! You’ll be reviewing your peers! And they will be reviewing you :)
What you need to do when you review someone else’s work is:
The review form explains itself. There is some help text that should make sense. One cool thing worth noting is that the review comments accept markdown text so you can add formatting and bullet points and that sort of thing.
If you owe reviews to your peers then that is more important than moving your own cards. Be a team player.
When a person lands a new job and they manage to survive the first 3 months then they tend to keep the job. When reviewing projects imagine that you are the person’s boss - imagine paying for the work, what kind of quality would you expect?
One of the main reasons we review each other is so that we can teach each other. Be informative and supportive.
Of course one of the best ways to learn is to teach. While reviewing other people’s work you will be forced to think about skills you might have already demonstrated. While reviewing people’s work try to recall things that you have done in the past that demonstrate similar skills.
Think about how your peer implemented the project, compare that to your own approach. Think about the tradeoffs. Be curious.
We wouldn’t ask you to review other people’s work if it wasn’t good for you :)
If there are 5 things wrong with a project submission then explain all 5. Make sure you give your peer enough information so that they can sort out everything as quickly as possible.
Set your peers up for success and efficiency!
Visit your review performance page on Tilde often. You’ll be able to see if you are doing a high quality work.
If you are bad at review, you’re probably going to be bad at working on teams. This will severely limit your career growth.
You probably wont do a great job of project review at first, but it is a skill you can get better at.
There are 2 positive statuses (Competent and Excellent) and 2 negative statuses (Not Yet Competent and Red Flag).
The best thing is to aim to review people who haven’t had feedback yet. Look for cards where there are the fewest smiley faces and review those first.
By taking part in this review process you get to:
You need to aim to be fast and accurate with your reviews.
In terms of accuracy, if you mark something as Competent and then a staff member marks it as Not Yet Competent then that tells us that you don’t know what competence looks like. Which means you have gaps in your knowledge.
We don’t expect you to be perfect all the time. But we do expect you to keep an eye on the cards you’ve reviewed. If a staff member disagrees with your review you need to look at it and figure out why they disagree with you. Then the next time you review someone’s work you need to try to use your new knowledge.
By reviewing code and stating your opinion you will constantly test and upgrade your skills.
You need to demonstrate your understanding of how the review column works before putting this project card into the review column.
FIRST the below project card should be marked competent:
Tilde project tutorial: How to submit a link
For coders the below project also needs to be in the complete column
Tilde project tutorial: How Repo projects work
If the relevant project card(s) aren’t complete, you will be red-flagged for this project card if you move it to the review column. Instructions must be followed.
On Tilde you will notice that this card is asking for a link submission. Please don’t worry about submitting a link
Please follow the following instructions to submit your work:
TOPIC: How to submit your markdown files