> nobody wants to read [documentation]. OP wants to read documentation. It's in the article. Quite a few commenters say that they're resorting to LLMs, not be

> nobody wants to read [documentation]. OP wants to read documentation. It's in the article. Quite a few commenters say that they're resorting to LLMs, not because that's how they want to learn about the code they're using, but because the documentation is terrible and LLMs summarising snippets from dozens of different forum questions and blog posts is the only alternative they have to terrible documentation. > most popular open source projects seem to prioritise guides for common use cases over extensive documentation. Open source projects that people aren't being paid to work on probably don't have extensive documentation, because writing extensive documentation is hard, and the kinds of people who like hacking on code that solves their problems are probably not people who enjoy writing extensive documentation when they could be implementing another feature. Even if a large segment of their users would prefer that, and it's what would be best for the project.