during the 11 National Day (and of course, the days before the national day), we carried out a pair programming project. I benefited a lot, in front of the partners to find their small, in the knowledge, always lost to the vast ocean, in time to find their own shortcomings, the elevator project, for me is equivalent to a practical project. And in some logic is not considered very rigorous, the final question is very real. Fortunately, in partnership with partners, our program is close to the perfect important link. It not only improves the efficiency, but also guarantees the correctness of the program writing. Finally, let's talk about how we feel about pairing programming.
experience and lessons learned:
the advantages of pairing programming we believe that the advantage of pair programming lies in the sharing of design ideas, and we avoid mistakes for each other. In general, the mistakes that you make when you're programming, though simple, are hard to spot, and in the eyes of another person, it's obvious. Of course, pairs of programming also have inappropriate places, such as the programming of other courses, need each of us to complete independently, you can not rely on peer help, there are some very traditional, standardized programming tasks, such as writing a section of the most conventional fast algorithm, at this time if someone is next to, it is purely a waste of time, Because these things are so familiar to us, we don't need to be guided by others. because pair programming can greatly improve the efficiency of programming, and two people programming in turn, not too tired, it is very suitable for agile development. If we are going to work on software development in the future, we will be very happy to do pairing programming, because it will greatly improve our programming experience, the programming is no longer so boring, debug road is not so scary. in the design phase, for example, one of us thought of adopting a strategy model to solve this problem, using an interface as the abstract behavior layer. another person found that our specific algorithm classes have some common behavior, so consider using abstract classes instead of the original interface as the abstract behavior layer, which can move those common behavior to the abstraction layer, greatly reducing redundant code, so that the design becomes more elegant. second, the disadvantage of pairing programming pair programming at the beginning, our two of the cooperation is not smooth, the use of the IDE's habits are different, coding habits are different, and even the expression of a word there are differences, will affect our efficiency. Just as we are getting used to each other, our task is basically over. Two people programming together inevitably appear inconsistent phenomenon, this situation we take the way is to stop the work at hand, until the discussion clearly concluded that, sometimes we have such a discussion may last longer, will affect our productivity.
Pairing programming Summary by Huang Bushin bin Li
