> 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.