When responding to code review comments, simple replies like 'Done' or 'Fixed' are often insufficient. Adding brief context explaining the 'why' or 'how' behind a change helps reviewers verify work without re-examining every line, preserves design reasoning for future reference, captures outcomes from offline discussions, and clarifies which option was chosen when multiple approaches existed. Google's engineering practices guide recommends this habit as a way to improve clarity and create a better historical record.
Sort: