it's usually the balance and middle that is most beneficial. you can't deny the value LLM code generation and research provides. But the extreme of using only LLMs or mostly LLMs. or not using LLMs at all is self-harming.

So far, LLM generated code hasn't lived up to my standards. I'll use it for things that aren't critical as-is, but mostly I use it as a reference, an example, a starting point. Essentially, where in the past I'd find a code base that does things and I'd try to do something similar, now I let the LLM generate the code base. There are to questions it helps me answer:

1) What are the possible ways of solving problems?

2) What are the pros and cons of each approach?

That said, there are people successfully deploying apps that are entirely vibe coded. How many fail or succeed, that I don't know. But there are enough, and you can't deny the evidence.

▲

Ronsenshi 3 hours ago | parent [-]

Why is not using LLMs self harming? We've been writing code without help of LLMs for many decades just fine.

	▲	notepad0x90 an hour ago \| parent [-]
		This is what I find amusing, we're in tech, how can you ask that? We've been rubbing stones to start fire too, but if you stick to that and refuse to use electricity, that's self-harming because you lose out on all the benefits. You can't keep doing things the same way, that's now how technology as an industry works, the whole point is to come up with newer and better things. If you're a user of technology, then you can think like that and keep using old tech until the natural balance of things forces you. I fully expect LLMs to be obsolete in a few decades, and I'm now wondering if people then will say how LLMs have been serving them fine for a few decades. "just fine" isn't good enough in tech, "better" is always the goal.