Live data from Hacker News

Vibe coding cleanup as a service

donado.co

21–30 of 151 posts

Re: Vibe coding cleanup as a service

#21
post #8

That raises the question if LLM-generated code is going out of fashion in general. The article seems to assume it will always exist and always need clean-up. But what if it's not worth it and instead you should (mainly) return to the world where humans write code? Simply because salary < LLM-credits + cleanup costs.

Using a LLM to generate code, that you then check and use is a bit different from vibe coding, where no one looks at the code anymore.

But both is here to stay.

Re: Vibe coding cleanup as a service

#22
post #2

I just take some kitchen paper and one of these small thin plastic bags to clean up after my own dog's shit. No need to pay for a service.

Just wanted to apologize for the shallow dismissal and the snark. This is going to generate cash flows so the associated activities are totally legit and not parasitic and a waste of oxygen. My gut reaction was not civilized.

Re: Vibe coding cleanup as a service

#23
Would be interesting to see an in depth breakdown on a project that has went through the vibe code to cleanup pipeline in full. Or even just a 'heavy LLM usage' to 'cleanup needed' process. So, if the commits were tagged as LLM vs human written similar to how it's done for Aider[0]: At which point does the LLM capability start to drop off a cliff, which parts of the code needed the most drastic refactors shortly after?

[0]: https://aider.chat/HISTORY.html

Re: Vibe coding cleanup as a service

#26

Would be interesting to see an in depth breakdown on a project that has went through the vibe code to cleanup pipeline in full. Or even just a 'heavy LLM usage' to 'cleanup needed' process. So, if the commits were tagged as LLM vs human written similar to how it's done for Aider[0]: At which point does the LLM capability start to drop off a cliff, which parts of the code needed the most drastic refactors shortly afte…

Interesting idea for some kind of blog post:

* come up with requirements for a non-obvious system

* try to vibe-code it

* clean it up manually

* add detailed description and comparisons of before and after; especially, was it faster or slower than just writing everything manually in the first place?

Re: Vibe coding cleanup as a service

#27
In my experience vibe coding is useful at the very beginning of a project (especially if the tooling selected does not have a boiler late generation) and at the very end when a lot of the work is refactoring.

YMMV but I’d rather build the MVP without much AI but then clean it up using it.

Re: Vibe coding cleanup as a service

#28

> Startups save weeks getting to MVP with Vibe Coding, then spend comparable time and budget on cleanup. But that’s still faster than traditional development. That's the core of situation as described in the article. I wonder how true that is, that it's faster overall than having developers build the MVP. From what I've seen, I think developers can build just as fast, especially with AI assistance. They may not want…

>> Startups save weeks getting to MVP with Vibe Coding, then spend comparable time and budget on cleanup. But that’s still faster than traditional development.

> That's the core of situation as described in the article. I wonder how true that is, that it's faster overall than having developers build the MVP.

In a startup it's often very important to show traction, and thus decreasing time to market can be hugely beneficial, even if it costs you more time overall.

The same reason people can rationally take on technical debt in general.

Re: Vibe coding cleanup as a service

#29
post #8

That raises the question if LLM-generated code is going out of fashion in general. The article seems to assume it will always exist and always need clean-up. But what if it's not worth it and instead you should (mainly) return to the world where humans write code? Simply because salary < LLM-credits + cleanup costs.

It might turn out to be unsustainably expensive to vibe code all day. That it was so subsidized might have been the irrational exuberance, which arguably leaves a bait-and-switch hangover.

But the general idea of compressing every code example in existence into a predictive autocompleter and generative assistant will never go away.

It would be like coding without syntax highlighting, by choice. Sure, people did it when they had to, but not anymore. You could, but why?

Do I really feel better about myself for writing a slight variation on depth-first search by hand for the 80th time? Not really?

Re: Vibe coding cleanup as a service

#30
post #27

In my experience vibe coding is useful at the very beginning of a project (especially if the tooling selected does not have a boiler late generation) and at the very end when a lot of the work is refactoring. YMMV but I’d rather build the MVP without much AI but then clean it up using it.

Our 'vibe coding' tools are still getting better very quickly. And you would expect that, even if core LLM progress stopped.

So I suspect we will get AI-assisted vibe coding cleanup very quickly.

Our (new) AIs will help us solve problems that we wouldn't have without our (old) AIs.

Post reply on HN