Software Engineering · Code Quality
A structured process where one or more teammates read proposed changes before they merge, checking for bugs, design problems, and maintainability issues.
In practice: The most valuable code reviews surface design concerns, not style nits — if style issues are taking up review bandwidth, that's a signal to automate them with a linter and formatter instead.