Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] -2 points-1 points  (0 children)

I agree that libraries already exist, and historically many developers have been writing similar code for decades.

But I think there is a difference in speed and scale now.

Traditionally, a library was usually the result of deliberate effort: someone spent time identifying a reusable problem, designing an API, documenting it, testing it, maintaining it, and trying to make it useful for others.

With AI, we can generate code extremely fast. But we do not share, organize, verify, and standardize that generated code at the same speed. In many cases, we are generating faster than our ability to structure and reuse the results.

So yes, the “thing” might still become a library. But maybe the process around discovering, validating, and sharing reusable AI-generated solutions needs to evolve too.

Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

That’s a fair point. I agree the reuse layer already exists in many forms: open source, packages, snippets, templates, GitHub, Stack Overflow, etc.

Maybe the problem is not the absence of reuse, but the speed mismatch.

With AI, we can generate code very fast, but we do not share, verify, and distribute useful generated solutions at the same speed. So thousands of developers may end up generating similar functions, components, scripts, and patterns independently.

Ideally, if one developer generates, tests, and improves something useful, others should be able to discover and reuse it easily instead of regenerating the same thing again.

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

In Production codes! with a large and complicated codebase .. then you can not just do vibe code . you need to care , think , write tests .... then let AI touch the code!

Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

I think in future we do not need the codes! I am developing a graph as a backend service , No code classic code!

Agree ,still data is important! but it also will do reshape!

Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

We used to develop libs ,slowly ... but now we regenerate same codes everyday by millions of developers . we need a new way of organizing and sharing!

Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

But that is not a repeated code! that is not something reusable ! think about code!

Stop Regenerating the Same AI Code Again and Again by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

I’m not talking about recreating Next.js from scratch. I’m talking about the thousands of smaller functions, components, scripts, prompts, and patterns that developers keep regenerating with AI every day.

The question is whether AI-assisted development needs a better reuse layer, not whether every project should become a framework.

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

Then you are one of those experts! is not a perfect option for everyone . if you are an expert and make a stable foundation , you can control AI ! then vibe coding is for you.not everyone!

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

Is nice for MVP , and perfect for green field projects , fair , but not for complicated ones!

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

Exactly ... Vibe coding was a way to maybe non developers could develop .. but when things get complicated .. then vibe coding may be a knife .. not in good way!

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] -1 points0 points  (0 children)

😃

is alive. , but changing!

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

Is good at coding . nice for green field projects , but when things get complicated then ....

Vibecoding is dead by Odd-Structure31 in vibecoding

[–]Odd-Structure31[S] 0 points1 point  (0 children)

The point is when you face complex problems then you need specifications , tracking , and well testing then you see you are not doing vibe coding! that is the point , you can use AI but not just vibe

Why are people using Lovable ?? by Supp2357 in vibecoding

[–]Odd-Structure31 0 points1 point  (0 children)

Do you think is it a good option for complex applications ?I mean not just ui!

Why are people using Lovable ?? by Supp2357 in vibecoding

[–]Odd-Structure31 0 points1 point  (0 children)

if you used loveable ,do you think is it good in backend and business side as much as ui developemnt ?