Software Engineering (3) pair programming

This pair programmed to record the video when the choice to complete the refund function, the leader is responsible for writing code, I supervise and try to point out the process of writing code problems.

The advantage of choosing the refund function for pairing programming is that both parties are familiar with the code of the ticket part (and because other courses have delayed the development of the group, I am not familiar with the code of the activity part of the team leader), the logic of the refund is similar to that for pairing programming.

There are not too many problems in the process of pairing programming, the mistake I really point out should be only to add the handler class to the view, the other feels more like the team leader deliberately test me ... (vaguely think that if there is time in the last Saturday, the team leader to teach me how to write the process of recording a better record of the ticket ...) ）

Personally feel this pairing is a very meaningful attempt, and it has made us familiar with this relatively new way of programming. Compared to the final integration of each of the previous individuals, pairing programming helps reduce debug time, helps to avoid the problems encountered during the integration of two human code, and helps to unify the code style.

Perhaps the only drawback is that because I do not understand the code and interface of the active part, this pair programming does not choose more challenging content.

Software Engineering (3) pair programming