"Today, we're launching the Code Wiki website in public preview, our first product built on this new system. It ingests public repositories and generates, hosts, and maintains comprehensive and interactive documentation for each one.Instead of reading static text, you can navigate interactively, jumping directly from high-level concept explanations to the exact code files, classes, and functions they reference. If you get stuck on a complex module, you can ask the Gemini-powered chat agent that uses the always-up-to-date wiki as context to answer highly specific questions about your repository, instantly bridging the gap between learning about the code and actually exploring it. For times when text isn't enough, Code Wiki automatically generates always-current architecture, class, and sequence diagrams, ensuring you can visualize complex relationships that match the exact current state of the code."developers.googleblog.com/en/i#Programming #OpenSource #SoftwareDevelopment #SoftwareDocumentation

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 11 months ago

"This is a case where some docs aren’t better than none, because they signify the triumph of intellectual laziness over trust and accountability. While I’m not concerned about their impact (any enterprise customer would shred you to pieces if you provided docs like those), I think that they represent a trend that we must fight, because docs entirely written by AI are wrong.Let’s draw the line: docs generated entirely by AI should never ship to users. You can use AI judiciously to audit your docs for gaps, to spot inconsistencies, to generate first drafts that you’ll edit later. But the moment you let any LLM have the final word on what users will read, you’ve abandoned the basic contract of docs: that someone who understands the system has taken responsibility for explaining it truthfully."passo.uno/ai-wikis-docs-teathe

  • source
  • parent