preface

Nowadays, many large companies (Google, Facebook) have used PR to conduct code review for a long time. You may say that it is only for large companies with large numbers of employees, but in fact, small teams are more flexible, and they are more familiar with the code of colleagues around them, and it is easier to put forward targeted suggestions. Codereview is also more difficult for large companies with large projects, many people and different styles

Domestic companies have abandoned the pull request mechanism in pursuit of agile development and fast pace

The basic pace of foreign companies is relatively slow, and they have enough time to review the PR of each children's shoes, raise opinions, and finally merge request

Pain points

With so many people working on a project, how do you do the following?

  1. Code specification, code elegance
  2. Clear logic, strong reusable, no repeated functional code
  3. Have a good command of their own functions and a good understanding of other business modules
  4. The ability to read other people’s code efficiently
  5. High constraint, avoid team members lazy to write some unreadable, unrobust code
  6. Uniform style, looks like one person wrote the code

In fact, the implementation of pull RequsET on code process management within the team can effectively improve the atmosphere, coding, reading, risk control and many other aspects of the whole team in the long term.

steps

1. Submitting PR for large version means submitting code review once every 2 weeks on average, lasting for several days and counting within the scheduling period, and submitting an important version once

2. To submit PR and daily review in the form of small version, maintain a PR record form for all children’s shoes, randomly select a student for PR review at random time every day, and maintain the status on the form

conclusion

Continuous and effective use of PR in the team can develop coding habits, reading ability, business understanding ability, and continuous high-quality output.

A good code management process is an essential way to build a Team that is capable of fighting with less risk output.

Finished, I am Steven, secretly finished writing, continue to move bricks.