Earlier quoted context omitted.
the next version of AI will simply make it into a bigger mess.
Now, now, not with this mindset. You have to ask the Ai to fix the mess, and if it doesn't, try again!
“Vibe Coding” vs. Reality
91–100 of 312 posts
Re: “Vibe Coding” vs. Reality
#92We already have examples of a model finding more performant sorts [0], given the right incentives and time, and the right system for optimizing (LLMs trained on “average code” probably aren’t it) the computer will best us at creating things for the computer.
Is “vibe coding” real today? Not in my experience, with even Claude code. My hand has to be firmly on the tiller, using my experience and skill to correct its mistakes and guide it. But I can see the current trajectory of improvement, and I’m sure it’ll get there.
[0] https://deepmind.google/discover/blog/alphadev-discovers-fas...
Re: “Vibe Coding” vs. Reality
#93The biggest give-away is: When you look at the companies making these claims and their jobs page shows they are actively hiring developers.
Re: “Vibe Coding” vs. Reality
#94Earlier quoted context omitted.
the next version of AI will simply make it into a bigger mess.
Now, now, not with this mindset. You have to ask the Ai to fix the mess, and if it doesn't, try again!
Re: “Vibe Coding” vs. Reality
#95[1] it's unbelievable what a difference in quality 1 year made for chat gpt
Re: “Vibe Coding” vs. Reality
#96I mean shouldn't Jensen be shitting his pants about this? Vibe code the CUDA away and bye bye margins ?
Re: “Vibe Coding” vs. Reality
#97Really this whole industry is on another fucking planet. I hate it but it’s so easy to make money.
Re: “Vibe Coding” vs. Reality
#98My, very limited experience with LLM assisted coding is that it depends... For basic frameworks done in something like Python it is very good, but not perfect, yet. But the iteration cycle to get to where you want to be is still faster than doing the whole job manually and I see this as a big win. For more esoteric fast changing languages/frameworks it has me chasing my tail in a chain of code updates where each fix…
I see statements like this a lot when talking about AI in general. People seem to think it is a foregone conclusion that no limit to LLM model improvement and capability exists. What causes you to believe this and what evidence do you have to back it up?
Re: “Vibe Coding” vs. Reality
#99Earlier quoted context omitted.
Yeah but AI coding does speed up some simple tasks. Sometimes by a lot. But we have to endure these tedious self-congratulatory "mwa ha well it's still not as good as my code" posts. No shit. Nobody is saying AI can write a web browser or a compiler or even many far simpler things. But it can do some very simple things like making basic websites. And sure it gets a lot of stuff wrong and you have to correct it, or fi…
> This post feels like complaining about cruise control because it isn't level 5 autonomy. It's nothing like that, because cruise control works reliably . There is never a situation where cruise control randomly starts going 90mph or 10mph while I have it set to 60mph. LLMs on the other hand... This is why I disagree with people who argue (as you did) "it really does speed up simple tasks". No it doesn't, because eve…
Re: “Vibe Coding” vs. Reality
#100> Cursor has some sort of "concise mode" (archived) that they'll turn on when there is high load where the model will still be rated at the normal price but behaves in a useless manner. This mode will omit details, drop important findings, and corrupt the output that is being produced. This is a real problem that I have experienced on and off. It's getting to the point where everyone on my team is actively looking fo…
Interestingly the times I've experienced the most weirdness were during extremely not normal business hours (from the California perspective). For 3 nights in a row last week, I found myself coding at/after 2:30am during what were apparently periods of excessive load on Claude Sonnet. When asking Cursor to do things, it would fail, tell me about the high load, and encourage me to try again soon. Well, I just kept clicking the button over and over again, thinking it would eventually be able to handle the request properly, and otherwise continue presenting the error. Not the case!
Incorrect/hilarious things Cursor/Claude did at points during those nights:
- repeat the inquiry back to me in full, then do nothing at all after that
- confidently assert it had located the bug I was looking for, then direct me towards the entire codebase
- assert that it had done what I asked, and request that I approve the changes it wanted to make to my code, which were... nothing, none whatsoever
- (possibly the most hilarious) begin to answer questions in borderline leetspeak, randomly substituting numbers in place of letters in words, before eventually devolving into total gibberish
Mostly just annoying due to the wasted time, though it's possible the entertainment value negated it. I don't expect miracles from Cursor to begin with, nor do I give it wide latitude to change very much in my projects, so the risk of damage wasn't really any worse then than at any other time. Of course, I am not a team working against deadlines on critical projects, just a guy screwing around at 2:30am.