Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vibe coding cleanup as a service

donado.co

Post reply on HN
Print view View original

131–140 of 151 posts

Re: Vibe coding cleanup as a service

#131

Post by bigstrat2003 »

bdzr wrote: post #123
icyfox wrote: post #112

From the jump, even without the emdashes, it was crystal clear that this post was written by Claude. I'm sure the OP put their own ideas into the prompt, provided some sources, etc. But reading some of these phrases provoked a pretty visceral sense that I'm just reading an LLM's output: "The harsh reality" "he perfectly captured" "architectural decisions that make senior engineers weep" "fundamental issue" It makes m…

I've made heavy use of emdashes my whole life. It feels like I have to eliminate them now :(

Don't let people's prejudice dictate your actions. If you like them, use them!

Re: Vibe coding cleanup as a service

#132

Post by jstummbillig »

HarHarVeryFunny wrote: post #126
jstummbillig wrote: post #107

Earlier quoted context omitted.

Unless, of course, there is a better AI at a future point, which is able to easily spot and correct the more underlying problems.

Sure but in the software field a few years is a lifetime. It's taken 8 years to go from introduction of the Transformer (attention paper) to today's LLMs, so I wouldn't be holding your breath waiting for something significantly different or more capable to replace it. It may well take AGI to replace a human "vibe coded mess" fixer-upper. The technical debt you're building up by vibe coding your product may well becom…

> It's taken 8 years to go from introduction of the Transformer (attention paper) to today's LLMs

I feel this position severely discounts the acceleration that is going on right now and our inherently limited abilities. Humans are not going to ever be significantly better at coding than they are today, and we can literally watch LLMs improve on it, by the month.

Re: Vibe coding cleanup as a service

#133

Post by HarHarVeryFunny »

jstummbillig wrote: post #132
HarHarVeryFunny wrote: post #126

Earlier quoted context omitted.

Sure but in the software field a few years is a lifetime. It's taken 8 years to go from introduction of the Transformer (attention paper) to today's LLMs, so I wouldn't be holding your breath waiting for something significantly different or more capable to replace it. It may well take AGI to replace a human "vibe coded mess" fixer-upper. The technical debt you're building up by vibe coding your product may well becom…

> It's taken 8 years to go from introduction of the Transformer (attention paper) to today's LLMs I feel this position severely discounts the acceleration that is going on right now and our inherently limited abilities. Humans are not going to ever be significantly better at coding than they are today, and we can literally watch LLMs improve on it, by the month.

We'll see. I think software development is one of the more challenging things that humans are capable of, and the challenge isn't because of something that computers have any advantage with due to computation speed or memory (unlike, say, chess).

I wouldn't expect to see a human level AI software developer (not just "coder" - the easiest part of the job) until we have human level AGI. Run-time compute and agents seem to be responsible for most of the recent advances in capability - good ways to squeeze the most out of the underlying LLM paradigm, but not the path to AGI.

We'll get there (AGI) one day, maybe in next 10-20 years, but in meantime if you want a vibe coded pile of sphaghetti to be cleaned up, it seems like it's going to be a job for a human.

Re: Vibe coding cleanup as a service

#134

Post by HarHarVeryFunny »

andy99 wrote: post #127
HarHarVeryFunny wrote: post #101

It's a bit strange that Karpathy's "vibe coding" ever gained traction as a concept, although perhaps only among those without enough experience to know better. As I understand it, what Karpathy was referring to as "vibe coding" was some sort of flow state "just talk to the AI, never look back" thing. Don't look at the generated code, just feel the AGI vibes ... It sounds absolutely horrific if you care even the tinie…

I still maintain that the original tweet about it was a joke, or at least not a suggestion for doing real work but just a reflection on the freedom of yolo mode coding. It wasn't meant to be instructions.

I'm not sure.. I kind of remembered it that way too, although perhaps not so much as a joke but just a throwaway tweet of what he was up so - experimenting with AI and having fun.

However, I just searched up his tweet, and now I'm not so sure - he seemed to be advocating it as a new way of coding.

https://x.com/karpathy/status/1886192184808149383

Re: Vibe coding cleanup as a service

#135

Post by rmoriz »

neya wrote: post #111
rmoriz wrote: post #80

Earlier quoted context omitted.

Have you instructed the agent to produce „simple“ solutions when possible?

Yes, the quality of output varies greatly depending on the model. Mostly they will hallucinate. For example, today I ran into an issue with file uploads. It suggested me `async_consume_uploaded_entries` which doesn't even exist.

I've made different experiences with Rovo Dev CLI (Sonnet 4). I think LLMs are designed to over-engineer because the learning data, typical open source projects, are over-engineered as well by design (they should provide universal services not tied to a single use case). I had to learn the hard way, since I steer the prompt to 1. limit external dependencies 2. don't introduce abstractions when not needed 3. focus on the main use path it works quite well. Since I also have tests and CI in place, hallucinations are caught very early. IMHO it's mandatory to be productive with the current state of coding agents.

Re: Vibe coding cleanup as a service

#136

Post by handfuloflight »

bdzr wrote: post #123
icyfox wrote: post #112

From the jump, even without the emdashes, it was crystal clear that this post was written by Claude. I'm sure the OP put their own ideas into the prompt, provided some sources, etc. But reading some of these phrases provoked a pretty visceral sense that I'm just reading an LLM's output: "The harsh reality" "he perfectly captured" "architectural decisions that make senior engineers weep" "fundamental issue" It makes m…

I've made heavy use of emdashes my whole life. It feels like I have to eliminate them now :(

N—never!

Re: Vibe coding cleanup as a service

#138

Post by dubeye »

Hmmm i do my own half assed diy and plumbing and the house hasnt fallen over yet, i replaced a pretty complex website and business management software operations and its a little didgy in places but again it is unlikely to explode

Re: Vibe coding cleanup as a service

#139

Post by scorpioxy »

Lu2025 wrote: post #84
scorpioxy wrote: post #67

Earlier quoted context omitted.

There's definitely a lot of politics involved in such projects. So I've learned that a break is necessary between major engagements to decrease the risk of burnout. The environment that creates "rescue" projects is usually not one where long term thinking is prevalent. It would be a pet project of someone who's still there or someone who left but where the ultimate decision maker is still there. Either case, you need…

I was about to ask whether engaging with this kind of people is even worth it. I've seen enough of Jamie Dimon-like power trips to stay away.

That's a good question that I sometimes ask myself. But if you want the money, you have to do what it takes. There's a limit of course and lines that I do not cross(illegal, unethical etc). There were plenty of times where I had to say that this is not going to work and chose to end the relationship with a handover. During those times, the technology wasn't the problem.

Re: Vibe coding cleanup as a service

#140

Post by a_bonobo »

abxyz wrote: post #105
HarHarVeryFunny wrote: post #101

It's a bit strange that Karpathy's "vibe coding" ever gained traction as a concept, although perhaps only among those without enough experience to know better. As I understand it, what Karpathy was referring to as "vibe coding" was some sort of flow state "just talk to the AI, never look back" thing. Don't look at the generated code, just feel the AGI vibes ... It sounds absolutely horrific if you care even the tinie…

For many non-technical people, their relationships with software engineers were producing horrific results. Vibe coding is an indictment of what we’ve been delivering. That a vibe-coded disaster is in any way desirable reflects poorly on us. The branding by Karpathy is cute but irrelevant to its success. I know people running vibe coded startups. The software quality is garbage. But it does what they want. And that’s…

>I know people running vibe coded startups. The software quality is garbage. But it does what they want. And that’s all they care about for now. Until a time when software quality impacts their business more than losing control does, they’ll keep vibe coding, rather than hiring a software engineer who bastardises their ideas.

Well, IKEA's furniture quality is garbage yet they make billions. It's cheap and fast. That's capitalism for you. (not implying that communist countries produced amazing products...)

Post reply on HN