Presented by Sergey Zhuk (@zhukserega)

October 17, 2019

The larger the pull-request you submit, the longer it will take to review it and the less valuable the review will be. Moreover, to spend several days on feedback, fixes, repeated reviews, approval and merge is laborious and not very pleasant. How to avoid such situations? I will tell you how our team has optimized the process, and:
What review strategies I use today.What kind of changes I never mix in one request.I will share some real examples.

About Sergey
Sergey is a developer interested in asynchronous programming. He has a tech blog, several books about asynchronous PHP and a YouTube channel with ReactPHP screencasts.

Tags: Git,Code,Reviews,Team,Management,Peer,Programming