It's time to move your docs in the repo
Summary
The article argues for moving documentation into the code repository to leverage version control, proximity to code, and automated testing/generation. It posits that AI makes documentation-driven practices more meaningful, suggesting that most files in a repo should serve human readers and that rules files may evolve into documentation. It also discusses the trade-offs with collaboration tools like Google Docs and considers security and access implications.