"Looking over your shoulder" was just a figure of speech, not a literal description. And I suppose I could have grabbed the keyboard, but there's social nicetie

"Looking over your shoulder" was just a figure of speech, not a literal description. And I suppose I could have grabbed the keyboard, but there's social niceties to navigate, everyone likes their keyboard & IDE set up different ways, and it's generally a PITA. Also the way I tend to code is never linear in a way that anybody else could follow. I write something, edit it, throw it away, put it back, rename it, hack out something I _know_ is buggy so I can see how it looks, and basically "thrash" my way to a solution that I like. That makes it essentially impossible for anybody to follow in real time, and having them try to point out errors would be counterproductive. In the later stages someone could help polish it, but even then I think it'd mostly be a waste of time. That's before we even get to things like dealing with interruptions, or answering other questions quickly. Ideally interruptions don't happen, but in practice they do, and I don't want to be wasting someone else's time. There's a lot I liked about XP, but I still think that (for some people) it's just a great way to make two devs produce the output of one intern.