Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI documentation you can talk to, for every repo

deepwiki.com

Post reply on HN
Print view View original

51–60 of 132 posts

Re: AI documentation you can talk to, for every repo

#51

Post by esperent »

andybak wrote: post #44
blopker wrote: post #16

I took a look at a project I maintain[0], and wow. It's so wrong in every section I saw. The generated diagrams make no sense. The text sections take implementation details that don't matter and present them to the user like they need to know them. It's also outdated. I hope actual users never see this. I dread thinking about having to go around to various LLM generated sites to correct documentation I never approved…

I just tried it on several of my repos and I was rather impressed. This is another one of those bizarre situations that keeps happening in AI coding related matters where people can look at the same thing and reach diametrically opposed conclusions. It's very peculiar and I've never experienced anything like it in my career until recently.

> people can look at the same thing and reach diametrically opposed conclusions. It's very peculiar and I've never experienced anything like it in my career until recently

React vs other frameworks (or no framework). Object oriented vs functional. There's loads of examples of this that predate AI.

Re: AI documentation you can talk to, for every repo

#52

Post by onion2k »

blopker wrote: post #16

I took a look at a project I maintain[0], and wow. It's so wrong in every section I saw. The generated diagrams make no sense. The text sections take implementation details that don't matter and present them to the user like they need to know them. It's also outdated. I hope actual users never see this. I dread thinking about having to go around to various LLM generated sites to correct documentation I never approved…

I went to the lodash docs and asked about how I'd use the 'pipeline' operator (which doesn't exist) and it correctly pointed out that pipeline isn't a thing, and suggested chain() for normal code and flow() for lodash fp instead. That's pretty much spot on. If I was guessing I'd suggest that the base model has a lot more lodash code examples in the training data, which probably makes a big difference to the quality of the output.

Re: AI documentation you can talk to, for every repo

#53

Post by curl-up »

NewsaHackO wrote: post #28
blopker wrote: post #25

Earlier quoted context omitted.

I dunno, it seems to be real excited about a VS Code extension that doesn't exist and isn't mentioned in the actual documentation. There's just too many factual errors to list.

>I dunno, it seems to be real excited about a VS Code extension that doesn't exist and isn't mentioned in the actual documentation. There's just too many factual errors to list. There is a folder for a VS Code extension here[0]. It seems to have a README with installation instructions. There is also an extension.ts file, which seems to me to be at least the initial prototype for the extension. Did you forget that you…

This thread should end up in the hall of fame, right next to the Dropbox one.

From a fellow LLM-powered app builder, I wish you best of luck!

Re: AI documentation you can talk to, for every repo

#54

Post by Vinnl »

h4ck_th3_pl4n3t wrote: post #14
WhyNotHugo wrote: post #5

I tried a few different repositories (both my own and various other people’s projects). They all yield the same: No repositories found No repositories matching "https://git.sr.ht/~whynothugo/ImapGoose" were found. Probably broken/down right now?

Maybe they only support github?

Yeah, I wanted to try it on my (GitLab) repo as well, but it also said "No repositories found". Clicking "Index any public repo" pops up a dialog that says "Search for a GitHub repository" and "or Enter the URL of a public GitHub repository".

So looks like it's not actually any repository.

Re: AI documentation you can talk to, for every repo

#55

Post by alansammarone »

ramon156 wrote: post #45

I've seen this idea before claude code gemini cli etc were a thing. This is not relevant anymore (unless you surpass these tools). Cool idea, bad timing

I don't know the specifics of this particular tool, I assume it's at most using a couple of passes of (some frontier model with specific system prompt + custom tools, for example code-specific rag + some form of "summarize"). By at most I mean "probably isn't doing anything crazier than that".

But it seems to be producing docs that are better than I tend to see with basic "summarize this repo for me"-style prompts, which is what I usually use on a first pass.

Re: AI documentation you can talk to, for every repo

#57

Post by alansammarone »

theletterf wrote: post #46

You need great pre-existing docs for something like this to work properly. AI must RTFM. https://passo.uno/from-tech-writers-to-ai-context-curators/

It certainly helps, but in my experience you get 60-80% of the benefit just with code (except in legacy or otherwise terrible code, for example with misleading/outdated comments everywhere, bad variable/function names, etc - in that case more like 40%).

Re: AI documentation you can talk to, for every repo

#58

Post by throwaway290 »

NewsaHackO wrote: post #28
blopker wrote: post #25

Earlier quoted context omitted.

I dunno, it seems to be real excited about a VS Code extension that doesn't exist and isn't mentioned in the actual documentation. There's just too many factual errors to list.

>I dunno, it seems to be real excited about a VS Code extension that doesn't exist and isn't mentioned in the actual documentation. There's just too many factual errors to list. There is a folder for a VS Code extension here[0]. It seems to have a README with installation instructions. There is also an extension.ts file, which seems to me to be at least the initial prototype for the extension. Did you forget that you…

here the maintainer says it doesn't exist. there's basically no way another interpretation is "more correct". presence or files can be not intended for use, deprecated, internal, WIP, etc. this is why we need maintainers.

Re: AI documentation you can talk to, for every repo

#59

Post by NicoJuicy »

blopker wrote: post #16

I took a look at a project I maintain[0], and wow. It's so wrong in every section I saw. The generated diagrams make no sense. The text sections take implementation details that don't matter and present them to the user like they need to know them. It's also outdated. I hope actual users never see this. I dread thinking about having to go around to various LLM generated sites to correct documentation I never approved…

What model did you use?

Re: AI documentation you can talk to, for every repo

#60

Post by jorvi »

cuuupid wrote: post #7
jasonjmcghee wrote: post #3

This gets posted pretty frequently. 231 points | 77 days ago | 53 comments https://news.ycombinator.com/item?id=45002092

YMMV, my experience with DeepWiki is that it’s decent but the DX of the documentation is horrible and the diagrams are often just incorrect. Worth mentioning this is a Cognition / Devin on-ramp and has been posted on HN a few times in just a couple months, feels a little sales-y to me.

From the title I assumed it would generate docs to put in the repo.

But it's docs outside the dev's purview on a deepwiki url, used to shepherd people into Devin. Wow. Talk about slimy.

Post reply on HN