What's in your RAG?
这条记录涉及编程工具或代码能力更新，适合开发者评估工作流变化和可复用价值。
I want to up my game, with RAG. I tested it ages ago, but haven't found a usecase. I play with coding, projects, and light sysadmin work.
# Thoughts
RFC library - seems verbose unnecessary
industry standards - typically in the model better than my cherry picked documents
Codebase - I don't have the largest code base (fits in context) and it changes too often to index?
Entire API references - this might work for small scripting languages, but for a bigger language (c#, nodejs, etc etc) this seems crazy overhead work downloading and managing hundreds of pages?
I did once put the Google calendar API .md file a folder and access that as a file read, so it worked well but this was such a small file it doesn't really need RAG.
Historical context - maybe for an enterprise app, with 1million lines of code and 10 years of notes yes, but for something smaller like me this seems wrong.
What do you put in your RAG? And for larger data sets (entire API ref guides) how do you manage that long term?