Code review

Effective code review examines behavior, risk, boundaries, tests, maintainability, and operability—not style nitpicks alone. Ask: Does this match requirements? What breaks at scale? Are errors handled? Will the next reader understand it? Use review checklists for security and migrations on risky changes.

Give actionable, kind feedback; distinguish blockers from suggestions. Authors should provide context, screenshots, and test evidence.

On interviews: describe how you review a PR touching auth and database migration differently from a UI tweak.

Common pitfalls: bikeshedding formatting, rubber-stamp reviews, and debating without suggesting concrete fixes.

The trade-off is thorough review latency versus defect escape to production.

Checklist:

• Verify behavior, tests, and rollback plan.
• Check boundaries and error paths.
• Prioritize risk-based depth per change.