We call it Poop Coding.
What intrigues me most about 'vibe coding' is also what intrigues me about 3D printing -- it's a tool that can't and won't natively produce at a high level of quality, like more robust manufacturing setups run by professionals can, but it does help the layperson solve problems they would otherwise be unable to solve themselves, often at an adequate level of quality. And I think most folks who use 'vibe coding', akin to those who 3D print, are aware of this. It's all experiment, discovery, trial-and-error.
I believe, if we consider 'vibe coding' as a more accessible approach to development for the less technical hobbyist, perhaps we can also consider it a conversation starter with the folks who would use it to talk more about the nuances of software engineering as a whole. I think there's something there.
Nothing is a panacea for specialization, to be clear. Folks who are skilled will always be SMEs. If they choose to engage with AI, they will understand that AI is just a tool to support them under the banner of those skills they know they possess. The skilled can guide thrse tools. The unskilled can only follow what the tool has been guided to produce for them. Major difference in quality.
But: that's where the conversation part of this comes into play. How do skilled folks talk to unskilled folks about the importance of the skill without it sounding so abstract?
Maybe 'vibe coding' is just another place from which to teach.
Hackaday
Fresh hacks every day