The 60/30/10 rule, and why the 10 is the part that matters least in the mix! When I first learned how to actually think about an AI build I was not thinking ratios, ICM change that. Sixty percent infrastructure. Thirty percent orchestration. Ten percent AI. And I’ll be honest, when I first heard it, I assumed the AI would be the big number. That’s the part everybody’s chasing, right? It’s the smallest one on the list. Once that clicked for me, it changed how I look at everything I build. Here’s how I understand each piece. The 60% is infrastructure: This is the foundation. Your folder structure, where your information lives, how it moves, the plain deterministic scaffolding that holds the whole thing up. None of it is glamorous. It’s the part people want to rush past because it feels like setup instead of real building. But this is the building. Get this part wrong and nothing you stack on top of it stays standing. Almost every time something I’ve built keeps falling over, I trace it back here. The 30% is orchestration: This is how it all moves. The workflow logic, the order of the steps, where the gates are, where your quality checks happen, how one step hands off to the next. The if this then that. This is where your actual thinking lives. The infrastructure gives you the shape. The orchestration is what makes the shape do something. The 10% is AI: This is the piece everybody obsesses over, and it’s the smallest slice of the whole thing. It’s the generation, the analysis, the part that runs at the very end once everything underneath it is already solid. When the ninety percent below it is sound, the AI looks brilliant. When it isn’t, there is no prompt on earth that saves you. So which matters more, the 60 or the 30 I went back and forth on this for a while, trying to decide whether the structure or the logic carried more weight. I finally realized that’s the wrong question. The 60 and the 30 are both the real work. They’re the deterministic part, the stuff you actually have to sit down and think through. The honest divide isn’t 60 against 30. It’s the 90 against the 10.

Hi everyone. I’m a newbie to coding and vibe coding aswell. I just wondered if you could help me and potentially the other members of the group by telling us the biggest and most regular mistakes someone could do while vibe coding, especially when someone like me cannot check the code itself. Please tell me what you have found out and how have you overcome those issues. I would be especially interested in handling, errors and getting rid of hallucinations. Thank you very much in advance. ☺️