I've always thought that when you debug your code, in many ways you're not debugging the code, you're debugging you.
The code just does what it says, but if you wrote it and it does something you didn't intend or expect, then that's a bug in you, not the code.
It's a bug in your understanding. In your world-model.
And as you step through the code, see how the variables actually change, and get that aha-moment, that's when you've found your bug.
You fix the code, but before that could happen, the code - stepping through the code - fixed you.
It's the process. The process of coding, the process of debugging, the process of writing - we tend to focus on the external artefacts: the resulting code, features, blog posts, books. But as important, and maybe even more important, is what happened to you when creating these things: you grew, you learned.
And that is why, even though you can create external artefacts, great beautiful artefacts, with AI, doing it that way robs you of the building-of-you.
I love using AI, for coding, for brainstorming, for writing things I don't want to write, but I am mindful that while some things are done purely for the outer effects, others are done for the growing of me.