231–240 of 258 posts
Impressive! 35 kLOC is quite a bit. I wonder how straightforward and maintainable this app ended up to be. This would require taking a look at the sources. While good Rails code tends to be very terse, frontend may be quite voluminous. > I believe within a couple of months, when things like log tailing and automated testing and native version control get implemented This sounds a bit too optimistic, especially around…
Earlier quoted context omitted.
> In my experience, most "human recipes" are just random variations on some baseline. This just shows your lack of experience and curiosity. The art of cooking is a cultural achievement with thousands of years of history, with vast differences between different countries and cultures. Just visit a store (yes, a real one) with a good cooking book section. You might be surprised.
Seriously, what's with this thread? I'd rather not have a discussion in this base tone.
[flagged]
https://news.ycombinator.com/newsguidelines.html
https://news.ycombinator.com/showhn.html
Please don't attack others or their work like this on this site, regardless of who or what you have a problem with. It's the opposite of the curious, respectful conversation we're looking for, and always has been.
Help! I just made the Diarrhea Walnuts ( https://www.recipeninja.ai/recipe/r_N1VSPtXzCJVV3l/diarrhea-... ) recipe and it turns out I am allergic to Walnuts! I am throwing up everywhere! You’re gonna be hearing from my lawyers!
Try out the Gluten Free Shark Teeth once you feel better! https://www.recipeninja.ai/recipe/r_ttOB5xyqpOLXCL/gluten-fr...
Perhaps this is 1998 again, when you could earn big money on creating a visitor-counter service, or a guest book service.
Perhaps, now is the time for a lot of smaller projects with AI, that will, in a few years, all be blasted off the market by big corporations and change in trends.
Earlier quoted context omitted.
I kinda wish I could look at the code, but it's not open source and the frontend sources are minified/obfuscated, but it's long and looks like it's using React and a css-in-react approach, which also generates a ton of code.
The term "vibe coding" gives me bad vibes, I feel that it is in some way an insult to my craft, the way a carpenter might feel about Ikea. But if only LLM's are going to read the code, the LoC aren't a big problem, increasing cost significantly less than if a real person would have to read it. The two biggest issues I can think of with this approach is performance and security, with the first one only being a problem…
Earlier quoted context omitted.
That or we're completely ignoring principles like DRY and producing a head spinning amount of tech debt. I can't really imagine producing that much code in that short amount of time and holding any amount of it in my head. I'd bet money there's code in there that does the same thing but different, leading to all kinds of little inconsistencies that make this code worthless in any serious context.
I’m an old school coder. I haven’t vibed. I’m guessing the “who is going to maintain this” could only be another tool similar to what built it. I can’t imagine trying to get my head around that much code in a timeframe acceptable to someone demanding product. So are we headed to a place where everything is written and maintained this way or a lucrative future of having to get these things to work properly.
Earlier quoted context omitted.
See https://twitter.com/karpathy/status/1886192184808149383 for when it was coined by Andrei Karpathy. I've written more about it here: https://simonwillison.net/2025/Mar/19/vibe-coding/ and here: https://simonwillison.net/2025/Mar/23/semantic-diffusion/
[flagged]
Earlier quoted context omitted.
Instead of complaining, why don't you click the link that was spoon fed directly to your cursor for the canonical answer within 3 seconds?
Because the effort needed to summarize the content of the links is barely more than posting them in the first place. Who knows what kind of time wasting is on the other side of a link these days either.. Dark pattern cookie pop-ups, subscription pop-ups, intrusive ads, account registration demands, pay walls, etc..
Earlier quoted context omitted.
By practice. It requires some skill too, to constantly remove slop and keep the project from deteriorating. Usually by suggesting good architecture, asking for tests, and rewriting / cleaning up some bad code endlessly. Still much faster than manual development.
But how exactly !
2. Tell it to make you something
3. Get frustrated when it doesn't work
4. Think about how to revise your prompt
5. Repeat from step #2