Vibe coding cleanup as a service • Hacker News Board

Re: Vibe coding cleanup as a service

#111

Post by neya » Sun, Sep 21, 2025, 3:03 PM UTC

rmoriz wrote: post #80

neya wrote: post #66

I use Elixir in production. So, it's already a pretty unique language with very low marketshare in the first place and not many developers are attracted to it because of that and the opportunities. And rarely, I do take on some existing codebases that would smell of code rot from vibe coding. Elixir is one of those languages where it's actually hard to make something look complex. But, vibe coders somehow manage to p…

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.

Re: Vibe coding cleanup as a service

#112

Post by icyfox » Sun, Sep 21, 2025, 3:12 PM UTC

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 me wonder whether a whole class of writing is going to be deprecated because the cadence is just too similar to LLM outputs.

Re: Vibe coding cleanup as a service

#113

Post by dostick » Sun, Sep 21, 2025, 3:15 PM UTC

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 suspect that he, as an insider is able to prompt and configure so that he gets good usable results every time, and when he describes that, it sounds so easy and obviously you should do it too.

Re: Vibe coding cleanup as a service

#114

Post by skeeter2020 » Sun, Sep 21, 2025, 3:22 PM UTC

this article doesn't add much; it's a thin advertorial for their services. It also just seems like typical maintenance programming, which has existed for about 1 day less than the entire time we've been writing software. I guess even this most unattractive of all programming work is also looking for a little AI sauce to spice up the offerring, and justify increased rates (maintenance work: $100/hr; vibe-coding cleanup: $200/hr)

Re: Vibe coding cleanup as a service

#115

Post by skeeter2020 » Sun, Sep 21, 2025, 3:22 PM UTC

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…

get ready for vibe-writing cleanup as a service...

Re: Vibe coding cleanup as a service

#116

Post by AnotherGoodName » Sun, Sep 21, 2025, 3:27 PM UTC

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 feel at this point ‘vibe coding’ is just a disparaging phrase of any AI coding assistance.

As always people can create both good and bad code using the tools at their disposal but right now there’s a lot of upvotes to be had online by simply posting ‘lol vibe coding so dumb!’. It’s tiring at this point.

Re: Vibe coding cleanup as a service

#117

Post by [deleted] » Sun, Sep 21, 2025, 3:32 PM UTC

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…

[deleted]

Re: Vibe coding cleanup as a service

#118

Post by thephyber » Sun, Sep 21, 2025, 3:33 PM UTC

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…

[dead]

Re: Vibe coding cleanup as a service

#119

Post by gerdesj » Sun, Sep 21, 2025, 3:47 PM UTC

skeeter2020 wrote: post #115

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…

get ready for vibe-writing cleanup as a service...

I'm sharpening my biro even as I type ...

Re: Vibe coding cleanup as a service

#120

Post by ronsor » Sun, Sep 21, 2025, 4:34 PM UTC

HarHarVeryFunny wrote: post #108

abxyz wrote: post #105

Earlier quoted context omitted.

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…

Using AI doesn't necessitate "vibe coding" - there are smart ways to use AI, where you are managing and structuring the process, as well "vibe coding". I guess the problem is that AI now allows non-programmers to program. It would be a bit like giving everyone a scalpel and they now either consider themselves to be surgeons, or give it a go regardless since now they can. I'm not sure where you are getting software en…

Usually the problem is they are too cheap to pay good engineers, so they can only hire bad ones...