You still communicate in code and fix the errors.

> You still communicate in code and fix the errors.

But you just said

> Coding as a skill won't be that important.

So coding is only important if you need to make your software actually work, I guess?

I just said its not that important. Your time won't be spent coding but rather fixing stuff here and there.

... so how are you supposed to fix things without coding, given that you admitted you need to dive into the code to fix things?

Its not a binary - we will spend less time thinking about code and occasionally fix things and more time on higher level abstractions.

Just like I sometimes need to understand and dive into assembly but not always. Its a spectrum and the value in the spectrum changing has consequences for how we work.