Reviewer
A reviewer is a person who examines an artifact, claim, or proposed change against relevant criteria and provides feedback or an assessment.
"Looks Good to Me"
A person who evaluates proposed code changes for correctness, clarity, context, and alignment with applicable criteria.
- How it is used
- Evaluates proposed code changes while setting review tone, controlling progress, and protecting the quality of what passes.
- How deep it goes
- Checks defects, comprehension, context, acceptance criteria, logical flow, and confusing passages through explicit review questions.
- Examples
- Uses pull-request review questions plus contrasting examples of vague and clear, constructive feedback.
- What you can do after
- Evaluate proposed changes, provide constructive feedback, and make responsible approval judgments.
Writing for Developers: Blogs that get read
A person who evaluates a draft and provides feedback about its content, structure, or technical accuracy.
- How it is used
- Uses peer feedback to harden articles, improve technical accuracy, and strengthen reader understanding before publication.
- How deep it goes
- Defines reviewer roles, selection, timing, preparation, scope, and response, but stops short of prescribing a formal review tool or scoring system.
- Examples
- Uses technical and clarity reviewers, tracked edits, early scheduling, scope-setting, and comments about omissions, context, and factual errors.
- What you can do after
- Practice/perform focused reviews by matching reviewers to reader intent, setting boundaries, and turning criticism into revisions or discussion.
Read how Writing for Developers: Blogs that get read explains reviewer →
Authorization in Action
A policy reviewer is a person responsible for examining an authorization policy for correctness, compliance, or approval.
- How it is used
- Applies independent engineering review to authorization policy implementations before deployment.
- How deep it goes
- Defines the reviewer’s accountability and separation from the author, but defers detailed review criteria and procedures.
- Examples
- Uses an engineer reviewing another engineer’s policy implementation within a workflow involving approval, coordination, and auditing.
- What you can do after
- Evaluate authorization policy implementations independently within standard code review and governance workflows.
Related concepts
- feedbackproduces · Feedback is information about an action, system, or outcome that can inform evaluation, decisions, or subsequent behavior.
- CODEOWNERS fileconfigured by · A CODEOWNERS file is a repository configuration file that maps file paths to people or teams responsible for reviewing changes to those paths.
- pull requestuses · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
- reviewer poolpart of · A group of people eligible to review and approve proposed code changes.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.