• ChickenLadyLovesLife@lemmy.world
    link
    fedilink
    English
    arrow-up
    45
    arrow-down
    2
    ·
    2 days ago

    I was fine with mentoring junior developers until my manager decided pair programming was the way to go. I’m happy to help and teach, but like fuck am I going to sit at the same goddamn computer with some maroon all day. Can’t even power-nap properly.

    • pinball_wizard@lemmy.zip
      link
      fedilink
      arrow-up
      5
      ·
      19 hours ago

      Can’t even power-nap properly.

      Yes. Pair programming should be encouraged when appropriate, not mandated.

      Naps are a part of the critical path! Lol.

    • mynamesnotrick@lemmy.zip
      link
      fedilink
      arrow-up
      6
      ·
      21 hours ago

      Full agree. Pair programming makes me unproductive and it’s always just feels like one person doing it and the other person in the back saying “uh huh, yeah”. Our place used it as a learning opportunity but the problem is the person I pair with haven’t ever worked on my project and have no clue what’s going on when I’m month deep into a feature branch.

    • Rooster326@programming.dev
      link
      fedilink
      arrow-up
      7
      ·
      21 hours ago

      The entire reason we developed git was so nobody would ever have to pair program again.

      Does he also request you write the code on paper first?

    • fruitycoder@sh.itjust.works
      link
      fedilink
      arrow-up
      20
      ·
      1 day ago

      Pair programing with a mentor shouldn’t be a day to day thing. Like why waste the time and put so much pressure on the trainee like that anyways?

      • epyon22@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        18
        ·
        1 day ago

        Honestly pair programming I feel works better with more similar abilities than far off. Also give em a task to let them struggle a bit in the beginning of the sprint.