Big tech is slow to adopt things, though, especially large corporations.
Also there's potential legal or copyright issues with A.I. generated code so I haven't dared use it at my job, for example. We already have to get explicit approval for any third party package we use, and that approval can take months.
Not only that, but I also don't dare describe anything about the company's business logic into these things because there's potential privacy and security concerns, and the company is super paranoid about all that.
This company is still trying to finally retire their (20? 30? years old) mainframe computers, as an example of how slow things can go.
And even if people use A.I., they have to learn a whole new language of how to coax it to get the results they want. They already struggle to clearly state requirements to engineers as is, or seem to not really know what they want there. And these same people often struggle to even use Excel half the time.
This fear kind of reminds me of the outsourcing fear a couple of decades ago. Everyone thought that engineers in the U.S. were totally screwed, that all engineering would be outsourced, because it's cheaper elsewhere. I was also worried, as I was in school studying this right as all those predictions were flying about.
Well a bunch of corporations did try to outsource everything, and the quality of their software suffered enough that they were eventually forced to roll back a good chunk of their outsourcing (not all of it, of course, I have three offshore devs on my team right now).
I suspect it's going to be that way with A.I. as well. A.I. will be able to handle things to a certain extent, but be terrible at the complex business logic and vague requirements and stitching all sorts of technology together in a holistic way, for quite some time. And businesses will get all excited about saving money and jump onto A.I. coding everything, and make a big old mess out of things, and then they're going to have to hire skilled engineers to untangle the messes or just plain rewrite major chunks of it.
Eventually that might not be the case, but I think all this taken together is going to slow things down enough that I can probably still count on retiring as an engineer, if I wanted to (I'm starting to really not want to).
I can see life getting harder for junior engineers in the near term (less than five years), but I think it's still very early to be all that worried about most engineers jobs. Although a year ago I would have put that timeline out 30-40 years. Now I'm willing to believe it could be 10-20.