Top-Down Code reviews

Top-Down Code Review

During a top-down code review, the reviewer begins by looking at the high-level artifacts of the system, such as ticket description, architecture diagrams or documentation. Then, they progressively drill down into more detailed aspects of the code.

Most developers nowadays start with a top-down approach, by first reading the code review description (aka. the pull request summary), or the related ticket or user story, before they start to examine the code.

This article covers the following:

Are you ready to learn more? Then sign-up, or log-in: It’s free.

This article first appeared on Last updated: January 30, 2024

Profile picture of Michaela Greiler

Written by Dr. Michaela Greiler who is obsessed with making code reviews your superpower. Learn more about her workshops.