Notes on documentation that keeps up.
Longer pieces on documentation drift: why pages go out of date, what makes one checkable rather than merely written, and what changes when most of the code is produced by an agent. Written while building Wiki Pilot, and honest about the parts it doesn't solve.
How to document a software project automatically
What automatic documentation can and can't do for an existing codebase, the three kinds of tool that claim to do it, and a step-by-step run that produces a docs site from a repo.
ReadWriting a codebase wiki on your Claude plan, not API credits
Wiki Pilot 0.7 can run its AI investigation inside Claude Code, so a Pro or Max subscription covers it. What that changes, what the agent is allowed to touch, and what else shipped with it.
ReadWhat actually belongs in a codebase wiki
Ten sections and the argument for each. Most internal wikis fail at the structure step, long before anyone runs out of willingness to write.
ReadYour docs aren't wrong. They're unverifiable.
Documentation doesn't rot because people are lazy. It rots because nobody can check it. Two fields in the frontmatter change that.
ReadDocumentation drift in the age of coding agents
Drift isn't new. The rate is. And now the docs feed back into the tools writing your code, which is a failure mode we didn't have before.
ReadNew posts are infrequent and only when there's something worth saying. Subscribe by RSS, or follow the repo.