Well, I am not sure why this is confusing. Engineers do things the rest of the company don't understand and everyone depends on. Removing dependencies and lac

Well, I am not sure why this is confusing. Engineers do things the rest of the company don't understand and everyone depends on. Removing dependencies and lack of clarity are two principles you would apply to your own code base. The Human stack, like you called it, is doing the same with the company and staff : remove dependencies and increase clarity. I am not saying this is the correct approach, but this is the approach. At the same time, we can understand that real product building and architecture require more than codegen, with or without AI. Generally, I look at the AI recent progresses similarly to what spreadsheets did to accounting a long time ago. It removed a lot of the dummy work and make everything more efficient. But we still need accountant and they are not wasting their day doing basic math. Of course the one who knew only how to make fast math but not accounting or business logic didn't make the cut on the long run, but I don't think anyone would want to come back to accounting like it was 60 years ago.