Pair programming is the practice of two programmers working together at one workstation. In infrastructure-as-code work, it moves change review earlier, combining implementation with immediate collaboration. section 7.3
Use pairing deliberately when infrastructure changes require shared understanding:
- Have one engineer catch omissions or risks that the other may miss. section 7.3
- Share infrastructure terminology and institutional knowledge while changes are written. section 7.3
- Expect an initial delivery slowdown, resource constraints, personality conflicts, and differences in working pace. section 7.3
- Build self-awareness and discipline so pairing remains a safe space for learning and applying coding best practices. section 7.3
Infrastructure access control
Pair on a change that adds a team to a GCP project. Discuss whether access should use an authoritative binding, then encode the decision while sharing its rationale with current and future teammates. section 7.3
