code review

A teammate reading a proposed change before it is merged, to understand it, catch mistakes and share knowledge.

In more detail

A good review checks that the change solves the problem and has tests, and keeps feedback specific and respectful. On hosting services such as GitHub it happens on a pull request, where reviewers comment on lines and approve or request changes.

Examples

Review is a weak control on its own under deadline pressure, which is why the course prefers safe defaults and automated gates.
In Terraform: For Terraform the reviewer reads both the code change and the plan it produces, paying most attention to deletions and replacements. Review is also the main defence against an accidental destroy of production. Plans saved as artifacts let the reviewer see exactly what will be applied.
In this course: Automation should check repeatable facts such as formatting, types and tests, leaving people to judge whether the requirement is met, the failure modes are acceptable and the design will be understandable. A good review comment names a risk, points to evidence and gives a concrete next action.

Related terms

Taught in

References

Certification courses