dex responds to the delete-the-wiki argument: documentation summaries are only necessary when they speed things up without reducing quality
dex said he cannot endorse the "$32 million paper," but agrees with the distinction between "codebases for humans" and "codebases for agents." He believes that documentation or summaries compressed by directory hierarchy are only necessary when they speed things up without reducing quality; otherwise, the simpler approach is to accept a slight loss of speed and read from the source every time. He also pointed out that if the codebase is closed-source, documentation such as mintlify can serve as a "primary source" for users' agent integrations.
Topics
View original postNo. We've got to stop applying old human-centric patterns to working in the new era. delete all your wikis. have an agent answer questions from source instead. at spawn we have: - zero dashboard tools - zero docs - we do not make or use summaries everything we do is primary sources + intelligence Nothing to go stale Nothing to organize Nothing to navigate Always exactly up to date Perfectly personalized The answers get better with every model If we want to see a chart, we ask for it, and we have it in a minute If we want an answer to a question, we ask it, and we have a to-the-minute correct answer
View original
No. We've got to stop applying old human-centric patterns to working in the new era. delete all your wikis. have an agent answer questions from source instead. at spawn we have: - zero dashboard tools - zero docs - we do not make or use summaries everything we do is primary sources + intelligence Nothing to go stale Nothing to organize Nothing to navigate Always exactly up to date Perfectly personalized The answers get better with every model If we want to see a chart, we ask for it, and we have it in a minute If we want an answer to a question, we ask it, and we have a to-the-minute correct answer
Body
I cannot cosign the $32m paper but yes I am nodding along to this one pretty hard
Only reason for any kind of doc/summary (eg compacted summary per dir down the hierarchy) is if it increases speed without reducing quality , but unless you’re buildings evals specific to your codebase watching like a hawk, simpler answer is live with a little speed hit and just go from source every time
I still can’t get over the overall framing of “codebases for humans” vs “codebases for agents”
And also mintlify/docs in general probably serve as one of those “primary sources” if your codebase is closed and your users’ agents need a primary source to integrate it