Thanks for sharing that, Roy.  As Sean admitted, it is a long list of don'ts 
(with justifications for why not to do things) and a nice list of things to do 
that include links to more details.


> On Nov 29, 2016, at 7:35 PM, Roy Tennant <> wrote:
> I happened to run across this very good (and long!) blog post[1] on running
> code reviews for teams that work remotely. I think it has a lot of good
> advice, at least from the perspective of someone who has never done it and
> would want a guide like this to do it well.
> Roy
> [1]

Reply via email to