How to write a more thoughtful code review

This post introduces communication strategies for code reviews, focusing on the author's responsibility for self-reviews and the reviewer's role in providing constructive feedback. It highlights the 'conventional comments' system as a method to add context and tone to feedback (e.g., 'suggestion (non-blocking)'), differentiating between blocking and non-blocking changes. The post also emphasizes fairness in code reviews, providing 'Dos and Don'ts' for both authors and reviewers, and cautioning against 'should/must' statements that may stem from personal bias rather than objective requirements.