Construction of the Law 03

I used to think that the development of the program is to do their own things, and their different ideas of people to communicate is a waste of time

In reading the construction of the law, I learned that:

4.1 Large sections refers to the code specification, we write code to pay attention to code style specifications and code design specifications, whether it is the class name, object name, indentation or line width of what, in the knot programming must have provisions, or to the back of the class or object more, it is easy to mess up, it is unclear who is who. To learn to encapsulate, write functions, the function module to materialize, reduce the main method inside the code, avoid large-scale error.

4.4 Refers to the code review, in peacetime programming program, I will also look at their own code, run the program, if the results are the same, error can be. Did not want to find out the code error, but also to consider whether the logic is wrong, the algorithm is not enough optimization and other problems. Can others feel that the program I am writing is easy to understand and can learn from it.

4.5 Pair programming, two people work together, think together to write a program, is conducive to improve efficiency, learn from each other. So to learn the different stages and techniques of cooperation mentioned in section 4.6, when beginning to explore the project, halfway through the problem, when the simple review, you can think independently, the period of clear thinking, good communication, together to write, strengthen cooperation. In the cooperation in an objective and comprehensive treatment of their own partners, know how to encourage each other, learn from each other.

I must do this later:

By pairing, I realized that writing a program is not just about knowing, but also seeing and understanding your own programs with others.

Construction of the Law 03