[Glyptodon]

My point of comparison of choice is overseas contractors, not pair programming.

Copilot or Cursor or whatnot is basically a better experience because you do not have to get on Zoom calls (after Slack has failed) to ask why some chunk of your system that cares about root nodes has mysteriously gained a function called isChild (not hasChildren) that returns a boolean based on whether or not the node has children and not whether it has a parent. Or to figure out why a bunch a API parameters that used to accept arrays now don't. Or why an ask to not show a constant literal in a menu resulted in algorithmic derivation of ordinals rather than using i18n.

With AI you probably don't have those kinds of things happen, but if you do, you can instantly tell it, sorry, that's wrong, this is why, and have it changed in a minute. Whereas with contractors, you waste a lot of time on things like communication and understanding gaps and language barriers that are mostly gone with AI.

The second you can interact really easily w/ AI from Jira Tickets, most engineers are going to turn into ticket writers and overseers for 80% of their work. (And yes, you'll still need engineers, because Product can't actually write decent engineering tickets, though telling the AI to write engineering tickets will probably get close, and because somebody with a clue needs to be in the loop, though many organizations will try to forget this and have things they don't understand go terribly wrong.)