Against the grain here: Yes, you will. You should try to understand what it is useful for and what it isn't. You don't need to vibe code at all; in fact, it's

Against the grain here: Yes, you will. You should try to understand what it is useful for and what it isn't. You don't need to vibe code at all; in fact, it's the exact opposite. You should read the code and be able to figure out what LLMs are bad at and how they make inhuman mistakes. I personally like the prompt completion of functions. The act of manually writing out in detail what needs to happen and how help me think about what I want to have done. Anyway, the main argument I have that you should be using it is that the first and experience of using it will teach you about what to look for in broken LLM code and also help you guide others into producing less broken LLM code.