Maybe, but that's a bet I'm willing to take.
Here's the rub: if my competitors are going to realize "massive productivity gains," where are those gains actually coming from?
Are they coming from the time it takes to type? No, because typing is a small portion of the time we spend as programmers.
Are the gains coming from the time spent on design and architecture? Maybe, but that means my software will have better architecture, and I will have better velocity in the long run. (I have real-world experience with this, by the way; it takes me, on average, less than an hour to fix bugs in my bc nowadays. Architecture matters for long-term velocity.)
Are the gains coming from the time squashing bugs? No, this is where AI would decrease productivity because you have to carefully review outputs to ensure there are not any bugs.
In essence, the productivity gains will only happen the less that my competitors actually review and clean up the code from these tools. The less they do that, the lower the quality. The lower the quality, the slower their long-term velocity will be.
"A little bit of slope makes up for a lot of y-intercept." [1]
[1]: https://gist.github.com/gtallen1187/e83ed02eac6cc8d7e185