upvote
The cost of AI is rapidly falling while its engineering capabilities keep rising. This implies that code is becoming more fungible, and you should expect any code you write today to mostly be replaced in the near future.

The requirements will be more stable than the code. Focus on them instead.

reply
Robust systems experience very little turnover in nearly every non-software discipline that involves systems. Why the hell would we insert risk into our system-building processes by needlessly turning over code?
reply
> The requirements will be more stable than the code.

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.

reply
> The cost of AI is rapidly falling while its engineering capabilities keep rising.

Wouldn't count on it. There likely is a ceiling, we might or might not be near it.

reply
Definitely with the cost. I strongly believe the price now is heavily subsidized and will shoot up in the future. (Not new. First hit is free..)
reply
> The cost of AI is rapidly falling while its engineering capabilities keep rising. This implies that code is becoming more fungible, and you should expect any code you write today to mostly be replaced in the near future.

I have code I wrote in 2006 which is still in daily use adding business value at my company. Why would it need replacing?

reply
> This implies that code is becoming more fungible

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?

reply
it's amazing that you could read a book like "The Design and Implementation of the 4.4 BSD Operating Systems" (1996) and still find it relevant to browse the code of OpenBSD and NetBSD, three decades later. While good software gets plenty of updates and additions, the core ideas barely bulge over time. A lot of churn is people playing around with no reason instead of solving the problem properly the first time.
reply
A shift is realizing that refactors go from something that was costly and infrequent to something that can happen inexpensively and frequently. It takes some rebalancing.

I recently used agentic processes to bring a young codebase to a functioning state very rapidly. This forced discussions about design principles that were folded back into a short document in the repo which then led to a major refactoring plan, and a massive pruning of code that was written the week prior. There are solid engineering approaches in the codebase now that wouldn’t have been achieved without this discovery process.

reply