Learn code review culture vocabulary: blameless reviews, commenting on code not people, review SLAs, async best practices, and sprint blocking language.
0 / 18 completed
1 / 18
What does 'blameless review culture' mean in a code review context?
Blameless review culture means feedback is directed at the code, design decisions, or system — never at the person. It creates psychological safety, encourages learning, and keeps reviews productive rather than defensive.
2 / 18
A team norm says 'we comment on code, not people'. What does this mean in practice?
'Comment on code, not people' means using impersonal, constructive language: 'This approach could lead to a race condition' instead of 'You introduced a race condition'. It keeps reviews collaborative and psychologically safe.
3 / 18
What is a 'review SLA' in an engineering team's process?
A review SLA (e.g. 'first review within 1 business day') prevents PRs from sitting idle for days. It sets expectations for both authors (don't expect instant review) and reviewers (don't let PRs languish).
4 / 18
A developer writes in Slack: 'This review is blocking the sprint.' What are they communicating?
'Review is blocking the sprint' is an escalation signal: a pending review is on the critical path for a sprint commitment. It's a request for urgent reviewer attention, not a complaint about the review process.
5 / 18
What are 'asynchronous review best practices' in a remote or distributed team?
Async review best practices mean writing comments that are self-explanatory — including context, reasoning, and a suggested alternative — so the author can respond and iterate without needing a call, enabling reviews to progress across time zones.
6 / 18
Sarah is reviewing John's pull request for a new user authentication module. John writes in the PR description: 'Fixed a critical bug – this was a nightmare to track down!' Mark responds on Slack: 'Great catch, John! Glad you found it.'
Which of the following best describes Mark's comment?
This scenario highlights the importance of constructive feedback in a code review culture. While Mark's comment acknowledges John's effort, it still focuses on the *process* (the 'nightmare') rather than solely celebrating the positive outcome – fixing the bug. A truly supportive environment would acknowledge the accomplishment without dwelling on potentially negative or self-deprecating language. The incorrect options all introduce unnecessary criticism or pressure.
7 / 18
Mark's comment, 'Great catch, John! Glad you found it,' in response to John's PR description about a critical bug, demonstrates which of the following aspects of code review culture? Consider the context of a team striving for a positive and supportive environment.
Mark's comment is an example of positive reinforcement. While it *could* be interpreted negatively if taken out of context (option 4), the phrasing 'Great catch' and 'Glad you found it' directly acknowledges John's successful resolution. It's important to avoid over-praising, however; a more detailed response acknowledging the bug's potential impact would have been even better, demonstrating a focus on quality alongside encouragement. The core of this scenario is validating effort within a constructive review process.
8 / 18
Sarah is reviewing John's pull request for a new user authentication module. John writes in the PR description: 'Fixed a critical bug – this was a nightmare to track down!' Mark responds on Slack: 'Great catch, John! Glad you found it.'
Which of the following best describes Mark's comment?
This scenario highlights the importance of constructive feedback in a code review culture. While Mark's comment acknowledges John's effort, it still focuses on the *process* (the 'nightmare') rather than solely celebrating the positive outcome – fixing the bug. A truly supportive environment would acknowledge the accomplishment without dwelling on potentially negative or self-deprecating language. The incorrect options all introduce unnecessary criticism or pressure.
9 / 18
Mark's comment, 'Great catch, John! Glad you found it,' in response to John's PR description about a critical bug, demonstrates which of the following aspects of code review culture? Consider the context of a team striving for a positive and supportive environment.
Mark's comment is an example of positive reinforcement. While it *could* be interpreted negatively if taken out of context (option 4), the phrasing 'Great catch' and 'Glad you found it' directly acknowledges John's successful resolution. It's important to avoid over-praising, however; a more detailed response acknowledging the bug's potential impact would have been even better, demonstrating a focus on quality alongside encouragement. The core of this scenario is validating effort within a constructive review process.
10 / 18
Sarah is reviewing John's pull request for a new user authentication module. John writes in the PR description: 'Fixed a critical bug – this was a nightmare to track down!' Mark responds on Slack: 'Great catch, John! Glad you found it.'
Which of the following best describes Mark's comment?
This scenario highlights the importance of constructive feedback in a code review culture. While Mark's comment acknowledges John's effort, it still focuses on the *process* (the 'nightmare') rather than solely celebrating the positive outcome – fixing the bug. A truly supportive environment would acknowledge the accomplishment without dwelling on potentially negative or self-deprecating language. The incorrect options all introduce unnecessary criticism or pressure.
11 / 18
Mark's comment, 'Great catch, John! Glad you found it,' in response to John's PR description about a critical bug, demonstrates which of the following aspects of code review culture? Consider the context of a team striving for a positive and supportive environment.
Mark's comment is an example of positive reinforcement. While it *could* be interpreted negatively if taken out of context (option 4), the phrasing 'Great catch' and 'Glad you found it' directly acknowledges John's successful resolution. It's important to avoid over-praising, however; a more detailed response acknowledging the bug's potential impact would have been even better, demonstrating a focus on quality alongside encouragement. The core of this scenario is validating effort within a constructive review process.
12 / 18
Sarah is reviewing John's pull request for a new user authentication module. John writes in the PR description: 'Fixed a critical bug – this was a nightmare to track down!' Mark responds on Slack: 'Great catch, John! Glad you found it.'
Which of the following best describes Mark's comment?
This scenario highlights the importance of constructive feedback in a code review culture. While Mark's comment acknowledges John's effort, it still focuses on the *process* (the 'nightmare') rather than solely celebrating the positive outcome – fixing the bug. A truly supportive environment would acknowledge the accomplishment without dwelling on potentially negative or self-deprecating language. The incorrect options all introduce unnecessary criticism or pressure.
13 / 18
Mark's comment, 'Great catch, John! Glad you found it,' in response to John's PR description about a critical bug, demonstrates which of the following aspects of code review culture? Consider the context of a team striving for a positive and supportive environment.
Mark's comment is an example of positive reinforcement. While it *could* be interpreted negatively if taken out of context (option 4), the phrasing 'Great catch' and 'Glad you found it' directly acknowledges John's successful resolution. It's important to avoid over-praising, however; a more detailed response acknowledging the bug's potential impact would have been even better, demonstrating a focus on quality alongside encouragement. The core of this scenario is validating effort within a constructive review process.
14 / 18
During a code review of a new API endpoint, Alice writes in the PR description: 'This endpoint now handles rate limiting. We've implemented a sliding window algorithm to prevent abuse.' Bob replies on Slack with 'Cool, thanks for the proactive work!' What does Bob's comment primarily demonstrate regarding code review culture?
Bob's comment highlights the importance of recognizing and appreciating proactive work in code reviews. It demonstrates an understanding that a good review isn't just about finding bugs, but also acknowledging improvements and thoughtful design choices. The other options focus on misunderstandings or lack of appreciation, not the core aspect of acknowledging positive contributions.
15 / 18
The team has a policy that all pull requests must include a 'code review readiness' checklist. John submits a PR with only comments on the code itself and no mention of testing or documentation. His reviewer, Sarah, points out this omission. What is Sarah primarily addressing?
Sarah is raising a concern about the completeness of the code review. While adherence to guidelines is important, her focus is on ensuring that all aspects – testing and documentation – are considered during the review process. This aligns with a more holistic approach to quality assurance, preventing issues later in the development lifecycle.
16 / 18
During a standup meeting, David says, 'I'm working on refactoring the user authentication module. I've identified several areas for improvement related to security and performance.' His team lead, Emily, asks, 'Can you share your findings with the team during the next code review?' What is Emily primarily requesting?
Emily is asking David to proactively share his findings and plans within the context of the upcoming code review. This promotes transparency, collaboration, and ensures that the team can contribute meaningfully before the actual implementation. It's a key element of knowledge sharing in a development environment.
17 / 18
A developer, Liam, receives a Slack message from his team lead, Chloe: 'This PR is blocking the sprint. Please prioritize addressing the critical security vulnerability before proceeding.' What does Chloe's message indicate regarding the code review process?
Chloe's message highlights the importance of prioritizing issues identified during code review. Specifically, a critical security vulnerability represents a high-priority issue that demands immediate attention, impacting the team's progress and potentially introducing significant risks. This demonstrates a focus on risk mitigation.
18 / 18
During a code review of a new feature, Mark comments: 'This solution is elegant and efficient.' What aspect of the code review culture does this comment primarily represent?
Mark's comment showcases an appreciation for good design principles – elegance and efficiency. While technical correctness is essential, recognizing well-crafted solutions demonstrates a broader understanding of quality that goes beyond simply fixing bugs. It reflects a positive feedback loop encouraging effective coding practices.
What does the "Code Review Culture Vocabulary Quiz" exercise practise?
Learn code review culture vocabulary: blameless reviews, commenting on code not people, review SLAs, async best practices, and sprint blocking language.
How many questions are in this exercise?
This exercise has 18 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 Culture Vocabulary Quiz" 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.