it's often a good opportunity to point out things that aren't clear when first seeing the new code. Like: * naming this variable `accumulator` instead of `x`

it's often a good opportunity to point out things that aren't clear when first seeing the new code. Like: * naming this variable `accumulator` instead of `x` more clearly communicates intentn * add a quick comment explaining the reason this workaround exists etc. A major focus of code review for me is the changes are maintainable in the sense that they empower people to make changes in the future effectively. I can agree with the post though that correctness and security are more important technically.