51–60 of 93 posts
Earlier quoted context omitted.
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.
But 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.
Earlier quoted context omitted.
Is it. For small scripts like these you can get far with basic search and sources like docs/github/SO. Maybe cursor is more “fun”, “engaging”, and the like, but it’s not like it was a difficult job before.
Biking isn’t difficult, but you’ll still travel more with a car.
Has anyone honestly had good experiences vibe coding? I mean like building any kind of application above and beyond a simple shell-like script? Honest question here. I'd be curious too what scenarios in general folks find LLMs useful re coding. edited: typo
Semi-controversial headline but I think the point is fair. It doesn't yet produce results that meet a spec well. It's fine for scripts because if it insists you do it the bot's way, that's fine. If it uses the wrong library, whatever. And so on. I'm going to keep shilling this until people start doing it: I'd love to see everyone who says he's vibecoded something non-trivial and posts/blogs about it start dumping and…
The one time so far that I actually implemented a full feature using only vibe coding (and it wasn't trivial), I had to be very specific about what I wanted, and it was in a very widely used stack (React/NextJS), it was a very common feature (sorting, filtering, pagination on a table) and it worked beautifully. But it felt magical the one time it happened. Every other time, I'm mostly using tab autocomplete and that…
But since my free time is so extremely limited, it would be really nice to get better LLM and agent support. So I hope the lesser used languages and frameworks get more training love, soon. Lest we all only use Next for hobby projects in the future.
Claude has helped me a lot to get through my small feature backlog faster. But if you don't review the code you're asking for hurt. It has literally written stuff like "if pending changes > 20, delete all", etc.
There are parallels to the “rapid application development” push of the 90’s. Visual Basic, Tcl/Tk, Python with Tkinter, HyperCard; all of them promised shortening the development cycle and democratizing computing. Code was interpreted rather than compiled, dynamically typed rather than statically, and a lot of batteries were included. It sorta worked, and sorta didn’t. I’m seeing no evidence that this round is differ…
Vibe coding promises the world, and behold fails to deliver.
There are parallels to the “rapid application development” push of the 90’s. Visual Basic, Tcl/Tk, Python with Tkinter, HyperCard; all of them promised shortening the development cycle and democratizing computing. Code was interpreted rather than compiled, dynamically typed rather than statically, and a lot of batteries were included. It sorta worked, and sorta didn’t. I’m seeing no evidence that this round is differ…
All the excitement I felt because it was new to me, but it was really just a very basic toy not a real piece of software.
Meanwhile there were seasoned pros who could probably do amazing things even with GWBASIC. But that was more in spite of it than because of it.
Earlier quoted context omitted.
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.
No, 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.
I have already vibe-coded countless number of scripts and two side projects that were on my "list" for years, these projects would have never seen the light of day if not for Cursor. That's the whole point.
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.
Even though, from personal experience, at scale it still falls apart
Earlier quoted context omitted.
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.
IDK, 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
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.