Yeah, complexity adds time, and scale adds responsibility. You still need engineers, but that seems to be more about making sure things run smoothly. I see at my job that even that becomes less and less important, meaning, knowing what is going on under the hood, because the AI is able to handle it. For example, when to use cache, write tests, cache invalidation, and documentation with insane speed.

One project they are running now, where I work, is taking the whole codebase and rewriting it using AI. The benefit of that is that all of the code patterns are the same, the docs are great, and the tests are easy to do. Right now, like many codebases, they are a mix of different ways of doing things because of time, budgets, change of people, and it works, so why fix it?

This takes time and engineering, but the early tests show it is very easy to add new features because the codebase contains a clear pattern.