11–20 of 29 posts
We just latch onto hysteria.
Earlier quoted context omitted.
That’s ridiculous. Pairing 100% would seriously hamper productivity. You need time to withdraw into your mind and think through solutions. This is why code reviews were invented.
Highly recommended: https://www.gerritcodereview.com/
This is very ideology over common sense. There is no scientific approach in software development. Did anyone conduct a reproducible study that was peer reviewed that concluded that pair programming was x-times better in creating relatively bug free software? We just latch onto hysteria.
Earlier quoted context omitted.
That’s ridiculous. Pairing 100% would seriously hamper productivity. You need time to withdraw into your mind and think through solutions. This is why code reviews were invented.
Highly recommended: https://www.gerritcodereview.com/
Earlier quoted context omitted.
The company I work for is completely committed to pair programming, which means everyone does it a 100% of the time. It is fine to help you ramp up when you just joined, but after 4 months of non-stop pairing, it seems like it's just too much.
This is such an interesting approach. I’ve read about this at Pivotal, and it’s interesting to see how it’s described on their blog vs Glassdoor. I greatly enjoy working with another engineer to solve an especially tricky problem, but only pair programming seems like it would be exhausting. What do you like and dislike about it?
Earlier quoted context omitted.
This is such an interesting approach. I’ve read about this at Pivotal, and it’s interesting to see how it’s described on their blog vs Glassdoor. I greatly enjoy working with another engineer to solve an especially tricky problem, but only pair programming seems like it would be exhausting. What do you like and dislike about it?
I dislike someone sitting next to me telling me what they think I should type for 6-8 hours a day.
My guess would be that full pair-programming wouldn't be uni-directional (you type, I tell you what to type, all day, every day), but I could definitely see that being the worst-case scenario.
Earlier quoted context omitted.
This is such an interesting approach. I’ve read about this at Pivotal, and it’s interesting to see how it’s described on their blog vs Glassdoor. I greatly enjoy working with another engineer to solve an especially tricky problem, but only pair programming seems like it would be exhausting. What do you like and dislike about it?
I totally agree it is useful for particularly tricky problems. It is not a coincidence that what I like the most about it is the initial discussion on the potential approaches to solving the problem. But then when we move into the implementation phase, that is when things get tiresome after four months of continuous and permanent pairing, because in my case, I appreciate silence and time to focus and think at my own…
Earlier quoted context omitted.
I dislike someone sitting next to me telling me what they think I should type for 6-8 hours a day.
I noticed you mentioned before that you are currently a company founder; was your full pair-programming experience at a previous job? Was that what it was like, and were you forced to work with an individual in which that was the dynamic? My guess would be that full pair-programming wouldn't be uni-directional (you type, I tell you what to type, all day, every day), but I could definitely see that being the worst-cas…
I would say your last statement is correct, each team needs to find working dynamics that make all members successful. I finished the project on that team and accepted a contract position in another city for a larger client.
We have a new project though, a graph backed transaction management platform, that will require more collaboration than our usual crud app but we will still not have a policy that involves "sit down and write the code together."
Earlier quoted context omitted.
The company I work for is completely committed to pair programming, which means everyone does it a 100% of the time. It is fine to help you ramp up when you just joined, but after 4 months of non-stop pairing, it seems like it's just too much.
That’s ridiculous. Pairing 100% would seriously hamper productivity. You need time to withdraw into your mind and think through solutions. This is why code reviews were invented.
Not everyone can sit down for 8 hours a day and write code. Some number of people get distracted by Facebook, Hacker News, whatever it might be. Having a baby-sitter of sorts sitting next to you certainly keeps this kind of person on track - and I know, I'm one of them.
Of course this is not every engineer out there. Sure, some people are able to stay focused for 8 hours a day, but I'm certainly not one of them.
Earlier quoted context omitted.
That’s ridiculous. Pairing 100% would seriously hamper productivity. You need time to withdraw into your mind and think through solutions. This is why code reviews were invented.
Highly recommended: https://www.gerritcodereview.com/