Writing better code reviews

In a distributed team, like ours, Pull Request reviews are one of the main ways we communicate about code. That makes it crucial they are clear, helpful, respectful, concise and actionable.

This tweet pointed me to https://conventionalcomments.org/ which is an interesting compendium of tips for how to make them so.

I’m not 100% sold of the rigidity it implies (I might have to use the approach for a while to form a stronger opinion), but even ignoring that part, it’s a good resource, so this post is really little more than a bookmark for me. However, as it might be useful to others, I decided to post it here.

Leave a Reply