Questions tagged [pair-programming]
Questions related to pair programming, a software development technique in which two developers work together at one computer workstation and simultaneously write and review code to speed up the development process.
1
vote
2answers
351 views
Bringing up a slow colleague in a nice way
I am a mid-level developer and leading a project at my company. I am very strongly encouraged to pair with another dev who is relatively new (half a year now). He is a good guy, but working with him ...
62
votes
20answers
24k views
How should I react when a co-worker says his 3000 line method is optimized? Should I report it to my boss?
I have a co-worker who said his 3000 line method is the most optimized possible. How do I react professionally to that?
Should I communicate this to the boss, who does not know anything about ...
9
votes
2answers
1k views
How to become more receptive to ideas as member of a mob programming team without going against my values
At the company I work for we have just started mob programming, where the team of three that I am a part of all write the code for our project together at one keyboard, and we only proceed if we all ...
6
votes
3answers
205 views
How should one be encouraged to ask to work in pair on a task which appears complex enough?
I'm working with a team of five developers working on a software product. The tasks range from very basic to rather complex.
There is no rule making it mandatory to use pair programming. The current ...
-1
votes
2answers
433 views
How many hours should we programming at the work? [closed]
For years this is a question for me, because I work like freelancing and coding at home. I do it like this:
1 to 1.5 hours coding, 1 or 2 hours free time. then repeat like that. Maybe I repeat this ...
5
votes
1answer
798 views
Pair programming: A year with the same pair
About a year ago, my team leader decided that she would start delegating tasks for me and a colleague to tackle as a pair. It started out just fine, it was our first pairing job, and we were trying to ...
