Does Pair programming mean you don't need design documentation? [closed]

Question

In pair programming, the experience of every member of the team can be spread to new member. This experience is always in sync with the code, because the "senior" of the pair knows how the code works and what the design is.

So what is the utility of design documentation in this case ?

UPDATE

I don't imply no design, I imply no documentation. With a team which practice pair programming I think that everybody is disposable, because everybody knows the code. If the senior developer leaves, I think that there is always at least one person who knows the code, because the experience was shared before.

Answer 1

What if your team is larger than 2 persons?

Just because two people know a part of a system does not mean it shouldn't be documented.

And I would be glad to know that I don't have to remember every tiny detail of a system just because it it's stored nowhere else than in my head.

For a small system this might work, but as the system gets larger, your limiting yourself and your colleagues. I'd rather use the memory capacity for a new system than to remember everything of the old system.

Answer 2

Have you ever played "telephone?" I don't think you should play it with your codebase.