code-review-excellence

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement. Goals of Code Review: Not the Goals: Good Feedback is: What to Review: What Not to Review Manually: Instead of stating problems, ask questions to encourage thinking: - Reviewing pull requests and code changes - Establishing code review standards for teams - Mentoring junior developers through reviews - Conducting architecture reviews - Creating review checklists and guidelines - Improving team collaboration - Reducing code review cycle time - Maintaining code quality standards - Catch bugs and edge cases - Ensure code maintainability - Share knowledge across team - Enforce coding standards - Improve design and architecture - Build team culture - Show off knowledge - Nitpick formatting (use linters) - Block progress unnecessarily - Rewrite to your preference - Specific and actionable - Educational, not judgmental - Focused on the code, not the person - Balanced (praise good work too) - Prioritized (critical vs nice-to-have) - Logic correctness and edge cases - Security vulnerabilities - Performance implications - Test coverage and quality - Error handling - Documentation and comments - API design and naming - Architectural fit - Code formatting (use Prettier, Black, etc.) - Import organization - Linting violations - Simple typos -...