> This style of learning is hands on. You learn a little bit about the shape of the problem before you sit down and learn the theory. We're talking about getti

> This style of learning is hands on. You learn a little bit about the shape of the problem before you sit down and learn the theory. We're talking about getting some project or task done. It's a practical exercise by definition. Any learning experience to be had is going to be hands on, and for student/junior-level tasks, it's not going to be some product of knowing deep theory in the first place. But the process of identifying the boilerplate that needs to be written, the process of manually entering it, the process of debugging your own code that you wrote, the process of scouring for examples and explanations, the process of being held accountable in a teacher or colleague's review, the process of discussing your experience of the task with someone who already understands it well... these all provide extra opportunities for hands-on learning that are short-circuited when having an AI put it together for you. Yes, script kiddies and VBA/Excel junkies in the sales department have been slapping together programs they didn't understand for decades, and many people have now joined the industry thinking that they might secure a career as an "engineer" by following tutorials well and pasting StackOverflow snippets efficiently. And while some people who found themselves starting on that path have eventually come to transcend it and learn fundamentals more deeply, the "slap it together" mentality, the "find a tutorial" mentality, and now the "have a chatbot do it" mentality easily become quiet traps for people who don't realize that they need to actively transcend them at some point. You can genuinely learn a lot about football by playing Madden on your couch, but if you don't get out on the field and actually play some games, your dreams of making it into the NFL are probably not going to pan out.