fubarx@lemmy.world to Programmer Humor@programming.dev · 21 days agoThe Vibe Coding Hero's Journeymessage-squaremessage-square19linkfedilinkarrow-up1219file-text
arrow-up1219message-squareThe Vibe Coding Hero's Journeyfubarx@lemmy.world to Programmer Humor@programming.dev · 21 days agomessage-square19linkfedilinkfile-text
minus-squarered_tomato@lemmy.worldlinkfedilinkarrow-up67·21 days agoHave you noticed how every LinkedIn bro is talking about their vibe coding workflows, but no one is showing what they’ve made with vibe coding?
minus-squareChromaticMan@lemmy.worldlinkfedilinkEnglisharrow-up40·21 days agoSometimes a post on LinkedIn will have a link to a “finished” product. But 99% of the time there is a comment that says, “Hey, your API endpoints aren’t protected.”
minus-squarered_tomato@lemmy.worldlinkfedilinkarrow-up25·21 days ago99% of the time it’s just a basic todo list
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up0·21 days agoThe 1 percent being AudioNoise?
minus-squarethedeadwalking4242@lemmy.worldlinkfedilinkarrow-up1·21 days agoIt’s literally a single small python file.
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up0·20 days agoBut not a ToDo list right? Unless you consider computer instructions as ToDo items, in which case, all executables would be ToDo lists.
minus-square6nk06@sh.itjust.workslinkfedilinkarrow-up37·21 days agoIn a recent post on HackerNews, someone said that there is no burden of proof that it works. The purest form of “trust me bro.”
minus-squareslazer2au@lemmy.worldlinkfedilinkEnglisharrow-up16·21 days agoI prefer the other posts of vibe coders complaining about data loss because their llm didn’t tell them how to prevent xss or SQL injection.
minus-squarelad@programming.devlinkfedilinkEnglisharrow-up14·21 days agoOr because their agent wiped all the data on production
minus-squareslazer2au@lemmy.worldlinkfedilinkEnglisharrow-up10·edit-221 days agoYea, that was a good story.
minus-squareitsathursday@lemmy.worldlinkfedilinkarrow-up14·21 days agoLike all the other content grifters and their tutorials or get rich quick scams.
Have you noticed how every LinkedIn bro is talking about their vibe coding workflows, but no one is showing what they’ve made with vibe coding?
Sometimes a post on LinkedIn will have a link to a “finished” product. But 99% of the time there is a comment that says, “Hey, your API endpoints aren’t protected.”
99% of the time it’s just a basic todo list
The 1 percent being AudioNoise?
It’s literally a single small python file.
But not a ToDo list right?
Unless you consider computer instructions as ToDo items, in which case, all executables would be ToDo lists.
In a recent post on HackerNews, someone said that there is no burden of proof that it works. The purest form of “trust me bro.”
I prefer the other posts of vibe coders complaining about data loss because their llm didn’t tell them how to prevent xss or SQL injection.
Or because their agent wiped all the data on production
Yea, that was a good story.
Like all the other content grifters and their tutorials or get rich quick scams.