Start with the idea
Start with soundness, data loss, and observable behavior before naming cosmetic issues. Explain impact, point to evidence, and offer a smaller safer change instead of rewriting to personal taste.
A review should help the author ship correct, maintainable code. Begin with user-visible behavior, data integrity, security assumptions, and concurrency or memory safety. Then examine API contracts and tests. Style matters when it obscures meaning or violates team conventions, but a naming preference is less urgent than a lost error result. Point to a concrete line, explain the failure scenario, and suggest a smaller change that addresses it. Separate a blocking issue from a suggestion.
Keep learning, for free
The rest of this lesson is waiting for you.
Create a free account to read the complete explanation, see the infographic, explore the code, and try the exercises. All 742 lessons and algorithm steps are included.
No payment details. Your account opens the complete Academy.