As part of our fully remote engineering team we lean heavy on async communication to keep our sprint’s moving across many different timezones.
Our engineering guidelines require each pull request to have the following content:
- A demo loom to showcase the expected outcome and behavior of the code
- A code overview loom to walk through how and why the code was written
- A PR description with text comments to provide any additional context or information
- Clear and descriptive commit messages
Longer pull requests, which we try and avoid, will typically have longer explanations and messages compared to smaller PRs.
Each PR has a maximum of two reviewers to avoid any confusion or fragmented expectations around who needs to sign off on the pull request.
It’s become common practice for loommates to include a gif when they approve each PR to add a little joy and delight to someone’s day.