Test your Code Review knowledge with a free interactive quiz — 28 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What does it mean to "comment on the code, not the person"?
In this round
What does it mean to "comment on the code, not the person"?
What is "rubber-stamping" in the context of code review?
A PR handler receives `req.body.userId` and uses it directly in a SQL query string via concatenation. What should the reviewer flag, and how urgently?
What is "bikeshedding" in a code review?
Why is explaining the reasoning behind a requested change usually more effective than just stating the verdict?
What is the risk of a reviewer treating every comment -- from a security bug to a naming preference -- with the same urgency and tone?
A reviewer writes: "Why would you write it this way? You always do this." What is wrong with this comment?
Why is it a bad idea for ESLint/Prettier-catchable issues (indentation, unused imports) to still be showing up as manual reviewer comments?
A reviewer disagrees with an author's architectural choice but is not fully certain their alternative is better. What is the most constructive way to phrase the comment?
Why does fast review turnaround (e.g. a first pass within a day) matter for team velocity?
A reviewer leaves 30 comments on a PR, all about variable naming and formatting, none about the fact that the new endpoint has no authentication check. What is the core problem with this review?
A PR adds a new database migration that drops a column. What should a reviewer check first?