Comment by km144
I think you're missing the value of rubber-ducking with the chatbot on a fairly well-defined/well-known problem in a somewhat specific/novel scenario—this is the vast majority of software development being done today.
Depending on the situation this can be invaluable. If you're experienced in the domain you probably know generally what you need to do but you might get a better result by reasoning through the best solution with the constraints and requirements you have. Or maybe you missed something obvious when you write out the full context—which is a required step for getting a good output from the chatbot, and generally isn't a required step if you aren't explaining your approach to someone else and you don't want to be rigorous.
> I think you're missing the value of rubber-ducking with the chatbot on a fairly well-defined/well-known problem in a somewhat specific/novel scenario—this is the vast majority of software development being done today.
I actually do use ChatGPT for rubber-ducking, but in that context there is no (or very little) code. In a coding context, I've resigned myself to purely autocomplete-on-steroids.
The thing is, in the vibe-coding context (having the LLM write the code for you), I've had atrocious results across all of the popular LLMs.