> I can only truly do that if I write it myself.

That's where you're wrong. AI can debug code better than humans. I put it on a task that I'd spent months on: debugging a distributed application which had random errors which required me to comb through MBs of logs. I gave Claude the task, a log parser (which it also wrote), and told it to find what each issue was. It did the job in a few minutes. This is a task that was, frankly, just a bit above my capacity with a human brain as it required associating lots of logs by timestamps trying to reconstruct what the heck was going on.

My new worry is that I need to make sure the code AI is writing is more comprehensible not to other humans, but to other AIs in the future, since there's very little chance humans will be doing the debugging by themselves given how bad we are at that compared to LLMs even now, let alone in a few years.

> but I should also get something

What do you want beyond a pay check? If you want to get better at your job, the most important technique you can improve right now is hands down how to interact with an AI to solve business problems. The learning you're thinking of, being able to fully understand code and actually debug it in your head, is already a thing of the past now. In a few years, no one will seriously consider building software that's not entirely AI-written except for enthusiasts, similar to the people currently participating in C obfuscated code competitions. I say this as someone who reluctantly started using AI in anger only a few months ago after hating on it before that for the laughable code it was producing just around 6 months ago (it probably was already good by then but I was not really giving it a chance yet).