Because you will have an understanding of the complete system. Your domain and the code. This means that you can be more creative with it and also get yourself out of a mess if it occurs (which it will).
From what I have seen AI doesn't understand the code. But even if you argue that it does understand the code it definitely doesn't understand the domain because it's only input channel is a stream of text and you didn't even type in a "full" text representation of the domain.
So you remain the only thing that can understand the whole system. If your competitor has no one (or no team) who can put together a full understanding of the system then you will have an advantage.
From my experience building different systems, there is no moat anymore ( beside your commercial connections for B2B). If one lack understanding of a domain, he will get it by testing the system.
So basically nothing has changed from before AI.
You will have a good understanding of a system which is 20 times smaller in size/features.
For a todo app that is fine. But for most projects your competitor will leave you in the dust with the speed at which they add features.
Same story, 25 years ago:
> But with Lisp our development cycle was so fast that we could sometimes duplicate a new feature within a day or two of a competitor announcing it in a press release. By the time journalists covering the press release got round to calling us, we would have the new feature too.
What happens when the biggest feature that can be touted is concrete objective metrics about bugs/uptime/quality-stuff? Can't slop your way to having the "crafted with love and care, no bugs in production in the last 2 years" feature.
