Comments by "Edward Cullen" (@edwardcullen1739) on "You Must Be CRAZY To Do Pair Programming" video.

  1. I've been really struggling with this in DevOps for a long time - everywhere I go, I end up on a "team" of individuals, working on disparate work streams, with very little day-to-day collaboration. Sure, for simple admin stuff, this is fine, but when you have to do something complex / implement something new, I often need to spend much longer on knowledge transfer (partly because of the junior nature of my colleagues). This is something I'm going to take a much harder line on as I think it really would be a Silver Bullet for so much; in the DevOps context, this would mean more like one person doing, the other documenting, which is at least a line I can try to placate the bean-counters...
    19
  2. I find the contrary - the worse the code (the more I need to hold in my head at once...) - the more beneficial pair-programming is as you can share that burden and you have someone to validate what your thinking.
    11
  3. You actually write code 8 hours a day? Where's your thinking and design time? "Talking in your ear" sounds like you don't like the people you work with, more than you don't like pair programming...
    4
  4. Software development is a collaborative exercise. No individual can effectively produce and maintain software of meaningful complexity.
    3
  5.  @georgeonearth  I guess you've never experienced a merge conflict then?
    1