The Knowledge: Towards a Culture of Engineering Documentation
summary
Google finds 48% of engineers cite missing trustworthy docs and discovers 137,000 internal Sites with 90% unused, so engineers embed markdown docs next to code in the monorepo and serve them via a renderer at predictable URLs. The project g3doc ships server-side rendering, IDE links, search and integrations; adoption climbs from a few pilot sites to ~10,000 projects, 17,000 authors, 200k files, 200k change lists, 3.9M monthly page views, and 30% of doc edits land with code — a clear reduction of friction and rising maintenance.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:49Engineering Documentation
- 2:03Problems with Engineering Documentation
- 8:23Why Did this Project Start
- 20:34Meaningful Integrations with Workflow Tools
- 22:03Page Info
- 25:42Core Values
- 30:14Virtuous Change Lists
- 32:53Tooling Comes First
related talks
44mCreating a Culture of Documentation
31mGREAT BIG ENGINEERING ORG; itty bitty docs team
21mTechDocs: Unlocking the Potential of Engineers' Collective Knowledge
42mEngineering Documentation
44mPushing documentation (so it doesn't hurt anymore)
56mEffective Documentation: The Key to Open Source Growth
05mDocs as Part of the Product: Open Source Technical Documentation at Scale
47mEngineering Documentation