5 ms·
The fact that they could be "vibe coded" means that they (or something similar) probably already existed, but you just didn't know they did.
by hajile 1y ago
The fact that they could be "vibe coded" means that they (or something similar) probably already existed, but you just didn't know they did.
- davely 1y agoBut the amount of time saved because one could vibe code it rather than search through Google’s terrible results is immense and a benefit in and of itself.
- skydhash 1y agoMaybe. But anytime I take on the task to automate something, it was a nice opportunity to check how others do it, what other things the program can accomplish. The decision to automate is already done, no need to rush through it.
- deleted 1y ago[deleted]
- dingnuts 1y agoIDK, there are a lot of little chores that I find needing done that previously would have been ten minutes of research and cli fiddling that are a prompt and copy paste now. It doesn't feel that different but it is a little faster
- hajile 1y agoIf you don't understand what the copy/paste is actually doing, you shouldn't be script-kiddying it in your project. If you do understand, then the AI is just quickly writing what you already intended. If you are having to understand something you didn't understand, it's probably taking a bunch of time to read and verify what the script does. This can be a good learning experience and reveal unknown unknowns, but probably isn't a massive speedup.
- johnfn 1y agoThis seems false to me. I vibe code shell scripts all the time. I understand what it's doing perfectly, but it would have taken me ages to look up all the bash syntax and get it all correct. Is it one square bracket pair around if statements, or two?
- hajile 1y agoYou are in the category I mentioned that already know the answer and are using AI to write the code you already understand faster. This is rather different from “vibe coding” in my opinion.
- int_19h 1y agoIt's different by the canonical definition - you aren't supposed to review the code when "vibe coding", only the app behavior.
- cma 1y agoI think it is somewhat similar to the emergent translation capabilities, it doesn't need to have trained on a translation of a text to do one of it. But it does need good coverage of the area.
- IshKebab 1y agoNo, there's a very very long tail of tasks that are too niche for a proper tool to exist for but it would be annoying effort to figure out yourself. My most recent example of this: write a script to delete all git branches that point to HEAD. Go ahead see how long it takes you to figure out the command for that, because it took me under 60 seconds with AI.
- hajile 1y agoThis is the learning to fish problem. If you understand git well, a solution isn't very hard (eg, rev-parse each branch and compare to the rev-parse of the current branch and deleting if they match). If you don't understand git well, you shouldn't be turning into a script-kiddy pasting in whatever the AI spits out and hoping that it works.
- NewsaHackO 1y agoYour method still requires a script though
- johnfn 1y agoYou are using "script-kiddy" as an ad hominem rather than making an argument with proper justification. "script-kiddy" refers to website vandalism and cracking. That has nothing to do with using AI to learn what rev-parse does. Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`.
- AstroBen 1y agoWhat the end product is depends on the specific parts chosen and the way they're put together Just because the parts are available doesn't mean every possible combination of them has already been made
- unchar1 1y agoParts of it could probably already exists in the LLM's corpus, but being able to join them together to build new things is what makes "vibe coding" so useful. Even though, from personal experience, at scale it still falls apart
- yoda97 1y agoNot if you know the field really well, I talk to my users.