liveBook · Manning

Pair programming

As explained in Lead Developer Career Guide

A software development technique in which two developers work together at one computer or on the same code.

Pair programming puts two developers at one computer or in the same coding session: one types while the other watches, suggests approaches, researches, and reviews. section 6.5.3

Use the technique to improve both code and team practice:

  • Prevent technical debt by giving the code an objective reviewer during implementation. section 6.5.3
  • Surface opportunities to optimize the development process and improve application structure. section 6.5.3
  • Learn another developer’s workflow while building camaraderie and exchanging ideas. section 6.5.3
  • Use sessions to observe problem-solving, code organization, and debugging skills when mentoring developers. section 9.3.2

A mentoring session

A mentor pairs with a mentee while implementing a task. The mentee types, and the mentor watches the problem-solving approach, asks questions, suggests alternatives, and notes opportunities to improve code organization or debugging. section 6.5.3 section 9.3.2

How Lead Developer Career Guide covers it

How deep it goes
Defines alternating typing and review roles and explains benefits, but stops short of prescribing session procedures.
Examples
Shows one developer typing while another reviews and suggests, and uses mentoring sessions to observe problem-solving, organization, and debugging.
What you can do after
Practice pair programming to produce cleaner code, identify process improvements, and assess or develop technical skills.
How it connects
Connects pair programming with technical debt, code review, debugging, mentoring, collaboration, and development-process optimization.

Also explained in

Compare how 5 books explain pair programming →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.