We need to consider the variation in the problem spaces of top 10%, top 25%, and the long tail of software engineers. Engineers doing nothing more vanilla start

We need to consider the variation in the problem spaces of top 10%, top 25%, and the long tail of software engineers. Engineers doing nothing more vanilla starter NextJS projects might be at the highest risk for their skillset eroding to technical advancement. I remain unconvinced that people working on systems that evolved over a decade or more, with microservice spaghetti, can truly leverage things like ChatGPT. If I'm on a greenfield project or want to generate something new, sure. Until I can say "migrate this AWS account to GCP and/or Azure, and update all of the deployment tooling for the hundreds of repos supporting it, and update the DNS records too" -- something that might take teams of engineers within large organizations a quarter or more to figure out, no, I don't feel at risk. The degree of ambiguity in the spaces we operate in (eg: the top 25% of software engineers) are far too great for this sort of technology.