lol okay dude. Flippantly you ignored all of the limitations I pointed out. Sure it could happen, but not on the timeline you’re discussing. There is no way within a year that they have replaced software engineers, I call absolute BS on that. I doubt it will rise above copilot within a year. I see it being used alongside code for a long time, calling out potential issues, optimizing where it can, and helping in things like building out yaml files. It cannot handle an entire solution, the hardware doesn’t exist for it. It also can’t handle specific contexts for business use-cases. Again maybe, but it’ll be a while - and even then our jobs shift to building out models and structuring AI prompts in a stable way.
My attitude is the same because these are the same issues that it’s faced. I’m not arguing that it’s not a great tool to be used, and I see a lot of places for it. But it’s naiive to say that it can replace an engineer at it’s stage, or in the near future. Anyone who has worked with it would tell you that.
I firmly do think companies want to replace their 250k engineers. That’s why I know that most of it is hype. The same hype that existed 20 years ago when they came out with designers for UIs, the same hype when react and frontend frameworks came out. Python was built to allow anyone to code, and that was another “end of engineers”. Cloud claimed to be able to remove entire IT departments, but those jobs just shifted to DevOps engineers. The goalposts moved each time, but the demand for qualified engineers went up because now they needed to know these new technologies.
Why do you think I worked with AI so much over the last year? I see my job evolving, I’m getting ready for it. This has happened before - those who don’t learn new tech get left behind, those who learn it keep going. I may not be coding in python in 10 years, god knows I wasn’t doing what I was 10 years ago - but it’s laughable to me to think that engineers are done and over with.