Code Reviews For Offshore and Temporary Developers

We recently added offshore resources and are having difficulty with a successful strategy for basic reviews. Previously, a developer could capture another developer and go, although there he is changing, taking notes on the issues raised. The original developer would repeat the reactor. With our offshore partners, we find that a painstaking process makes for the time zone and language problems. With reviews taking longer and more controversial.

Has anyone created a really successful strategy for checking code with offshore teams in an inflexible environment.

+3
source share
3 answers

, , , , , , , , . Timezone , , .

, . , , .

+1
+1

, , GitHub , .

0

Source: https://habr.com/ru/post/1734468/


All Articles