Review comments that improve code health
Use concise review language for clean-code concerns without blocking on preference.
It works, so why block on structure? Use when the change passes tests but worsens code health. Your line It works now, but this structure makes the next change harder because the policy and side effect change for different reasons. Do not argue aesthetics. Name the future maintenance cost. It ties the review to code health, not taste. Is this comment blocking or a nit? Compare Use blocking comments for code-health risk, not personal polish. I added the abstraction because we will probably need it later. Use when reviewing speculative flexibility. Can we keep the current seam but remove the…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in