🔀Code Review
Also known as Peer Code Review, PR Review
Your team reads your changes before they go in. They catch bugs and share ideas.
Think of it like
Think of it like asking a friend to read your story before you hand it in. They spot what you missed.
Example
Jack reviews Emma's change and spots that a price can be negative. She adds a check before it merges.
Why it matters
A second pair of eyes catches bugs the author cannot see. It also spreads knowledge across the team.
Definition
Common mistake
Key takeaways
- 1Before the merge. Problems are cheapest to fix here.
- 2Kind and clear. Comment on the code, not the person.
- 3Learn both ways. Reviewers learn as much as authors.