[quamserena]

I don’t understand how this can be more optimal than just reading the documentation that a human already wrote. All “normal” uses can be answered by reading the docs, everything advanced you can just read the code. I’m not sure when I would ever use this?

[sidcool]

Reading a ton of docs and interpreting them is a tedious activity. If you can get deducible or inferable answers with AI, that's a huge win. I have faced issues with kubernetes that needed me to wade through the code for days to find it was a missed case or unsupported. AI would help me in minutes. That's the claim here, if it works that way.

[quamserena]

I’ve never had AI understand a problem of that depth though. It can maybe surface the right part of the docs to reference but in the times I have used it it leads me down the wrong path half of the time.

[linkage]

I encourage you to put your preference to the test on the NixOS and nixpkgs documentation.

[dpark]

Generating and maintaining docs is a massive cost. Presumably the point of this is to reduce that cost. And for projects where the existing documentation is poor or nonexistent, this might be far better than what’s available today.

How well this actually works, though, I have no idea.

[theletterf]

This doesn't replace docs, nor technical writers.