Pair programming
Pair programming is a software development practice in which two people collaborate on the same programming task, sharing implementation, review, or guidance responsibilities.
"Looks Good to Me"
Pair programming is a software-development practice in which two programmers collaborate simultaneously on the same task, typically sharing one work context.
- How it is used
- Uses two-person collaboration to improve implementation, share context, and support code review throughout development.
- How deep it goes
- Explains roles, styles, adoption steps, workspace needs, session length, remote considerations, and limits relative to code review.
- Examples
- Uses driver–navigator, driving school, Pomodoro, tour guide, ping-pong, and tag-team styles alongside legacy-code and review-feedback scenarios.
- What you can do after
- Apply it by selecting a pairing style, running a small trial, switching roles, and retaining code review for team-wide documentation.
The Creative Programmer
Pair programming is a software-development practice in which two programmers work together at one workstation or on the same code.
- How it is used
- Uses pair programming to share responsibility, reduce social debt, and help teammates challenge misconceptions constructively.
- How deep it goes
- Explains team, learning, quality, and creativity trade-offs, with pair rotation and reflective breathing room as practical guidance.
- Examples
- Contrasts enforced all-day pairing with sporadic pairing and examines expert–novice sessions that run at mismatched speeds.
- What you can do after
- Apply it by rotating partners, matching collaboration to learning needs, and reserving solo time for reflection.
Read how The Creative Programmer explains pair programming →
Introduction to Generative AI, Second Edition
A software-development practice in which two programmers collaborate closely on the same code.
- How it is used
- Positions language models as interactive programming partners that accelerate coding without making them autonomous replacements.
- How deep it goes
- Explains autocomplete, natural-language requests, iteration, and limitations, but defers detailed treatment of newer agentic tools.
- Examples
- Uses Copilot suggestions, comment-to-code conversion, testing assistance, and a generated function docstring as examples.
- What you can do after
- Apply via AI coding assistants to draft, complete, test, and iteratively revise code while checking proposed results.
Read how Introduction to Generative AI, Second Edition explains pair programming →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Pair programming is a software development practice in which two programmers work together on the same implementation, typically sharing one workstation or alternating coding and navigation roles.
- How it is used
- Moves infrastructure change review earlier by combining implementation, collaboration, and knowledge sharing.
- How deep it goes
- Defines the practice, explains benefits and adoption risks, but defers detailed pairing processes.
- Examples
- Uses GCP project access control, authoritative bindings, and collaborative infrastructure implementation as concrete examples.
- What you can do after
- Apply pairing to identify infrastructure conflicts earlier and preserve architectural rationale during implementation.
Lead Developer Career Guide
A software development technique in which two developers work together at one computer or on the same code.
- How it is used
- Uses collaborative coding to improve implementation quality, development processes, team learning, and mentoring assessment.
- 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.
Read how Lead Developer Career Guide explains pair programming →
Related concepts
- technical debtaddresses · Technical debt is the future cost, effort, or risk created by technical choices or deferred work that make a system harder to change, maintain, or operate.
- code reviewcontrasts with · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
- AI agentcontrasts with · An AI agent is a computational system that uses artificial intelligence to interpret information, select actions, and pursue goals through interaction with an environment.
- social debtaddresses · Social debt is the accumulated cost of unresolved interpersonal or team problems that impair collaboration and performance.
- driver-navigator styleincludes · A pair-programming arrangement in which one programmer writes code while the other reviews and guides the work in real time.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.