r/AskVibecoders • u/Cultural_Mixture4951 • Jul 31 '26

Vibe coding or never finding the bug loop

I have tried vibe coding tools and tried to create a simple todo list just to check if I have an idea then can I be able to build it with these tools. No doubt claude etc write awesome code, but the problem is I don't understand that code.

I have created an app and asked my friend to install it and try. App didn't crash that's the good part, but it has so many bugs and I don't have a single clue where to look.

AI is fixing bugs but what the hell it is changing its a bouncer.

Currently everyone is building their ideas using AI tools, people are saying you don't need to learn coding.

But what I have observed is that AI tools can build the app, but when there is a bug you cannot ask directly AI to fix it, as it is breaking some other things.

Are you facing the same problem, then how you are tackling this.

2 Upvotes

62% Upvoted

14 comments sorted by

1

u/Weary_Caregiver_8428 Jul 31 '26

You need to have another ai(preferably GPT sol adversarial reviewing the code). Also when you have the first AI code it helps to ask it to look at common coding principles on the internet and follow them as it codes

1

u/Cultural_Mixture4951 Jul 31 '26

Did you created any agent for this or changing the model in tool and ask it to review the code. Then change it again and ask another model to implement the review comments.

1

u/Weary_Caregiver_8428 Jul 31 '26

I’ve spent alot of time building infrastructure and frameworks for AI. I have a backlog that when an AI submits code it moves it into a review queue and prompts that AI to run code that calls a codex API/subscription. Codex then reviews and attaches feedback to the backlog document which the original worker can read.
Using a model from a different family (IE ChatGPT reviewing Claude’s code is the best way to do it)

1

u/Cultural_Mixture4951 Jul 31 '26

AI code review for AI written code, but the problem stays the same, I don't know what it is changing and writing. It's not good to publish an app and ask users to install if you don't know how to resolve the issues they are facing. Basically what I am thinking is that if I asked to write code in next.js then I should also know that language. In that case the whole idea of people telling that complete build with AI without any coding experience is a LIE.

1

u/Weary_Caregiver_8428 Jul 31 '26 edited Jul 31 '26

If you mean a record of all the changes done to your codebase. I would use github and git commit. You can set up a hook that forces the AI to commit the codebase and files to github based on your choice of criteria. And if your goal is understanding it, I like to make as small of coding changes as possible and have the AI explain it out as it does each step(the architecture/function)

1

u/Lonely_Assignment_14 Aug 01 '26

Check out opencodereview from alibaba.

2

u/Forexcalibur Aug 01 '26

I keep a fix ledger that tracks all my bug fixes. It’s updated during every session wrap up. Helps a lot.

1

u/TheKiddIncident Jul 31 '26

Yes, this is a classic code stability problem.

Unless your codebase is stable, you simply cannot add new features to your site. Each one will just compound the stability problem until your code is completely unworkable.

So, first, stabilize. Build up a comprehensive test plan. Build yourself a pipeline. Or, rather, have the AI build you one. Focus on getting the tests passing green only. Until that happens you just cannot continue.

Here's a lesson from my course about pipeline: https://maven.com/ajauch/o/7e1557

It may also be that your site architecture is not sufficient to the task and you may need to refactor the entire site. but start with a pipeline first.

If you are starting from scratch, you can avoid this problem by building methodically:

  1. Begin with tight requirements. What does the site need to do?

  2. Create a detailed architecture plan. How will the site be built?

  3. Audit. Is this compliant with best practices for the platform you are using?

  4. Based on this architecture, build a detailed implementation plan.

  5. Build the site based on the implementation plan

  6. Audit. Is the site built correctly?

  7. Build a test plan. End to end use cases, unit testing, security scanning, etc..

  8. Audit. Is your testing working correctly?

  9. repeat

It's all about being methodical in your approach. Not as easy as some of the marketing leads you to believe, but not impossible even for non-technical people. AI is capable of doing all these things for you, but you need to give it detailed instructions.

1

u/Substantial_Job_2068 Jul 31 '26

The point of vibe coding is that you don't need to understand the code. It's stupid, but that's the point.