[Retr0id]

Nobody who was writing code before LLMs existed "needs" an LLM, but they can still be handy. Procfs parsing trivialities are the kind of thing LLMs are good at, although apparently it still takes a human to say "why not using an existing library that solves this, like https://pkg.go.dev/github.com/prometheus/procfs"

[Jach]

Sometimes LLMs will give a "why not..." or just mention something related, that's how I found out about https://recoll.org/ and https://www.ventoy.net/ But people should probably more often explicitly prompt them to suggest alternatives before diving in to produce something new...

[otabdeveloper4]

> Procfs parsing trivialities are the kind of thing LLMs are good at

Have you tried it? Procfs trivialities is exactly the kind of thing where an LLM will hallucinate something plausible-looking.

Fixing LLM hallucinations takes more work and time than just reading manpages and writing code yourself.

[Retr0id]

Claude code can read manpages too

[otabdeveloper4]

If I'd ever feel the urge to misengineer a rube goldberg contraption to manage my vibe coder LLM output I'll get back to you.

But at the moment I feel like all that sounds suspiciously like actual work.

[delusional]

It cant "read" anything. It can include the man page in the prompt, but it can never "read" it.

[Retr0id]

If the output is working code I don't really care whether it's reading, "reading", or """reading"""