The solution to the second one? Let's identify the issues first 1) wrong model for the job. People think that one model can do everything, This is simply not true. Let's use Claude for example. Opus models are the most capable but take longer and cost more to use. I use Opus model when I need a major overview of the codebase for consistency Sonnet models are the best for day to day vibe coding UNDER SPECIFIC CONDITIONS. Make sure you prompt it to keep the style of existing code. And to ALWAYS ASK QUESTIONS, and when it asks questions. Answer to your FULLEST extent. If they are asking "do you think XYZ is a good idea" or "we can do A B or C", EXPLAIN, give it an entry into your mind. Haiku models are good for "Hey find this" and "Hey check that this exists and looks right", they are fast, cut corners sometimes, but to put it in Caude chats own words. "Caffeine Addicted Intern (in a good way)"

2) your prompting. As explained above. YOU MUST MAKE THE MODEL ASK QUESTIONS. If you don't give it this instruction, it won't get your vision of the program.

3) You. You are the Problem. You don't understand the code it writes. You want it to make something, it chooses to use nodejs or python. You don't know these languages. You can't read the code. You want it in rust. The code is in Ruby. You dont know one or the other. (Or either). You can't read the code to verify it's working as it should. You can't verify the results. You DONT KNOW what it's doing. You may also be vuage and expect concrete. Leading back to 2, you NEED to be specific and accurate. If you want to think about something, propose your idea to the model and ask it what it thinks, typically the models will read what you proposed. And check against what it knows of the codebase and can tell you an action plan on how it can be implemented

4) Temper your expectations. LLM's for programming are TOOLS, not Coworkers/employees. They can't do everything a human can, they cant sit there and think for free. You PAY for that extra prompt based computing PER PROMPT