Lately, I’ve been relying heavily on generative AI to help with my programming tasks. Whether it’s writing JavaScript or structuring entire modules, AI has become a go-to assistant. The results were impressive—faster delivery, fewer blocks, and the feeling of getting more done in less time.

But a few weeks later, I returned to one of those projects to make some changes. And it hit me: I had no idea what the code was doing.

Because I hadn’t written most of it, I had to trace through logic that wasn’t mine, layered in a structure I didn’t fully understand. It felt overwhelming. Not because the code was wrong, but because I had outsourced too much of the thinking.

I realized I had become dependent—not just on AI for syntax or suggestions, but for the actual logic and architecture of my work. I was skipping the hard parts, the thinking parts, the parts that teach you how to get better.

So I’m taking a step back. For the next month, I’ll minimize my use of AI for coding. Not because I think it’s bad—AI is an incredible tool—but because I want to reconnect with the craft. When something doesn’t work, I’ll try to figure it out myself before asking for help. I want to rebuild my own muscle for problem-solving, structure, and clarity.

Sometimes, progress looks like slowing down.