When people hear that I use AI while coding, one of the first assumptions they make is that AI writes everything for me.
It does not.
If anything, AI has changed how I learn, not whether I learn.
As a student, I am constantly switching between different subjects, projects, and technologies. One day I am working on a Java application, the next I am debugging embedded C code on an ESP32, and a few days later I am trying to understand how a website should be deployed. In the middle of all that, AI has become something I rely on, not to do the work for me, but to help me understand it better.
Learning without feeling intimidated
One thing I appreciate about AI is that it never gets tired of questions.
When I first started learning HTML, even the smallest concepts felt confusing. I would wonder why one tag behaved differently from another or why something was not appearing on my webpage. Instead of spending hours jumping between websites trying to find an explanation that made sense, I could ask AI to explain it in simpler words.
Sometimes I would ask the same question three different ways until it finally clicked. That freedom to keep asking why without worrying about asking a silly question made learning much less intimidating.
Debugging is still my responsibility
If you have ever programmed before, you know that writing code is only part of the process. The real challenge usually begins when the code does not work.
Whenever I get stuck, AI often helps me identify possible reasons behind an error. Sometimes it is a missing library. Sometimes it is a logic mistake. Sometimes it is simply that I have overlooked something obvious after staring at the same screen for hours.
But I have also learned that AI is not always right. There have been times when it suggested functions that did not exist anymore, libraries that had changed, or solutions that did not fit my project at all.
That is why I never stop at the first answer. I test it. I read the documentation. I compare different approaches. If something does not make sense, I ask more questions until I understand why a solution works instead of simply copying it.
Breaking down complex topics
One thing I have noticed about engineering is that many concepts seem impossible until someone explains them the right way.
Whether it is object-oriented programming, embedded systems, communication protocols, or machine learning concepts, AI helps me break large topics into smaller pieces that are easier to understand. Instead of trying to learn everything at once, I focus on understanding one idea at a time. That approach has made learning much less overwhelming.
Brainstorming projects
Some of my favorite conversations with AI are not about code at all. They are about ideas.
I will often discuss different approaches for a project, ask what could be improved, or explore different ways to solve the same problem. Sometimes those discussions lead to completely different ideas than the ones I started with. It is a bit like having a whiteboard session whenever inspiration strikes.
Improving my writing
Coding is not the only skill I want to improve.
As I have started building projects, I realized that being able to explain them clearly is just as important. Whether I am writing documentation, preparing project reports, publishing blogs, or updating my portfolio, AI helps me organize my thoughts and communicate them more effectively. The ideas are still mine, but AI often helps me express them more clearly.
Learning faster does not mean learning less
One criticism I often hear is that AI makes students lazy. I understand where that concern comes from. If someone copies code without trying to understand it, they probably are not learning much. But that is true even without AI.
Copying code from a tutorial, a forum, or a friend does not magically teach someone how to program. The real learning happens when you stop and ask yourself questions. Why does this work? What happens if I change this? Can I build it differently?
For me, AI simply makes it easier to reach that stage faster.
AI does not replace curiosity
The more I use AI, the more I realize that the quality of the answers often depends on the quality of the questions. A vague question usually leads to a vague answer. A thoughtful question leads to a much more useful discussion.
In that sense, AI has actually encouraged me to become more curious. Instead of accepting the first explanation, I find myself asking follow-up questions, exploring alternatives, and understanding concepts more deeply than I might have otherwise.
My biggest lesson
Perhaps the biggest lesson AI has taught me has very little to do with technology. It is taught me that learning is not about knowing all the answers. It is about knowing how to ask better questions.
AI can explain concepts. It can review code. It can point me in the right direction. But it cannot replace the satisfaction of finally solving a problem after hours of debugging, nor can it replace the understanding that comes from building something yourself.
At the end of the day, every project still requires curiosity, patience, and persistence. AI just happens to be one of the tools that helps me along the way.
