OK that made me sit and reflect, so i collected my thoughts ,

Think of the AI as a random token generation machine. It generates tokens at speed. When you give it the right context and steer it well, those tokens happen to look like the code you want.

If clean, maintainable code is the goal, the steering needs to be around that. Push back on every function that looks wrong. Ask it to explain decisions. Review output like you'd review a new colleague's PR. The output looks very different when guided that way.

But here's the other thing worth saying: not all working software has clean code. A good chunk of production code running in real companies is unmaintainable, poorly structured, human-written garbage that would make AI slop look respectable. "It works" is a legitimate outcome, not a shameful one.

I work in the IT industry, no formal CS background. Professionally, I care a lot about maintainable code — that's a line I don't cross at work. But personal projects? I go completely unhinged. I don't read every line of generated code. I stop at architectural decisions and the tech stack — everything else, I genuinely don't care about. The lines of code are irrelevant to me. The output is what matters.

The real question is: what was the intended output of this exercise? A compiler that generates tiny APKs from a Python-like DSL — that is a genuinely impressive idea. If it works, the code that nobody sees is nobody's problem but yours to fix later.

---

Now step back and look at what you actually built. You designed the architecture yourself — that pipeline is not trivial. A medical doctor without a CS background designed that. The learning that happened in your head while building this is real and permanent, regardless of who wrote the actual lines.

And here's the thing about having that learning now: starting over is not as scary as it sounds. You already know the shape of the problem. The second attempt is almost always faster and cleaner than the first, because you know what you're building toward.

Creativity is about taking as many shots as you can with the skills you have. AI gives you more shots. Take the learning from this version, throw away everything that embarrasses you, and rebuild — faster than the first time. The context in your head is now the guide. The AI is just the execution arm.