I Use AI to Code. I Still Want to Understand It.

AI makes it easier to build software and other cool stuff. But I don't want to lose the ability to understand what I'm building.

I spent a long time writing code, reading documentation and figuring out why things broke you know the old reliable, belt to ass way. That process taught me more than how to get software working. It taught me how to reason through problems.

I could build faster and explore a lot more unfamiliar tools, and try ideas that would have taken much longer to implement. I wasn't interested in giving that up. I mean why would I I basically 100x my workflow. AI had become a useful part of how I worked making things more efficient and giving me more hands to deal with stuff since I'm an indie dev.

But once in a while I'd look at code an AI assistant had written and realise I wasn't entirely confident I understood it.

I could ask for an explanation. I could request changes and definitely If something broke I could ask the model to debug it.

But what happened when I needed to make a decision the model hadn't anticipated?

That question bothered me. I knew how to build software, yet I sometimes wondered how much of what I was building I could independently reason about. It brew up a new strain of imposter syndrome.

Working on code isn't the same as understanding what you are doing genuinely.

There's nothing new about developers using tools and abstractions they don't fully understand. Nobody knows every detail of every library they use and they shouldn't, most of the time it's not efficient you just have to know what you are doing

What feels different with AI is how easily we can move past the parts we haven't worked through ourselves. It give a dangerous sense of false mastery.

A feature works so we move on and forget about it. The implementation looks reasonable like senior dev code reasonable, so it's easy to accept it. We might not notice the gaps in our understanding until we need to change something or investigate a problem the model hasn't seen before.

I don't think using AI makes someone a worse developer. But we're still responsible for the software we ship, regardless of who wrote the code.

For me, the question isn't whether I typed every line myself. It's whether I understand the decisions that matter and can take the work further when I need to.

There's a particular kind of frustration that comes with building something successfully and still feeling unsure about your own understanding. 😂

You know you have experience. You've put time into learning your craft. Yet an AI assistant can produce a solution before you've had the chance to work through the problem yourself.

You might start wondering genuinely, Could I have figured this out without the model?

I've felt that tension, and I know other developers are thinking about it too.

I don't believe the answer is to stop using AI or return to doing everything manually. I want to keep building with AI. I just don't want my role to become accepting whatever it produces.

Some of the best parts of development come from questioning an approach or experimenting with an idea, even discovering or outsourcing a better solution could give some sort of internal satisfaction. I want AI to help me do more of that and not replace the thinking that makes it possible. Becuase creativity and ideas makes us human.

Sometimes another explanation isn't what you need

You might follow a tutorial and understand the example perfectly. Then you encounter a different situation involving several promises, and suddenly you're unsure what happens next.

Perhaps you understood the explanation. But could you apply the concept?

Those aren't necessarily the same skill.

Sometimes the magical missing piece is some concept you haven't understood properly. Sometimes you understand the individual parts but struggle to use them in a new situation. Watching another tutorial might help, but it might also leave the actual problem untouched.

I've become interested in what happens when we stop treating every difficulty as a request for another explanation.

What if, instead, we could identify where our understanding breaks down and work on that specific gap?

That question became part of why I'm building Vectra.

Vectra is my first project and its an adaptive learning engine designed to help people move beyond understanding an explanation to demonstrating what they've learned.

The idea is to check understanding and identify gaps in what people know Not just spam with explanations. Vectra's main philosophy resolves around adapting the learning process when someone struggles, rather than simply repeating an explanation and hoping it eventually clicks.

I'm still developing it but it's well enough for peoeple to try, and I don't want to pretend the problem is solved just because I believe in the approach. I want to keep exploring what genuinely helps people become more confident in what they know.

If you've ever understood a tutorial but struggled to use the concept independently, I'd love for you to try Vectra for free

I want us to build more, not understand less

AI has made a lot of things possible for me as a developer. I want to see where these tools take us.

Unfortunately speed isn't the only thing I care about.

I want to build things I can explain and most especially come back to and improve. I want to use AI without feeling that I've handed over the thinking along with the implementation.

And when I discover a gap in my understanding, I want to see it as something I can work on and not a reason to question whether I belong in software development.

That's the idea behind Vectra, and it's something I want to keep exploring as AI changes how we build.

How about you guys when you use AI to code how do you tell whether you truly understand what it has built? I want know what the rest of the community does your workflow might help out others that are struggling so let me know in the comments.

Everyone should have cool approaches to this problem mine was Vectra let me know yours down below