> code is getting less and less important in our team, so we don't need many engineers.

That's a bit reductive. Programmers write code; engineers build systems.

I'd argue that you still need engineers for architecture, system design, protocol design, API design, tech stack evaluation & selection, rollout strategies, etc, and most of this has to be unambiguously documented in a format LLMs can understand.

While I agree that the value of code has decreased now that we can generate and regenerate code from specs, we still need a substantial number of experienced engineers to curate all the specs and inputs that we feed into LLMs.

> we can generate and regenerate code from specs

We can (unreliably) write more code in natural english now. At its core it’s the same thing: detailed instructions telling the computer what it should do.

Maybe the code itself is less important now, relative to the specification.