Clean Code and Code Review Basics
Readable code lowers onboarding time and production risk.
Clean code basics
- Small focused functions
- Clear naming
- Single-responsibility modules
- Avoid deep nesting and hidden side effects
- Keep business rules explicit
Pull request checklist
- Does the change solve the right problem?
- Are edge cases covered?
- Are tests updated?
- Is the code understandable after six months?
- Are logs and error paths sufficient?