Code Review English: Giving and Receiving Feedback Professionally
5 exercises — requesting changes diplomatically, explaining why a change is needed, acknowledging good code, asking clarifying questions, and responding to review comments professionally.
0 / 10 completed
1 / 10
You are reviewing a PR and need to request a change to how errors are handled. Which comment is MOST constructive?
Requesting changes diplomatically: Use 'Consider...' or 'What do you think about...' rather than directives. Explain the specific problem (silent error swallowing), the consequence (caller doesn't know), and suggest a concrete solution (code example). Option B does all three. This is the 'Conventional Comments' approach widely used in professional code review.
2 / 10
You need to explain WHY a specific change is needed in a code review. Which explanation is BEST?
Explaining the 'why' behind a requested change dramatically improves the quality of code review. Option B gives the specific reason (12 references = single source of truth), the maintainability benefit (one-line future change), and the risk avoided (inconsistency from multi-place edits). This helps the author understand the principle, not just make the mechanical change.
3 / 10
You want to acknowledge good work in a code review. Which comment is MOST specific and useful?
Acknowledging good code: Specific positive feedback ('using a generator function to lazily evaluate') is more valuable than generic praise ('LGTM', 'good job'). Naming what is good and why it is good reinforces the pattern, helps the author know what to replicate, and creates a learning culture. LGTM is fine for routine approvals but misses a teaching opportunity.
4 / 10
You don't understand why a particular design decision was made in a PR. Which clarifying question is MOST professional?
Clarifying questions in code review: Frame questions as genuine curiosity rather than implicit criticism. Acknowledge the possible reason ('was there a specific constraint') and leave room for the decision to be correct ('or is this worth revisiting'). Option B is collaborative and non-confrontational. Option D is too blunt; Option A sounds accusatory.
5 / 10
A reviewer has left a comment suggesting you use a different data structure. You disagree but want to respond professionally. Which response is BEST?
Responding to review comments professionally: Acknowledge the suggestion, explain your reasoning with specifics, and leave the door open to being wrong ('I'm open to switching'). Option B demonstrates that you considered the alternative, gives a clear technical reason for your choice, and invites further discussion. This is collaborative disagreement — the hallmark of a strong engineering culture.
6 / 10
Sarah is reviewing a pull request for a new user authentication module. She notices the code doesn't include any input validation. Which of the following comments would be MOST helpful to David, the developer who wrote the code?
This question tests giving feedback about security risks. Option 2 is the most constructive because it directly addresses a potential vulnerability with a specific suggestion for improvement. Options 1 and 3 are irrelevant to the situation; option 4 asks for clarification instead of offering guidance. Focusing on security concerns is key in code reviews.
7 / 10
Mark has just received a Slack message from Emily regarding his recent pull request for the payment processing service. She writes: 'Just wanted to say this looks great! 👍'. Which response is BEST in replying to her?
This assesses acknowledging positive feedback appropriately. Option 0 is a simple and polite acknowledgment of Emily's comment. Options 1 and 2 are overly critical or detailed for an initial response; option 3 shifts the conversation to a different topic without acknowledging her praise.
8 / 10
John is presenting his code review findings in a pull request description. He needs to explain why he suggests refactoring a complex function into smaller, more manageable components. Which sentence BEST captures the essence of this feedback?
This tests explaining the *why* behind feedback. Option 1 provides a clear rationale for the refactoring – focusing on readability and maintainability— which is professional and constructive. Options 2 and 4 are simply stating opinions or suggesting something without justification, while option 3 is dismissive.
9 / 10
Lisa is reviewing a PR that uses a different data structure than previously agreed upon. She believes it introduces unnecessary complexity. What's the MOST professional way to express her disagreement?
This focuses on respectfully disagreeing while seeking understanding. Option 1 is confrontational and unproductive; option 2 politely asks for the reasoning behind the change, allowing for discussion and potentially revealing valid reasons. Options 3 and 4 avoid addressing the issue altogether.
10 / 10
Tom receives a comment in a code review stating: 'Consider using a queue for handling asynchronous tasks.' He believes a simple thread is sufficient. Which question is MOST appropriate to ask to clarify the reviewer's suggestion?
This assesses seeking clarification on technical suggestions. Option 1 directly probes for the rationale behind the suggestion – understanding the problem that a queue is intended to solve. Option 2 asks for context and justification for the recommendation, while options 3 and 4 are premature assumptions or irrelevant questions.
What will I practise in "Code Review English: Giving and Receiving Feedback Professionally"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.