On that, I agree. In fact, I'd argue that the typing of the code is the least important part. But in order to do the other, more important things, you need to actually understand how code works and the medium you build for. i.e., the fundamentals!

I do not understand how chips work past a very superficial level. I do not understand how my operating system kernel works. My understanding of what a browser does with my code is pretty rough. And yet I am totally capable of making websites. Some things get completely abstracted away.

Code is certainly not yet fully abstracted away but can you at least agree that it conceptually *could* be?

Far future abstraction is not relevant to modern discussion. A coder in the 70s had to know how to poke holes in cards. Telling them they won’t need to know that in 20 years would have been irrelevant and actively harmful to their learning at the time.

Okay, so now we agree that it *could* happen and merely disagree on the timeframe in which it might happen. I think it's already happening, you think it might never. Agreed?