Reddit thread asks for deeper RAG guides

This is the right kind of question, because RAG starts simple and gets messy fast once you care about retrieval quality, routing, and evaluation in real systems.

• –The post points to the exact gap most builders hit: knowing the API-level basics but not the production patterns.
• –The most useful resources here will be hands-on repos, evaluation guides, and advanced demos, not generic “what is RAG” explainers.
• –The mention of knowledge graphs and routing suggests interest in modern hybrid RAG patterns, not just chunk-and-embed workflows.
• –For developers, the real lesson is that RAG is an architecture family, so learning should span indexing, retrieval, reranking, grounding, and measurement.