What Code Reviews Taught Me Over Time
SMRTR summary
After reviewing roughly 100 pull requests, clear patterns emerged — most of them not about code quality, but about process and communication. Key lessons include enforcing PR description templates, capping PR size at ~200 lines, and scrutinizing AI-generated code for fake imports, stale patterns, empty catch blocks, and tests that prove nothing. Asking questions instead of giving orders makes reviews faster and kinder.
SMRTR provides this summary for quick context. The original article belongs to GitConnected.
Read the original article