Answers: <p>Agile fits very well with a DevOps culture and pair programming is no exception.</p>
  
  <p>The following are some examples of "pair programming" principles applied in a DevOps context:</p>
  
  <ul>
  <li>A pair of individuals working together on a Dockerfile for their service.</li>
  <li>A pairing sits together to work on defining their infrastructure as code.</li>
  <li>A traditional developer and an IT administrator building a <a href="https://en.wikipedia.org/wiki/CI/CD" rel="nofollow noreferrer">CI/CD</a> pipeline together.</li>
  <li>A specialist and tester sit together to define what the testing environment should look like.</li>
  <li>A specialist and a customer sitting together and working on a deployment to the customers infrastructure.</li>
  </ul>
  
Answers: CC BY-SA 4.0
Answers: 2019-12-12T19:40:29.960Z
Answers: 2019-12-12T19:40:29.960Z
Answers: Wesley Rolnick
Body: <p>In agile, pair programming can be performed like the following:</p>
  
  <ul>
  <li>two specialists of same discipline change the place before the terminal and each has a chance to code and to conceptualize/reflect;</li>
  <li>two specialists of different disciplines work together, but one is rather a customer and cannot code much in the target language; also the coder might not know much about the requirements which then discussed directly and coded and tested and deployed.</li>
  </ul>
  
  <p>How is this relevant/appliable in DevOps context? (facts)</p>
  
Tags: <deployment><culture><agile><software-engineering>
Title: How well can agile pair programming work in interdisciplinary DevOps contexts?
UserDisplayName: Ta Mu
ThreadText: # How well can agile pair programming work in interdisciplinary DevOps contexts?
  
  (Asked by: username_0 on 2019-12-12)
  
  In agile, pair programming can be performed like the following:
  
  * two specialists of same discipline change the place before the terminal and each has a chance to code and to conceptualize/reflect;
  * two specialists of different disciplines work together, but one is rather a customer and cannot code much in the target language; also the coder might not know much about the requirements which then discussed directly and coded and tested and deployed.
  
  How is this relevant/appliable in DevOps context? (facts)
  
  **Tags:** deployment, culture, agile, software-engineering
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-12-12. Score: 2
  
  Agile fits very well with a DevOps culture and pair programming is no exception.
  
  The following are some examples of "pair programming" principles applied in a DevOps context:
  
  * A pair of individuals working together on a Dockerfile for their service.
  * A pairing sits together to work on defining their infrastructure as code.
  * A traditional developer and an IT administrator building a [CI/CD](https://en.wikipedia.org/wiki/CI/CD) pipeline together.
  * A specialist and tester sit together to define what the testing environment should look like.
  * A specialist and a customer sitting together and working on a deployment to the customers infrastructure.
  
  
  ---
  
  