Live data from Hacker News

Google Releases CodeWiki

codewiki.google

11–20 of 45 posts

Re: Google Releases CodeWiki

#14
post #6

I don’t understand how this can be more optimal than just reading the documentation that a human already wrote. All “normal” uses can be answered by reading the docs, everything advanced you can just read the code. I’m not sure when I would ever use this?

Generating and maintaining docs is a massive cost. Presumably the point of this is to reduce that cost. And for projects where the existing documentation is poor or nonexistent, this might be far better than what’s available today. How well this actually works, though, I have no idea.

This doesn't replace docs, nor technical writers.

Re: Google Releases CodeWiki

#15
Not sure how this is supposed to show. Does it only show stuff about existing repositories?

I put in the URL for a project of mine in Codeberg and didn't seem to be able to do anything - i expected that it'd go clone the repository, parse the code and attempt to tell stuff about it, but all i got was an error :-P.

Re: Google Releases CodeWiki

#16

I don’t understand how this can be more optimal than just reading the documentation that a human already wrote. All “normal” uses can be answered by reading the docs, everything advanced you can just read the code. I’m not sure when I would ever use this?

I encourage you to put your preference to the test on the NixOS and nixpkgs documentation.

Re: Google Releases CodeWiki

#17

Not sure how this is supposed to show. Does it only show stuff about existing repositories? I put in the URL for a project of mine in Codeberg and didn't seem to be able to do anything - i expected that it'd go clone the repository, parse the code and attempt to tell stuff about it, but all i got was an error :-P.

Apparently gotta request a new repo. Kinda lame.

Re: Google Releases CodeWiki

#19
post #9

I don’t understand how this can be more optimal than just reading the documentation that a human already wrote. All “normal” uses can be answered by reading the docs, everything advanced you can just read the code. I’m not sure when I would ever use this?

Reading a ton of docs and interpreting them is a tedious activity. If you can get deducible or inferable answers with AI, that's a huge win. I have faced issues with kubernetes that needed me to wade through the code for days to find it was a missed case or unsupported. AI would help me in minutes. That's the claim here, if it works that way.

I’ve never had AI understand a problem of that depth though. It can maybe surface the right part of the docs to reference but in the times I have used it it leads me down the wrong path half of the time.
Post reply on HN