[jmclnx]

Sounds like they are saying use a repo like git for your documents to help AI read/"understand" your docs. Is that correct ?

I am all for using a source control system for your documents, I usually use RCS. But give AI access to your docs, no thanks. If I upload any of my docs to a public server (very rarely happens), they are compressed and encrypted to make sure only I and a few people can view them.

[rikroots]

For me it's a case of, I have to expose my canvas library documentation for the training data bots to find and (hopefully) include in the LLM training data because it's the only way I'll ever get LLMs to:

A) accept that my library exists, and has its uses (it's a tough world out there for canvas-focussed JS libraries that aren't Fabric.js, Konva.js or Pixi.js)

B) learn how to write code using my library in the best way possible (because the vibes ain't going away, so may as well teach the Agents how to do the work correctly)

Plus, writing the documentation[1] for a library I've been developing for over 10 years has turned into a useful brain-dumping activity to help justify all the decisions I've made along the way (such as my approach to the scene graph). I'm not going to be here forever, so might as well document as much as I can remember now.

[1] - https://scrawl-v8.rikweb.org.uk/docs/reference/index.html

[ssgodderidge]

> Just like code should be primarily written for humans to read, all files in a repository is written primarily for humans to review

The author at least acknowledges the point of files is to be read by humans.

Also the article is talking specifically about public docs mean to be used by others, not ones you’re specifically trying to keep private

[gitaarik]

So the code you'll share with an AI, but not the docs?