You don't forget CS concepts so easily, but all the syntactic tricks of new language variants and working set vocabulary of APIs, data formats, and frameworks keeps churning away from whatever you last had contacted in a real, hands-on way.
It is fascinating, wondering where this is going as programmers turn into their own middle managers on top of agents. Particularly, the school who claim that you don't really need to understand all the code and instead treat it like a black-box experiment. If this fad takes over the main stage, then everyone becomes one of those less technical managers.
But, in this new scenario, there is no human in the loop to inject judgement calls and "manage up" anymore. There is no programmer culture except the models and agents, which don't really have the same social connections to drive a programming culture. What will happen? A culture per agent product? Per enterprise client of the agent vendor? Per agent operator? Per codebase?
About half a year ago I noticed there were no people called 'Agile something' at our org, so I asked about it. They looked at me like I was a space alien. I remember, it was like 3 years ago that management bet the house on 'Agile transformation' talking about how Agile practices are the bread and butter of a good organization.
Now they're talking about AI the same way.
The memo has NOT gotten around, though AI now makes it easier to make all the various slide decks and schedule all the 50+ person meetings that power this process.
Negative value to the project, perhaps; but if these "software architects" are kept around despite several rounds of this, it may be because they're providing positive value to the company, in terms of:
- being able to provide the executive team corroborating evidence to show to investors to convince them that they're acting strategically in the market; or
- where the existence of the project, no matter how failed, serves as collateral to get breathless puff-piece articles written about the company in places where dumb CTOs/CIOs who make IT buying decisions will read them (and not necessarily buy the product that came out of that project — hopefully not! — but remember the company itself the next time they're comparing vendors for something else.)
I regularly meet (recently examined) people who are trained "software architects". Common among them is that they are often delay projects championing their pet idea, sometimes bringing negative value to the project. The best programmers are just so much better software architects also. So I expect history to repeat at this point.