←back to thread

Hallucinations in code are the least dangerous form of LLM mistakes

(simonwillison.net)
371 points ulrischa | 1 comments | 02 Mar 25 19:15 UTC | HN request time: 0.205s | source
Show context
why-el ◴[03 Mar 25 03:07 UTC] No.43237886[source]▶
I am not so sure. Code by one LLM can be reviewed by another. Puppeteer like solutions will exist pretty soon. "Given this change, can you confirm this spec".

Even better, this can carry on for a few iterations. And both LLMs can be:

1. Budgeted ("don't exceed X amount")

2. Improved (another LLM can improve their prompts)

and so on. I think we are fixating on how _we_ do things, not how this new world will do their _own_ thing. That to me is the real danger.

replies(2): >>43238020 #>>43238560 #
1. sfink ◴[03 Mar 25 05:26 UTC] No.43238560[source]▶
That's ok. Writing such a spec is writing the code, declaratively.

The only difference between that and writing SQL (as opposed to writing imperative code to query the database) is that the translation mechanism is much more sophisticated, much less energy efficient, much slower, and most significantly much more error-prone than a SQL interpreter.

But declarative coding is good! It has its issues, and LLMs in particular compound the problems, but it's a powerful technique when it works.