pepopowitz’s avatarpepopowitz’s Twitter Archive—№ 1,878

    1. …in reply to @hilarysk
      @hilarysk @10fw So many thoughts!!!! 1. Don't just explain _what_ you're doing, explain _why_ you're doing it. Verbalize your thoughts - "when I see this error, it makes me think we got something wrong with XXXX. I'm going to type YYY in my console to verify."
      Permalink On twitter.com Twitter logo pepopowitz’s avatar ❤️ 3 Favorites Mood -4 🙁
  1. …in reply to @pepopowitz
    @hilarysk @10fw 2. Assume in the nicest way possible that your pair does not have the same context as you. The person with more context should ask as many questions as the person without the context - "have you seen this function before? Do you want to see what it does?"
    On twitter.com Twitter logo pepopowitz’s avatar ❤️ 2 Favorites Mood +1 🙂
    1. …in reply to @pepopowitz
      @hilarysk @10fw 3. I prefer for the person with less context to drive, otherwise it's too easy to lose them while the person with more context flies through things. This isn't necessary, and the problem is probably also addressed by over-explaining/asking questions/keeping them engaged.
      Permalink On twitter.com Twitter logo pepopowitz’s avatar ❤️ 3 Favorites Mood -1 🙁
      1. …in reply to @pepopowitz
        @hilarysk @10fw 4. With 2 of you, you're more likely to get side-tracked. Track assumptions & decisions you make, remaining work, things to investigate. Keep them in a place accessible to both, so one can pick up work when the other's not available.
        Permalink On twitter.com Twitter logo pepopowitz’s avatar ❤️ 1 Favorite Mood +1 🙂
        1. …in reply to @pepopowitz
          @hilarysk @10fw 5. For long sessions, take frequent breaks, switch drivers often, don't be afraid to say "hey I just want five minutes to catch up on comms for a bit." Be respectful of each others' needs to get some space.
          Permalink On twitter.com Twitter logo pepopowitz’s avatar ❤️ 1 Favorite Mood -1 🙁
          1. …in reply to @pepopowitz
            @hilarysk @10fw 6. Use a tool to credit each other for your commits when pairing. My friend & coworker @jonallured is working on github.com/jonallured/pear, or there's github.com/git-duet/git-duet.
            Permalink On twitter.com Twitter logo pepopowitz’s avatar ♻️ 1 Retweets ❤️ 1 Favorite Mood +2 🙂
            1. …in reply to @pepopowitz
              @hilarysk @10fw @jonallured 7. I do all my pairing remotely, and strong internet is important for that. I don't have much to say about in-person pairing, but I've heard/read that it's helpful to have two of everything, even in the same space. (source: artsy.github.io/blog/2018/10/19/pair-programming/)
              Permalink On twitter.com Twitter logo pepopowitz’s avatar ❤️ 1 Favorite Mood +6 🙂