No, I'm saying to use AI as what it is, a tool for debugging.that's a bad analogy. You're trying to say that you don't need to learn problem solving or bug fixing because of ai. That's like not knowing how to build and relying solely on the drill insteadDoesn't mean that AI isn't just a tool.doesn't mean that problem solving and bug fixing is not a part of coding. it's like saying “Grammarly exists, so grammar isn't really that important”Programmer here, AI is used a ton in problem solving.problem solving and bug fixing is part of coding, in order to program that's a skill you have to learn.Scratch is such an easy language to learn, what do we need ai for?In order to try to problem solve in a more direct way than tutorials and schools can?
Should we use hammers for everything, when many things benefit from drills?
What I'm saying is that those are vital skills. Do whatever you want after you're done learning, but not as your learning it. We use calculators after we learn basic equations, but that doesn't mean that we should use one when we first learn it
I'm saying you should learn to use AI to troubleshoot. AI is used to guide you in the right direction.
You may not use a calculator early on(I know most higher level math classes, you immediately learn how to do something on the calculator first), but you use formula sheets, you use a sheet of scrap paper. Same thing here. AI doesn't fix the problem for you. It guides you in a direction. Unless you were born knowing how to do probability distributions, of course.
Using AI to generate code, that's just big fixing. And most AI generated code either barely works, or requires major tinkering to implement. That is, knowing if you're better off using screws or nails.