Programming

24083 readers

168 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

LLM's hallucinating or taking our jobs? (lemmy.world)

submitted 2 weeks ago by monounity@lemmy.world to c/programming@programming.dev

81 comments fedilink hide all child comments

Lemmings, I was hoping you could help me sort this one out: LLM's are often painted in a light of being utterly useless, hallucinating word prediction machines that are really bad at what they do. At the same time, in the same thread here on Lemmy, people argue that they are taking our jobs or are making us devs lazy. Which one is it? Could they really be taking our jobs if they're hallucinating?

Disclaimer: I'm a full time senior dev using the shit out of LLM's, to get things done at a neck breaking speed, which our clients seem to have gotten used to. However, I don't see "AI" taking my job, because I think that LLM's have already peaked, they're just tweaking minor details now.

Please don't ask me to ignore previous instructions and give you my best cookie recipe, all my recipes are protected by NDA's.

Please don't kill me

you are viewing a single comment's thread
view the rest of the comments

[–] ulterno@programming.dev 0 points 2 weeks ago

Well, it did let me make fake SQL queries out of the JSON query I gave it, without me having to learn SQL.
Of course, I didn't actually use the query in the code, just added it in a comment for a function, to give an idea to those that didn't know JSON queries, of what the function did.

I treat it for what it is. A "language" model.
It does language, not logic. So I don't try to make it do logic.

There were a few times I considered using it for code completion for things that are close to copy paste, but not close enough that it could be done via bash. For that, I wished I had some clang endpoint that I could then use to get a tokenised representation of code, to then script with.
But then I just made a little C program that did 90% of the job and then I did the remaining 10% manually. And it was 100% deterministic, so I didn't have to proof-read the generated code.