Code Review¶
Review changes to improve correctness, maintainability, security, shared understanding, and delivery flow.
flowchart LR
J[Junior: review behavior] --> M[Middle: design and risk]
M --> S[Senior: system boundaries]
S --> P[Professional: review systems]
flowchart LR
Context --> Scope --> Correctness --> Design --> Risk --> Tests --> Operability --> Decision
| Level | Guide | You are done when |
|---|---|---|
| Junior | Review one clear change | You can verify intent, behavior, tests, and readability respectfully. |
| Middle | Review design and risk | You can identify boundary, security, and performance consequences. |
| Senior | Review system evolution | You can protect invariants, compatibility, rollout, and operations. |
| Professional | Design review capability | You can improve review quality and flow across an organization. |
Practice rule¶
Review in risk order: understand intent and scope first, then correctness, design, security, performance, tests, and maintainability. Style automation should not consume human attention.