Just recently discovered Devins DeepWikis and love them. Same idea, talk to your repo, right? What does Sourcebot doe differently / better? https://deepwiki.org/
Yea it's a similar idea - DeepWiki has the generated "wiki" part which we think is really cool (and maybe we'll add something similar in the future). The core chat experience is the same idea - we had some UX inspiration since we think they nailed the experience.
Deepwiki's context retrieval seems to be more sophisticated. I'm speculating, but I imagine they are using the generated wiki + embeddings which probably gives them higher recall over the codebase, vs. how we are using precision search.
Sourcebot has more "IDE" features built into the product like a file explorer and code navigation, which makes it easier to use the AI-generated answer as a jumping off point for further code exploration.
So, what would have happened if they hired him? Would he have his AI mask on in all future calls. Clearly this would not be sustainable, or? Im confused.
My daily driver for the last year or so. But it really is an acquired taste. Some colleagues love it and now use it as well, some hate looking at it and comment on it every time I share my screen.
I recently also wanted to play around with some itunes podcast data. But it seemed Apple removed the scrapable catalogue index of their podcast library. How did you build up your database, if i may ask?
Thanks for the link. This illustrates my concern pretty well. Instead of having one highly relevant index we now have a multitude of smaller services that hold information about the podcast universe. And afaik they dont confederate in any way. So one would need to query all of them...