I think the jump from "we should be welcoming to newcomers to the field" to "therefore accessibility doesn't matter" is not supported by what I said.
I think the jump from "we should be welcoming to newcomers to the field" to "therefore accessibility doesn't matter" is not supported by what I said.
I think "we should be welcoming to newcomers to the field" is a very different statement than "there are no fundamentals" and "telling AI to write code for you is coding."
Welcoming newcomers would mean encouraging learning and making that easier. That's not what AI is.
On that we continue to disagree.
It's weird that your publicly stated stance is that coders should not learn how to actually write code.
I don't think that's true right now. LLMs are too unreliable, they will still need to learn enough code to verify the outputs. But even if eventually the code becomes abstracted away then they will learn other aspects of programming, like structured problem solving, repeatability, scalability, etc.
There is more to development than the mere ability to type out code.
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.