The skill of finding errors is actually a very useful one. I can count on one hand how many times I've made similar mistakes in code, after 3 hours staring at i

The skill of finding errors is actually a very useful one. I can count on one hand how many times I've made similar mistakes in code, after 3 hours staring at it that lesson really sticks and you don't make it again. When an algorithm tries to fix it for you you only learn how to send the code to the algorithm to fix it for you. It's convenient in the moment for sure, but you haven't learned how to fix your own code and won't know how to fix it when the algorithm is the cause of the error. That also ignores secondary risks, like giving your codebase to a nonprofit / very much for profit company. That isn't always possible depending on the codebase, and in general why bother giving them access to it when you instead learn how to find your own missing semicolons? Why spin up a pipe of GPUs and burn all that power rather than learning to do it yourself?