Wouldn't count on it. There likely is a ceiling, we might or might not be near it.
These kinds of changes to the way teams are formed and managed, and how products are developed is what really fascinates me about the impact of coding agents.
Even if it works, for some definition of works, to dump a huge spec into a coding agent context window, I suspect this is where a lot of horror stories about agentic coding come from.
Teams, and the management structure above them, are going to have to get used to more collaborative and iterative product definition and development in order to extract the most value from coding agents.
I have code I wrote in 2006 which is still in daily use adding business value at my company. Why would it need replacing?
As is a lot of newer code. Depends on the threat model
> Another reason is that if you can find a better way to accomplish the goal, then you should eventually switch to it.
If it's financially better and the gains outweigh the risks, sure
> If your code from 2006 is already perfect and there is no room for improvement
Or more realistically if the cost of improving it would be higher than the business benefit gained from improving it
> which is that any code from 2006 that you’re running has survived the quality filter of time
Not really, it's terrible code. But it does the job, because it was written to solve a business problem, not written to make beautiful code.
Code has always been fungible, in the sense that it could be refactored.
> you should expect any code you write today to mostly be replaced in the near future
Why on earth do you think this? It does not follow from your other points. Just because you could turn your business into a rube goldberg code juggling machine, why would you?
Otherwise you still end up with balls of spaghetti where each change takes longer and longer to work into the codebase. With a bit of planning, you can keep tackling changes and they keep taking the same amount of time more or less.