3 ms·

You make a fair point about git blame—we've always forgotten our old code. But there's a crucial difference between forgetting the "what" (the specific lines o

• muzani 1y ago
  You should have the why ironed out well before engaging the AI. Draw your UI, model your architecture, etc. If you must have the what before the why, that's perfectly normal and agile, but do it after the LLM is done type. If you do want to use a LLM for brainstorming, design, etc, it should be done before the coding. Like humans, they're not great at doing both at the same time. The models we have now are just very poor with setting up things from scratch. I think vibe code leans to frameworks like Expo because these are a little more stable without needing any architectural work, but they're rigid and limited. In mobile, we always use a pattern like view-viewmodel-repository-service. There's little reason to use less for an app with lots of async (e.g. web apps). There's also patterns like design systems and putting all your themes and colors in one box. But the AI will almost never set up this pattern. It's well aware of it and it'll seamlessly when you tell it to do it. But you have to set it up first.