Generally it is recommended that you fine-tune if you want to shape the output style. If you eant ro only output json, or just output jsdoc, etc.
To add knowledge, RAG is a better idea and easier to keep updated on code changes.
If rag does not give back good results then that's a problem with the retrieval part, which can be measured and improved.
We're building documentation + rag systems for enterprise code bases and this is what we saw works best.
I think documentation and tests are and should be as coupled to the original code.
True that docs are not part of CI/CD and can get stale faster. Do you feel there is a huge push for autgeneration though?
> My take is the better approach is similar context enrichment for rag - you ask the LLM to generate a summary for a page,
Curios to hear more about. Are you referring to a doc's page?
They are both super important and complimentary, true. But if you could only do one? Which one would you choose?
I see your point with tests as examples, but I would find those pretty hard to read/find compared to docs. And if the doc's examples are not backed by tests we get into the same problem as docs being outdated.
reply