Thanks for the overview. I have started to pair-program with the new team/company I have recently joined. At first I was reluctant to it and wanted my own space to think about the logic/problem/solution but after a few session I am starting to see the huge benefits to it! I'm really looking forward to many more pair-programming sessions with my colleagues :)
The statement that code ownership is a bad idea and that everyone on the team should share the code seems like a good idea at first but there is a learning curve involved with jumping between the different pieces. We experienced this when we coded a system that spanned database code, front end code and mainframe code. Every few months we needed to refresh on MVS/TSO/JCL/DB2 ...of course if the code base is small this works well. I think pairing works best on initial design approach before coding starts. And then it would be more of a team discussion.
Hey, great video. Perhaps you could look to what woody zuil has to say about driver/navigator. His definitions are a bit different, but it’s in the context of ensemble programming. I tend to follow his definition more
I've seen a talk from Woody in the past about mob programming, but I'm not sure how his driver/navigator is different from what I'm saying, can you elaborate? Btw, I also have a video about driver/navigator in more detail: ua-cam.com/video/jqGmL6Hf23k/v-deo.html
Great video! How did you make your description so professional? It has images, clear spacing? Is there a format or something you can use. Would love to know more
I hate pair programming.. at least at my current company (never did it before): - the development is way way slower - the quality is not necessary better - It is very energy draining.. the need to explain every single character and discussing why I use X over Y is crazy - I can't focus if someone is talking, especially about some unrelated bullshit. - other devs usually don't take any breaks. That means sometimes I sit for 5 hours and talk about everything Sometimes we had a bigger problem, and we talked about it for hours and tried to solve it. Later after work I thought about the problem by myself quietly for few minutes and solved the problem in 30 minutes... I prefer to work alone and if I need help (or someone else needs help) I am OK with pair programming for max 1 hour. I also love to listen to music while coding and not blah blah blah.. Maybe I am not compatible with pair programming or maybe we are doing it wrong, I don't know.. But for me it is a nightmare. In my next job, I will explicitly ask if the company is doing pair programming.
Thanks for the overview. I have started to pair-program with the new team/company I have recently joined. At first I was reluctant to it and wanted my own space to think about the logic/problem/solution but after a few session I am starting to see the huge benefits to it! I'm really looking forward to many more pair-programming sessions with my colleagues :)
Thank you for the great video. We're only going to use pair programming in our team so I found it extremely useful.
The statement that code ownership is a bad idea and that everyone on the team should share the code seems like a good idea at first but there is a learning curve involved with jumping between the different pieces. We experienced this when we coded a system that spanned database code, front end code and mainframe code. Every few months we needed to refresh on MVS/TSO/JCL/DB2 ...of course if the code base is small this works well.
I think pairing works best on initial design approach before coding starts. And then it would be more of a team discussion.
I have a code paring interview coming up. This video is helpful.
Thanks for this mate!
I’m sure to learn a lot from you!
Hey, great video. Perhaps you could look to what woody zuil has to say about driver/navigator. His definitions are a bit different, but it’s in the context of ensemble programming. I tend to follow his definition more
I've seen a talk from Woody in the past about mob programming, but I'm not sure how his driver/navigator is different from what I'm saying, can you elaborate?
Btw, I also have a video about driver/navigator in more detail: ua-cam.com/video/jqGmL6Hf23k/v-deo.html
Im going to propose this at the start-up im workign at 🎉
Cool video! Appreciate the helpful tips🤩
Great video, would love to hear your thoughts on pair programming between a junior and senior dev, more of a mentor/mentee role
I recommend you read the "Different skill levels" section of this article:
martinfowler.com/articles/on-pair-programming.html#DifferentSkillLevels
Great content mate.
Great video! How did you make your description so professional? It has images, clear spacing? Is there a format or something you can use. Would love to know more
Do you mean the chapters? YT generates the design itself, I only provide the "0:00 Intro, 0:20 Chapter 1" etc.
@@branvandermeer I think UA-cam did an update and I just realized it when viewing your video. I thought there was some kind of code you used.
Great content!! thank you!
This was helpful. Thanks!
I hate pair programming.. at least at my current company (never did it before):
- the development is way way slower
- the quality is not necessary better
- It is very energy draining.. the need to explain every single character and discussing why I use X over Y is crazy
- I can't focus if someone is talking, especially about some unrelated bullshit.
- other devs usually don't take any breaks. That means sometimes I sit for 5 hours and talk about everything
Sometimes we had a bigger problem, and we talked about it for hours and tried to solve it. Later after work I thought about the problem by myself quietly for few minutes and solved the problem in 30 minutes...
I prefer to work alone and if I need help (or someone else needs help) I am OK with pair programming for max 1 hour.
I also love to listen to music while coding and not blah blah blah..
Maybe I am not compatible with pair programming or maybe we are doing it wrong, I don't know.. But for me it is a nightmare.
In my next job, I will explicitly ask if the company is doing pair programming.
Great video,
Subscribed!