Building law Enforcement Read Note 03

Then read down on the two men working together. In the IT industry, we call the code, that is, programming is our basic ability, is to measure whether we are professional standards, but the high level of programming does not mean that our professional quality is high, so-called professional quality is our code SU whether the specification, whether there is strict indentation, in the module is the division of {}, The structure is strict and neat, the code of thought is clear and so on. We have just contacted this industry, learning coding time is not long, so we should start from now on every program, strict code, to a professional quality standards to measure the requirements of their own, from the beginning to form a good habit, improve their professional quality, appear more professional. After we have written the code to review the code is also essential, to develop these good writing code habits for us in the future in the Professional post is very helpful. Then is the emphasis of the chapter on pairing programming. Pair programming technology is a very simple and intuitive concept, can achieve a multiplier effect of the work. But people-to-people cooperation is not a simple thing-especially when people are accustomed to working alone. The implementation of pair programming technology will bring benefits to the development of software projects, but these benefits must be carefully considered and planned to truly reflect. On the other hand, two experienced people may find that there is no skill transfer in pairing programming, but letting them solve the same problem at different levels of abstraction will allow them to find a solution faster and with fewer errors. Two programmers are less likely to have the same drawbacks and blind spots, so when we use pair programming we get a powerful solution. And this solution is exactly what other software engineering methodologies do not. In our usual programming, if you encounter a very difficult problem (difficult to get bored with the project), then you are bound to want to record help, whether it is from the vast amount of information on the Internet, or from the side of the technology guru, you will work hard to solve (if you have a love of computer knowledge). This time might as well use pair programming to try, others do not say, may feel different. In fact, pairs of programming sit up very simple and very interesting, find a poor level of the programmer and not too far to match their own pair. Use only one computer, everyone choose a person to sit in front of the keyboard for input, another person sitting behind to dictate. Two people to communicate constantly, the frequency should not be less than one minute. The whole idea of design from behind only mouth not to hand-dominated, and by the keyboard to do the implementation of the person. Because people's thinking speed is faster than the speed of the input code. Then the person watching can have free time to do extra thinking, observe the code to write the question of whether there is no problem with the structure. Some new benefits have been found with respect to pairing programming. It can promote the programmer to participate in the project's own improvement, when a pair of programmers work, the lower level of the party will be subtly affected by a slightly higher level of programmers, learning something new. And the high-level side is also because of the constant to tell their own ideasCome and tidy up their own ideas.

Then Mr. Wang also let us two person knot group to develop program, just start not adapt to feel very awkward, but really let a person follow another person's thinking to write, another person said side check code whether there are errors, format is standardized, the ability to cooperate has a great improvement.

Building law Enforcement Read Note 03