Just in case: This is not a call for everyone to "pair program" with an AI.

If you pair program with someone else on your team, you both learn what the other is thinking. You both become more familiar with what the code is doing, and why it's doing it.

If you "pair program" with an AI, anything it learned, it forgets as soon as the prompt is closed.

So don't think that's what he's talking about here. He's talking about XP, with humans, just like in the 1990s. There may be some AI in there too, but that's not where the XP part comes from.

That's only if you don't preserve the results explicitly. If you're trying to delve into some new code without enough docs, I could imagine learning lots about the system along the LLM and then leaving that as documentation and/or agent files in the repo.

> Just in case: This is not a call for everyone to "pair program" with an AI.

If that's not what you're doing, you're likely doing it wrong.

> If you pair program with someone else on your team, you both learn what the other is thinking. You both become more familiar with what the code is doing, and why it's doing it.

Yes.

> If you "pair program" with an AI, anything it learned, it forgets as soon as the prompt is closed.

Same with humans, including your future self. So pair on docs.

TL;DR: You should absolutely be XP pair programming with your LLM.

100%