Yeah! A component of the value of pair programming is not only that they may be more correct than you about how to write part of the code but also merely that t

Yeah! A component of the value of pair programming is not only that they may be more correct than you about how to write part of the code but also merely that they have a _different_ way to write the code. That difference -- the juxtaposition of two approaches -- can generate meaningful insights even if _both_ approaches are individually wrong. We pair programmer almost constantly at my work, and I've grown accustomed to the feeling of "oh yeah, good point, I didn't think of that". Coding alone misses those moments. Copilot brings it back halfway (or quarterway, or eighthway).