Code Review Etiquette & Tone
Practise the IT-English phrasing that keeps code review comments constructive: softening, asking questions and praising good work.
0 / 25 completed
1 / 25
Which comment has the most constructive tone?
Framing feedback as a collaborative suggestion ('Could we...') is constructive and non-confrontational.
2 / 25
A reviewer prefixes a comment with 'nit:'. What does that signal?
'nit' marks a small, optional preference that shouldn't block the merge.
3 / 25
Which phrase best 'softens' a critical comment?
Hedging with 'I might be missing context' invites discussion rather than asserting the author is wrong.
4 / 25
Why is it good etiquette to comment on the code, not the person?
Saying 'this function' rather than 'you' keeps the review professional and reduces defensiveness.
5 / 25
Which is an appropriate 'positive' review comment?
Specific praise reinforces good practices and balances the critical feedback.
6 / 25
Alice posted this comment on a PR: 'This function is incredibly inefficient. The loop iterates 10 times unnecessarily. Please refactor.'
Bob responded with: 'I appreciate the feedback, Alice! Could you perhaps suggest a more efficient alternative or point me to relevant optimization techniques?'
Which response demonstrates better code review etiquette and tone?Alice's comment is blunt and immediately critical, which can be perceived as aggressive and discourage collaboration. Bob's response demonstrates a constructive approach by acknowledging the feedback while asking for specific help—this shows respect and encourages a solution-oriented conversation. The key here is moving beyond simply pointing out problems to offering support and guidance, aligning with best practices for code review.
7 / 25
John posted this comment on a PR: 'This code is messy and difficult to understand. It needs significant cleanup.'
Maria responded with: 'Thanks for raising this point, John. I'm happy to discuss the specific areas you found challenging and how we can improve readability going forward.'
Which response demonstrates better code review etiquette and tone?John's initial comment is critical and lacks constructive feedback. While pointing out problems is necessary in a code review, the phrasing 'messy' and 'difficult to understand' can come across as harsh and dismissive. Maria's response, however, acknowledges the issue while inviting a collaborative discussion about specific challenges and potential solutions – this demonstrates respect and a willingness to help, which is crucial for productive code review etiquette. Choosing option 3 correctly identifies that both comments are appropriate in the context of a code review, but Maria's reply is *better* due to its proactive nature.
8 / 25
Sarah posted this PR description:
"I've added the new API endpoint for user authentication. It returns a JWT token upon successful login."
Mark replies with: "Sounds good! Can you include some documentation on how to use the token?"
Which of the following best describes Mark's tone and approach?
Mark's response demonstrates a helpful and collaborative tone. He acknowledges the completion of the task (the API endpoint) but proactively seeks clarification regarding its usage – specifically documentation. This is important for ensuring the code is understood and effectively utilized by others. Option A misinterprets Mark's response as demanding, while options B and D represent unnecessarily negative or unproductive feedback.
9 / 25
David posted this Slack message after receiving feedback on a PR:
'Okay, I've made the changes you suggested. While I don't agree with your assessment of the performance, I appreciate you pointing it out.'
Which of the following best describes David's tone and approach?
David's response demonstrates a lack of open-mindedness and an unwillingness to consider alternative perspectives. While acknowledging receipt of feedback is good, his statement 'While I don't agree with your assessment' immediately positions him as resistant to constructive criticism, which can create friction within the team. The 'appropriate' option misinterprets this behavior; David isn't demonstrating professionalism but rather defensiveness. A better response would involve a more open and collaborative approach.
10 / 25
Reviewer: 'This function could be improved by using a more efficient algorithm.'
Developer: 'I chose this algorithm because it's the simplest to implement and meets the performance requirements outlined in the specifications.'
Which of the following responses from the reviewer is most appropriate in maintaining a productive code review conversation? The key here is to avoid directly dismissing the developer's reasoning. Option 1 is overly prescriptive and potentially confrontational. Option 2 encourages a constructive discussion by seeking clarification on the original requirements. Options 3 and 4 are dismissive and don't invite further dialogue. By requesting details, the reviewer demonstrates respect for the developer's choices while also ensuring alignment with the project goals.
11 / 25
Alice posted this comment on a PR: 'This function is incredibly inefficient. The loop iterates 10 times unnecessarily. Please refactor.'
Bob responded with: 'I appreciate the feedback, Alice! Could you perhaps suggest a more efficient alternative or point me to relevant optimization techniques?'
Which response demonstrates better code review etiquette and tone?Alice's comment is blunt and immediately critical, which can be perceived as aggressive and discourage collaboration. Bob's response demonstrates a constructive approach by acknowledging the feedback while asking for specific help—this shows respect and encourages a solution-oriented conversation. The key here is moving beyond simply pointing out problems to offering support and guidance, aligning with best practices for code review.
12 / 25
John posted this comment on a PR: 'This code is messy and difficult to understand. It needs significant cleanup.'
Maria responded with: 'Thanks for raising this point, John. I'm happy to discuss the specific areas you found challenging and how we can improve readability going forward.'
Which response demonstrates better code review etiquette and tone?John's initial comment is critical and lacks constructive feedback. While pointing out problems is necessary in a code review, the phrasing 'messy' and 'difficult to understand' can come across as harsh and dismissive. Maria's response, however, acknowledges the issue while inviting a collaborative discussion about specific challenges and potential solutions – this demonstrates respect and a willingness to help, which is crucial for productive code review etiquette. Choosing option 3 correctly identifies that both comments are appropriate in the context of a code review, but Maria's reply is *better* due to its proactive nature.
13 / 25
Sarah posted this PR description:
"I've added the new API endpoint for user authentication. It returns a JWT token upon successful login."
Mark replies with: "Sounds good! Can you include some documentation on how to use the token?"
Which of the following best describes Mark's tone and approach?
Mark's response demonstrates a helpful and collaborative tone. He acknowledges the completion of the task (the API endpoint) but proactively seeks clarification regarding its usage – specifically documentation. This is important for ensuring the code is understood and effectively utilized by others. Option A misinterprets Mark's response as demanding, while options B and D represent unnecessarily negative or unproductive feedback.
14 / 25
David posted this Slack message after receiving feedback on a PR:
'Okay, I've made the changes you suggested. While I don't agree with your assessment of the performance, I appreciate you pointing it out.'
Which of the following best describes David's tone and approach?
David's response demonstrates a lack of open-mindedness and an unwillingness to consider alternative perspectives. While acknowledging receipt of feedback is good, his statement 'While I don't agree with your assessment' immediately positions him as resistant to constructive criticism, which can create friction within the team. The 'appropriate' option misinterprets this behavior; David isn't demonstrating professionalism but rather defensiveness. A better response would involve a more open and collaborative approach.
15 / 25
Reviewer: 'This function could be improved by using a more efficient algorithm.'
Developer: 'I chose this algorithm because it's the simplest to implement and meets the performance requirements outlined in the specifications.'
Which of the following responses from the reviewer is most appropriate in maintaining a productive code review conversation? The key here is to avoid directly dismissing the developer's reasoning. Option 1 is overly prescriptive and potentially confrontational. Option 2 encourages a constructive discussion by seeking clarification on the original requirements. Options 3 and 4 are dismissive and don't invite further dialogue. By requesting details, the reviewer demonstrates respect for the developer's choices while also ensuring alignment with the project goals.
16 / 25
Alice posted this comment on a PR: 'This function is incredibly inefficient. The loop iterates 10 times unnecessarily. Please refactor.'
Bob responded with: 'I appreciate the feedback, Alice! Could you perhaps suggest a more efficient alternative or point me to relevant optimization techniques?'
Which response demonstrates better code review etiquette and tone?Alice's comment is blunt and immediately critical, which can be perceived as aggressive and discourage collaboration. Bob's response demonstrates a constructive approach by acknowledging the feedback while asking for specific help—this shows respect and encourages a solution-oriented conversation. The key here is moving beyond simply pointing out problems to offering support and guidance, aligning with best practices for code review.
17 / 25
John posted this comment on a PR: 'This code is messy and difficult to understand. It needs significant cleanup.'
Maria responded with: 'Thanks for raising this point, John. I'm happy to discuss the specific areas you found challenging and how we can improve readability going forward.'
Which response demonstrates better code review etiquette and tone?John's initial comment is critical and lacks constructive feedback. While pointing out problems is necessary in a code review, the phrasing 'messy' and 'difficult to understand' can come across as harsh and dismissive. Maria's response, however, acknowledges the issue while inviting a collaborative discussion about specific challenges and potential solutions – this demonstrates respect and a willingness to help, which is crucial for productive code review etiquette. Choosing option 3 correctly identifies that both comments are appropriate in the context of a code review, but Maria's reply is *better* due to its proactive nature.
18 / 25
Sarah posted this PR description:
"I've added the new API endpoint for user authentication. It returns a JWT token upon successful login."
Mark replies with: "Sounds good! Can you include some documentation on how to use the token?"
Which of the following best describes Mark's tone and approach?
Mark's response demonstrates a helpful and collaborative tone. He acknowledges the completion of the task (the API endpoint) but proactively seeks clarification regarding its usage – specifically documentation. This is important for ensuring the code is understood and effectively utilized by others. Option A misinterprets Mark's response as demanding, while options B and D represent unnecessarily negative or unproductive feedback.
19 / 25
David posted this Slack message after receiving feedback on a PR:
'Okay, I've made the changes you suggested. While I don't agree with your assessment of the performance, I appreciate you pointing it out.'
Which of the following best describes David's tone and approach?
David's response demonstrates a lack of open-mindedness and an unwillingness to consider alternative perspectives. While acknowledging receipt of feedback is good, his statement 'While I don't agree with your assessment' immediately positions him as resistant to constructive criticism, which can create friction within the team. The 'appropriate' option misinterprets this behavior; David isn't demonstrating professionalism but rather defensiveness. A better response would involve a more open and collaborative approach.
20 / 25
Reviewer: 'This function could be improved by using a more efficient algorithm.'
Developer: 'I chose this algorithm because it's the simplest to implement and meets the performance requirements outlined in the specifications.'
Which of the following responses from the reviewer is most appropriate in maintaining a productive code review conversation? The key here is to avoid directly dismissing the developer's reasoning. Option 1 is overly prescriptive and potentially confrontational. Option 2 encourages a constructive discussion by seeking clarification on the original requirements. Options 3 and 4 are dismissive and don't invite further dialogue. By requesting details, the reviewer demonstrates respect for the developer's choices while also ensuring alignment with the project goals.
21 / 25
Alice posted this comment on a PR: 'This function is incredibly inefficient. The loop iterates 10 times unnecessarily. Please refactor.'
Bob responded with: 'I appreciate the feedback, Alice! Could you perhaps suggest a more efficient alternative or point me to relevant optimization techniques?'
Which response demonstrates better code review etiquette and tone?Alice's comment is blunt and immediately critical, which can be perceived as aggressive and discourage collaboration. Bob's response demonstrates a constructive approach by acknowledging the feedback while asking for specific help—this shows respect and encourages a solution-oriented conversation. The key here is moving beyond simply pointing out problems to offering support and guidance, aligning with best practices for code review.
22 / 25
John posted this comment on a PR: 'This code is messy and difficult to understand. It needs significant cleanup.'
Maria responded with: 'Thanks for raising this point, John. I'm happy to discuss the specific areas you found challenging and how we can improve readability going forward.'
Which response demonstrates better code review etiquette and tone?John's initial comment is critical and lacks constructive feedback. While pointing out problems is necessary in a code review, the phrasing 'messy' and 'difficult to understand' can come across as harsh and dismissive. Maria's response, however, acknowledges the issue while inviting a collaborative discussion about specific challenges and potential solutions – this demonstrates respect and a willingness to help, which is crucial for productive code review etiquette. Choosing option 3 correctly identifies that both comments are appropriate in the context of a code review, but Maria's reply is *better* due to its proactive nature.
23 / 25
Sarah posted this PR description:
"I've added the new API endpoint for user authentication. It returns a JWT token upon successful login."
Mark replies with: "Sounds good! Can you include some documentation on how to use the token?"
Which of the following best describes Mark's tone and approach?
Mark's response demonstrates a helpful and collaborative tone. He acknowledges the completion of the task (the API endpoint) but proactively seeks clarification regarding its usage – specifically documentation. This is important for ensuring the code is understood and effectively utilized by others. Option A misinterprets Mark's response as demanding, while options B and D represent unnecessarily negative or unproductive feedback.
24 / 25
David posted this Slack message after receiving feedback on a PR:
'Okay, I've made the changes you suggested. While I don't agree with your assessment of the performance, I appreciate you pointing it out.'
Which of the following best describes David's tone and approach?
David's response demonstrates a lack of open-mindedness and an unwillingness to consider alternative perspectives. While acknowledging receipt of feedback is good, his statement 'While I don't agree with your assessment' immediately positions him as resistant to constructive criticism, which can create friction within the team. The 'appropriate' option misinterprets this behavior; David isn't demonstrating professionalism but rather defensiveness. A better response would involve a more open and collaborative approach.
25 / 25
Reviewer: 'This function could be improved by using a more efficient algorithm.'
Developer: 'I chose this algorithm because it's the simplest to implement and meets the performance requirements outlined in the specifications.'
Which of the following responses from the reviewer is most appropriate in maintaining a productive code review conversation? The key here is to avoid directly dismissing the developer's reasoning. Option 1 is overly prescriptive and potentially confrontational. Option 2 encourages a constructive discussion by seeking clarification on the original requirements. Options 3 and 4 are dismissive and don't invite further dialogue. By requesting details, the reviewer demonstrates respect for the developer's choices while also ensuring alignment with the project goals.
Frequently Asked Questions
What does the "Code Review Etiquette & Tone" exercise practise?
Practise the IT-English phrasing that keeps code review comments constructive: softening, asking questions and praising good work.
How many questions are in this exercise?
This exercise has 25 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Code Review Language category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Code Review Etiquette & Tone" part of a larger series?
Yes — it's one exercise in the Code Review Language category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Code Review Language category page for related exercises, or browse the main Exercises hub for other IT English topics.