Table of Contents

Programming in teams

A plea for pair-programming

The common pattern that I find in “bugs that make no sense” is that I am believing something that isn't true. Once I identify and challenge that belief, the bug becomes obvious. The reason that these bugs are harder to find in my own code is because I believe my code is correct, so I don't question it so closely. When I'm reading other people's code I have less belief that it is correct, so less hindrance to finding the bugs.

Put another way: finding a bug in my code is both a success and an admission of failure. Finding a bug in someone else's code is pure success. This sounds like a strong case for pair-programming!
Neil Brown, How to ruin Linus's vacation, LWN newsletter

Why program in a team?

What are the problems?

Suggestions

Sprint-based development
Communicating
Planning & Distributing

The Question of Leadership