Best Practices
Best Practices
Do
- Review in small batches (200-400 lines ideal)
- Focus on logic, not style (use linters)
- Ask questions rather than demand changes
- Acknowledge good code
- Provide specific, actionable feedback
- Test the changes locally when possible
Don't
- Nitpick style issues
- Rewrite author's code in comments
- Leave vague feedback ("this is wrong")
- Review when fatigued
- Approve without understanding
- Block for preferences, not issues