To Pair or Not to Pair: Pair Programming

Поділитися
Вставка
  • Опубліковано 15 жов 2024

КОМЕНТАРІ • 30

  • @AllanKobelansky
    @AllanKobelansky 3 роки тому +9

    I think we need some research on “pair team leads, or pair managers”.

    • @robotempire
      @robotempire 3 роки тому +1

      Very interesting thought.

  • @dmlled
    @dmlled Рік тому

    re-visiting after many years. Superb talk, still

  • @neptronix
    @neptronix 2 роки тому

    This video convinced me to give this a try at my new company. Thanks for the talk!

  • @ishimwejoseph833
    @ishimwejoseph833 Рік тому

    Pair programming very well explain ! Thanks

  • @AnitShrestha
    @AnitShrestha 5 років тому +3

    Really a great presentation on Pair Programming covering a lot of aspects!
    Two minds are greater than one only if both are at sync and understanding. Also, I believe that if the individuals can achieve the feeling of togetherness, this helps to solve the problem of loneliness as well.
    In my years of experience tackling the hard/confusing/unclear tasks a lot of time alone with the feeling of not being able to ask for help or even find help did made me unhappy and hindered my growth.
    Hence, I take Pair Programming in very a positive way to share and grow together. I think you know more about your own skill sets when you share. I look forward to more insight in future video on the subject.
    Thank you Birgitta Böckeler and ThoughtWorks!!!

  • @martinkarugaba
    @martinkarugaba Рік тому

    Thank you, I learned alot.

  • @shannonmalayajones7649
    @shannonmalayajones7649 4 роки тому +1

    Tactical and strategic

  • @rhalesdev
    @rhalesdev 4 роки тому

    Ooo nice try, but who built the ENIAC?

  • @shannonmalayajones7649
    @shannonmalayajones7649 4 роки тому

    Concentration
    Empathy
    Time management
    Energy
    Feedback
    Awareness of difference
    It personal

  • @mayurdave8154
    @mayurdave8154 6 років тому +1

    ua-cam.com/video/S92vVAEofes/v-deo.html

  • @jimjones6419
    @jimjones6419 3 роки тому

    I've watched a few video's on this technique and can't find any comments that say this increases velocity.

    • @tamil-ml
      @tamil-ml 3 роки тому +4

      pairing is only 15% slower than individual development but provides more quality code so the trade-off is much more worth it.

  • @naomilfmn3325
    @naomilfmn3325 3 роки тому

    love this video very cool :0

  • @G4GBill
    @G4GBill 3 роки тому +1

    Do you remove all responsibility, expectations and deadlines from the Senior during this period of time, otherwise where is the incentive. I could possibly see a Senior being asked to spend 25 minutes total for their day!

  • @shannonmalayajones7649
    @shannonmalayajones7649 4 роки тому +1

    Frictional and frictional change🤫

  • @shannonmalayajones7649
    @shannonmalayajones7649 4 роки тому

    K

  • @shannonmalayajones7649
    @shannonmalayajones7649 4 роки тому

    Programme to be foretirna twins at work

  • @G4GBill
    @G4GBill 3 роки тому +1

    Looks to me that this isn't viable just from your need to delete all the comments!

  • @JazzMachine77
    @JazzMachine77 5 років тому +13

    Funny how today non-tech people who hardly can use excel want to tell experienced engineers how they should code.

    • @dalxo
      @dalxo 3 роки тому +4

      Can't agree more. I saw literally ruining the entire team when this technique was hard push by a non-tech manager who just heard about it somewhere on UA-cam. All seniors and the most experienced people (5-10 years in the team) quit within one year. I had to work hard, spent lot of my free time to self educate, learn new tech, read books and why should I give all that knowledge for free to someone fucking lazy junior who just believe that life is fun and it's my duty to babysit him. I have seen this technique being more abused and wrongfully applied than any benefit.
      Btw. I do pairing - but when it makes sense and with people who share common working habits (reliability, respect, resourcefulness), then it's really a pleasure.

    • @robotempire
      @robotempire 3 роки тому +1

      I hope you’ve grown beyond childish & idiotic thoughts like this.

  • @ChiefsFanInSC
    @ChiefsFanInSC 3 роки тому +3

    A third reason pair programming has never taken off is that it is a bad idea.

  • @fareed1983
    @fareed1983 2 роки тому +1

    I helped a co-worker at the start of my career by programming in pair with him and teaching him the right way of using object oriented methods in the project we were doing. He took all the credit and became my arch enemy throughout his career due to his jealousy of not being able to keep-up with me. Pair programming is just a forceful way to create redundancies so that arrogant brilliant talented coders will not become too powerful and low-esteemed technically challenged project managers don't have an existential crises.

  • @littlebearjeremy
    @littlebearjeremy 3 роки тому

    President Xi should watch this

  • @edwinov
    @edwinov 2 роки тому

    Pair programming sucks harder than a NILFISK !!!!!!!