517 karma · joined February 23, 2019
So yes you can certainly use to index and query your own repos for yourself, but it's also a way to get more of your OSS lib users onboarded.
At the beginning, we started with qualitative "vibe" checks where we could iterate quickly and the delta in quality was still so significant that we could obviously see what was performing better.
Once we stopped trusting our ability to discern differences, we actually bit the bullet and made a small eval benchmark set (~20 queries across 3 repos of different sizes) and then used that to guide algorithmic development.
We stress-tested with repos like langchain, llamaindex, kubernetes and there the retrieval still needs work to effectively return relevant chunks. This is still an open research question.
For the time being, indexing and retrieving a good collection of 10-20 code chunks is more effective/performant in practice.
That being said, our goal was to make the library modular so you can easily add support for whatever embeddings you want. Definitely encourage experimenting for your use-case because even in our tests, we found that trends which hold true in research benchmarks don't always translate to custom use-cases.
This is a great idea. Definitely something we plan to support.
Thanks for taking the time to check out the project and for your very insightful comments. It appears like Amazon's storyteller was discontinued in 2015 so it didn't end up being as useful as promised.
I think the real power is in what you described: "how to translate the story from script to screen for optimum storytelling power and production cost." This is a nuanced question because that translation seems difficult to get right (how does one incorporate signals about production cost, etc.) Would love to get more of your thoughts here.