RSS feed [root] /software_engineering /weblog /team



title search:


Thu Nov 03 23:39:44 GMT 2022

pair programming

How work alone might be better than pairing -[..]/03/pair-programming-considered-harmful/

When to pair, when not to -[..]ramming-the-disadvantages-of-100-pairing

This is an excellent arguement -

It's only worth pairing on complex code, rote code yields no advantage.

I think there is a point to this - pairing is about improving design and minimizing mistakes. Rote code that's simple to write yields little opportunities for pairing to make a difference.

Except this: writing boring rote code is a smell. If I'm writing boring repetitive code it's usually a sign that I've missed an important abstraction, one that will drastically reduce the amount of rote code to write. Pairing will help you find that abstraction.

Common pitfall of pairing

Look like a good way to start pair programming[..]02/13/pairing-pattern-ping-pong-pairing/

Discussing pair programming -

Experience sharing of working with expert - here is the disclaimer of the blog

Why pairing -[..]n/opinion-on-the-technion/#why_pair_wise

Pair Programming smells
- Unequal access
- Keyboard domination
- Pair marriage
- Worker/Rester
- Second Computer
- "Everyone does their own work"
- 90% of work 90% done
- People who can't stand to program together
- Debates lasting more than 10 minutes without producing new code
Pair-programming smalls -[..]com/2009/02/pair-programming-smells.html[..]ir-programming-disadvantages-of-100.html[..]012/08/08/in-praise-of-pair-programming/

Programmer Pairing with a Tester -

Showing how pair programming is better than traditional code review -[..]ment/design/code-reviews-with-five-whys/[..]code-review-try-mob-instead-82149ef035df

(google search) (amazon search)
download zip of files only