| ▲ | onethought 2 days ago | |||||||||||||||||||||||||||||||
But anyone didn't do it... you an expert in software development did it. I would hazard a guess that your knowledge lead to better prompts, better approach... heck even understanding how to build a status bar menu on Mac OS is slightly expert knowledge. You are illustrating the GP's point, not negating it. | ||||||||||||||||||||||||||||||||
| ▲ | hombre_fatal 2 days ago | parent [-] | |||||||||||||||||||||||||||||||
> I would hazard a guess that your knowledge lead to better prompts, better approach... heck even understanding how to build a status bar menu on Mac OS is slightly expert knowledge. You're imagining that I'm giving Claude technical advice, but that is the point I'm trying to make: I am not. This is what "vibe-coding" tries to specify. I am only giving Claude UX feedback from using the app it makes. "Add a dropdown that lets me change the girth". Now, I do have a natural taste for UX as a software user, and through that I can drive Claude to make a pretty good app. But my software engineering skills are not utilized... except for that one time I told Claude to use an AGDT because I fancy them. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||