Reading the fourth chapter of the Law of construction

The fourth chapter is about cooperation between two people. Software engineering is a process that requires individual and team effort, individual impact teams, and team impact individuals. So two people are the most basic team work.

Code normalization, Code style normalization, code design normalization, code review is to make the code easily understood by the partner to improve cooperation efficiency. This feeling is very necessary because we have to understand each other's ideas, and the code responds to that. On the one hand is to standardize our own writing code format and style, on the other hand can also allow others to cooperate with us better.

Pair programming can effectively improve the efficiency of project programming, but this requires the result of running-in, I think the cooperation requires communication. From the beginning of the two people to cooperate, to a whole team work, need time, need more cooperation exchanges, can improve efficiency, achieve maximum effect.

Question: 4.7 3. Do I need to have code specifications?

Think: I feel like an organization, a team, should have a certain discipline, although allowed to blossom in a certain situation, showing the characteristics of their code. But from the team, I think it's very necessary to have code specifications. Because people look at your code easier to understand, save time and improve the efficiency of the team.

　　

Reading the fourth chapter of the Law of construction