[rstagi]

Honestly same way I did before, checking periodically. There's a real challenge though: I'm getting less and less knowledgeable about the details of my own code, so it's hard to fact-check everything all the time.

Anyway, for now we're assisting to either outdated Docs (Coding Agents often don't even look at them), or to over-bloated ones (the slop is not just in the code). We should probably still find a balance between human readable docs (e.g. README.md) and LLM-tailored ones (e.g. llms.txt)

[ghosts_]

Would you consider introducing any tooling around that? I've been building an automation setup for keeping dev docs up to date (and eventually user-facing knowledgebase docs) but would love to chat with other developers to make sure I'm doing the right thing or meeting the right needs. For me the focus was introducing easily readable / digestible docs, including mermaid diagrams where they are useful, linking to other parts of the code / docs, etc. and then a layer on top is a basic "Q&A" feature (you could do the same in any AI tool realistically) but something that surfaces docs or generates them on demand based on where the knowledge gaps are.