I worked on a team like this: 2 in Europe, 1 West Coast US, 2 in Australia. We did post-merge code reviews, otherwise we'd go back-and-forth over DAYS trying to

I worked on a team like this: 2 in Europe, 1 West Coast US, 2 in Australia. We did post-merge code reviews, otherwise we'd go back-and-forth over DAYS trying to merge a single PR. So, write your code with tests and deploy to production; monitor for errors. During post-merge review, if you saw a bug, create a fix + tests PR, tag the author and merge the fix. Generally, these would be 'subtle bugs' or bugs that weren't hit with the current production traffic. If you saw a better approach, create a PR with your suggestion and we'd do the whole back-and-forth thing -- but the feature was deployed, so we could sit back and bike-shed the approaches for days. I loved it. The turn-around time from feature ideation to launch was very low. There was no 'authority' in reviews, it was 'our code' and we're always trying to make it better.