And?

The issue is that you should not blindly trust code. Being originally written by a human being is not, by any means, a quality certification.

That's why you meed to know the cavieats of the tool you are using.

LLM hallucinate. People willing to use them need to know, where is more prone to hallucinate. Which is where the data about the topic you are requesting is more fuzzy. If you ask for the capital of France is highly unlikely you will get an hallucination, if you as for the color of the hair of the second spouse of the fourth president of the third French republic, you probably will get an hallucination.

And you need to know what are you using it for. If it's for roleplay, or any not critical matters you may not care about hallucinations. If you use them for important things you need to know that the output needs to be human reviewed before using it. For some things it may be worth the human review as it would be faster that writing from zero, for other instances it may not be worth it and then a LLM should not be used for that task.

As an example I just was writing some lsp library for an API and I tried the LLM to generate it from the source documentation. I had my doubts as the source documentation is quite bigger that my context size, I tried anyway but I quickly saw that hallucinations were all over the place and hard to fix, so I desisted and I've been doing it myself entirely. But before that I did ask the LLM how to even start writing such a thing as it is the first time I've done this, and the answer was quite on point, probably saving me several hours searching online trying to find out how to do it.

It's all about knowing the tool you are using, same as anything in this world.

LLM also does not bully you for asking. Nor it says "duplicated question" for non duplicated questions... There's a reason people prefer LLM to SO nowadays.

It's not panacea. But it's not the doom world destroying useless machine that some people like to tell it is.

It's a useful tool for some task if you know how to use it. Everyone who actively use it is because we have find put that it works for us better than other tools for that task, of not we would not use it.

Giving my own personal experience, I tend to ask first to an LLM rather that what I used to do digging in old SO answers because I get the answer quicker and a lot of the times just better. It's not perfect by any stretch of the imagination, but it serves me a purpose.

For instance last week I needed a PowerShell command to open an app compatibility menu from the command line. I asked and got this as a response:

(New-Object -ComObject Shell.Application).Namespace((Split-Path "C:\Ruta\A\TuPrograma.exe")).ParseName((Split-Path "C:\Ruta\A\TuPrograma.exe" -Leaf)).InvokeVerb("P&roperties")

Worked at first try, exactly as I wanted.

You are free to try a search engine with the query "PowerShell command to open an app compatibility menu from the command line" and check for yourself how little help the firsts results get you.

It's a tool, as many others. The magic lies in knowing when and how to use it. For other things I may not use it, but after a couple of years using it I'm developing a good sense of which questions does it handle well and which questions is better not even to try.