[circuit10]

You can’t realistically cover every use case. With an LLM you can say something like “Make me a program that sets up an SDL window with the title ABCD that has a 396x224 RGB565 framebuffer and moves around a red square using the WASD keys by using a loop to fill in pixels in that framebuffer and then quits when it reaches the right edge of the screen” and it has a reasonable chance of making something that works or at least is easy to adjust into something that does. Just because sometimes it might not work the first time isn’t a good reason to try to stop people from using it entirely

[gavinhoward]

I would bet good money that, as a use case becomes more niche, an LLM's output becomes more wrong. If that's true, your assertion would be wrong.

[circuit10]

It does become more wrong, yes, but blocking it isn’t going to help it get any better. The idea that everything an LLM does can be replaced by documentation isn’t true

[gavinhoward]

> The idea that everything an LLM does can be replaced by documentation isn’t true

An LLM is false value, so I'm not worried about that.

[circuit10]

How is it false? I’d say an LLM is like the output you’d get if you forced someone to write something with a strict time limit and without being allowed to go back and edit things or look anything up - likely to be wrong about anything that needs deep thought, but not entirely useless for simple things that are just tedious like boilerplate code