this post was submitted on 16 Oct 2026
625 points (95.8% liked)

Linux

68249 readers
204 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Ephera@lemmy.ml 9 points 1 week ago* (last edited 1 week ago) (1 children)

But why can you not audit what the LLM creates? You can't do it for the general case, i.e. prove that for a given prompt it always spits out a valid solution, but you can look at what it actually spit out for your concrete prompt and then you can freely decide, if those code changes are good.

I am of the opinion that a thorough review often takes similarly long to actually writing it yourself, and there's a high chance that you miss architectural aspects, if you don't investigate yourself.

But yeah, again, I think you're taking the comparison too literal.
He is just saying that LLMs are a tool. You need to know how to use your tool and produce objectively good results. Then he does not care what tool you use to get there.

[–] Doomsider@lemmy.world 5 points 1 week ago (1 children)

Auditing typically means tracing the logical path. How do you suggest to do this with an LLM?

I am definitely taking his words literally which is why I disagree with just this one point.

[–] Ephera@lemmy.ml 2 points 1 week ago

You don't have to do everything with the LLM. Tracing the logical path very much still happens by looking at the code in your editor.

This is also why I'm saying it isn't much faster. Understanding the existing code and what changes are necessary is the bulk of the work when handwriting code as well.

You *can* tell the LLM to go ham and implement the change on its own and then only look at the diff afterwards, but anyone who thinks they understand the code changes then, is lying to themselves IMHO.