{"id":558,"date":"2013-09-15T20:28:13","date_gmt":"2013-09-15T17:28:13","guid":{"rendered":"http:\/\/blog.adrianbolboaca.ro\/?p=558"},"modified":"2014-12-16T09:58:21","modified_gmt":"2014-12-16T07:58:21","slug":"what-is-pair-programming","status":"publish","type":"post","link":"https:\/\/blog.adrianbolboaca.ro\/2013\/09\/what-is-pair-programming\/","title":{"rendered":"What is pair programming?"},"content":{"rendered":"

Pair Programming<\/h1>\n

Blog post series<\/h3>\n

This blog post is part of a series about pair programming games. To read about more please click see more sessions<\/a> on pair programming games.<\/p>\n

About<\/h3>\n

Pair programming is a technique in which two programmers work together to solve a task. They work on one computer, ideally each having their own keyboard in front of them.
\nThere are two roles: driver<\/strong> and navigator<\/strong>.<\/p>\n

The driver writes the code and takes the short time decisions. The driver should trust the navigator totally for the long term decisions.<\/p>\n

The navigator reads the code of the driver and gives meaningful suggestions on how the code could be better. Also the navigator focuses on the long term decisions and thinks the strategic direction the code moves to.<\/p>\n

Both the driver and the navigator need to verbalize their actions and concerns and to speak on the code.<\/p>\n

\"cat-pair-programming\"<\/a><\/p>\n

<\/p>\n

Advantages<\/h3>\n

From some studies (see here<\/a> for example) we can say that when programmers work in pairs usually produce less code with less defects and a better design.
\nPair programming is the fastest feedback loop in the Agile world.
\nUsually pairs tend to write unit tests for the important cases as the navigator can spot missing tests.
\nLearning: knowledge can pass easier from the more experience to the less experienced team members, or the other way around.
\nConfidence of the team in the code correctness and quality.<\/p>\n

Disadvantages<\/h3>\n

Can be very tiring especially for beginners.
\nCould lead to fights and decreased team morale between team members in the case the two pairing do not get allong.
\nBreaking the ice: it is often difficult for people to start pairing, as the first sessions are awkward because the two pairs open themselves one to the other and they might be afraid of criticism.<\/p>\n

Sessions<\/a><\/h3>\n

I started a series of articles on the theme of pair programming games. Each of the games has some clear purposes and should be used in certain cases. Some of the games can be used to improve the communication thus to improve the productivity. Some others are useful to use when you have a rock star in your team. And yet others are powerful for fast learning. So here are the games:<\/p>\n