RE: Vibe coding is much more complicated than I thought
You are viewing a single comment's thread:
Yep, the best way to vibe code is to break it into pieces, ask for a plan or step by step instructions. You can also tell the AI you have no programming knowledge, and it should come with a plan for you (or a finished product, you'll have to choose, most likely). I wouldn't go for the finished product, as it is much more difficult to change afterwards with the help of AI.
I have a background in programming, and it helps with vibe coding, indeed. For example, I catch the misses of the AI, which it recognizes when you question it about them. While it's a GREAT help, it doesn't produce perfect work. In fact, if you give the same code you put together based on its instructions to the same model in a future session, it will find ways to improve it or even things to fix.
That actually really helps. I have done that, especially when it wants me to panache different codes bases together. I prefer to tell it to do it by itself lol.
I realised that too and especially while debbugging it tries to mend things 10 x exactly the same way and it can be helpful to either change the model or to think by myself and give it a nudge in the good direction :-)
Absolutely! It's very important how you guide it. Sometime it gives you options. It it good if you know what would be better to choose between the options, to have a broad view of the project, or even to drop its options altogether and suggest a different next step.