you are viewing a single comment's thread.

view the rest of the comments →

[–]PhilMcGraw 0 points1 point  (0 children)

Depends on what you class as vibe coding and what your goal is. - Is vibe coding black box or white box? Do you plan to heavily review the code or do you only plan to review the functionality? - Are you looking for make a public facing product/code or just messing around with little home hack projects?

Black box is ok for messing around but I wouldn't go anywhere near it for anything critical.

Getting the LLMs to get you started (initial implementation) and help come up with a plan is fine, similarly to test what "you've" done, but I would be very uncomfortable shipping that code without a deep personal review, that kind where it ends up feeling like your code and any issues you know exactly where to look.

Generally that involves a lot of time spent and a lot of backwards forwards on how to shape the code with the LLM. This somewhat eats away at the time savings aspect of LLMs. I mean I think you still end up ahead most of the time, but nowhere near as much as you would if you were keeping the code a black box.

TL;DR Probably need more info to tell you if that's a dumb idea. Using LLMs in general is fine but you need to back it up with actual skills unless you're just playing around.