Well that's great for you. That's some knowledge that you will possess for the rest of your life.

I want a green lawn and big bushy shrubs in front of my house. Do I need to know the intricate biology of my soil and habitat? No, of course not. I just do the surface-level things that make the lawn and shrubs thrive.

I understand your point, but also imagine applying that across the whole spectrum of computing.

It's very useful that there's an intermediary that knows how that stuff works so I can build things without thinking about it in excruciating detail the whole time, I can dip down lower and learn stuff when it's relevant (like cache access and nested arrays) but I can also not do that in many situations.

There's also the argument that you can do engineering without understanding the underlying science as seen in th pyramids, the beautiful old european churches, etc

Who is more productive? A python dev who learns about x86 registers in his free time or one that uses AI at work?