Advantages and disadvantages of Pair Programming

This article is also published in: cool shell (Http://www.cocre.com /? P = 77 )

 

Advantages and disadvantages of Pair Programming

 

Chen Hao

Http://blog.csdn.net/haoel

 

Pair-programming may be the most popular programming method in recent years. The so-called Pair programming, that is, two people write a program, one is called driver, the other is called observer, and the driver is programmingCodeWhile the observer can view the driver code in real time and help the driver program. In addition, the driver and observer can be discussed with each other to effectively avoid closed doors and build a car, reduce the code review time in the future, and reduce the code learning cost.

 

Experiments show that, on average, the cost of Pair programming time is 10% more than that of single-person programming, but it also reduces code bugs by 15%. If you calculate the code maintenance and learning costs in the later stage, Pair programming is more efficient and cost-effective than single-user programming. Pair programming is a very good programming practice for both the development team and the business.

The following are some advantages of Pair programming:

1. ProgramMembers help each other and teach each other to complement each other.
2. This allows the programming environment to effectively implement design.
3. Enhance code and product quality and effectively reduce bugs.
4. Reduce learning costs. Programming, sharing knowledge and experience, and learning effectively in practice.
5. During the compilation process, mutual discussions may help solve problems faster and more effectively.

 

 

Of course, there may also be some bad points for team-end programming:

1. Programmers who have different habits can have trouble or even conflict at work.
2. Sometimes, programmers will disagree on a problem (the Code style may be the place where the technical staff may enter war) and quarrel will lead to a major internal friction.
3. When two people work together, they may be unable to concentrate. Programmers may talk about work-independent things, but they are distracted, resulting in lower efficiency than single users.
4. Pair programming may allow programmers to learn from each other more quickly. In some cases, learning from each other may grow as fast as it is for programmers. For example, partner to deal with work, perfunctory projects.
5. Experienced veterans may feel very excited in the face of new users. Inappropriate communication leads to team discord.
6. When new users are faced with experienced veterans, they are very nervous and uneasy, and even have a mental state of fear and anxiety, which leads to low-level errors, the Veterans keep following them and accuse them of causing them to become more nervous and have a vicious circle. This eventually leads to inefficient project progress and team appearance.
7. Experienced people prefer individual combat. Looking for someone to stand behind him may make him very uncomfortable. This will eventually lead to emotional impact during programming, but vice versa.

Whether to use Pair programming requires specific analysis of specific issues and cannot be blind. Everything has its own good and bad, and paired programming is no exception. Only by knowing the good and the bad can you make better use of it.

 

Finally, we need to remember that people are a very complex animal. their shortcomings and inner shadows may be worse than you think, these things can make everything fail. Therefore, as man ware said, talent is the core of software development and the most important thing that requires time to focus on.

 

 

 

(Indicate the author and source when reprinting. Do not use it for commercial purposes without permission)

 

MoreArticleVisit my blog:Http://blog.csdn.net/haoel