liveBook · Manning

Cross review

As explained in Build High Value Software Systems

A review practice in which someone other than the change's primary author examines the proposed change.

Cross review has someone other than the primary author examine a change. For critical components, an independent reviewer with relevant technical or architectural depth can catch unsafe assumptions and help spread knowledge. section 13.4.2

For a critical-component pull request:

  • Choose a reviewer who is neither the primary author nor the component's original creator. section 13.4.2
  • Ensure at least one reviewer has depth in the technology or the component's architectural context. section 13.4.2
  • Use the review to surface reasoning and build both reviewers' ability to maintain the component. section 13.4.2

How Build High Value Software Systems covers it

How deep it goes
Specifies reviewer independence and expertise, then explains how review transfers knowledge and catches design risks.
Examples
Uses a pull request to a critical component as the setting, with an independent reviewer who has relevant depth.
What it assumes
Requires a reviewer with depth in the technology or the component's architectural context.
What you can do after
Practice cross review by requiring independent, appropriately knowledgeable reviewers for critical-component changes.
How it connects
Connects code review with collective ownership, knowledge transfer, and architectural safety.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.