[jmalicki]

My favorite thing is when some projects now have better documentation in their Claude skills or MCPs than they ever did for users.

[danappelxx]

There is natural incentive for engineers working on a project to keep Claude skills up to date. I cannot say the same for general documentation.

[cousin_it]

But maybe not for long. When we get long-running AIs, the knowledge locked inside the AI's thinking might supplant docs once again. Like if you had an engineer working at your company for a long time and knowing everything. With all the problems that implies, of course.

[andsoitis]

at any time you can ask the model to produce documents given the latest state of the code base and at an altitude you choose.

[jmalicki]

That's the weird best thing about LLMs - there is finally incentive for projects to create documentation, CLIs, tests, and well organized modular codebases, since LLMs fall flat on their face without these things!

[Yoric]

Yeah, I joined a project a couple of months ago, felt completely lost.

Last week, a colleague finally added for Claude all the documentation I'd have needed on day one. Meanwhile, I'm addressing issues from the other direction, writing custom linters to make sure that Claude progressively fixes its messes.

[yks]

But that documentation itself is likely AI-generated

[jmalicki]

At least it saves me from having to generate the docs myself!

[MichaelZuo]

Why continue involvement with a project that clearly devalues their “customers” or “users” who care about documentation?

[jmalicki]

Projects that spend time on documentation for my robots have shown me they care about my use case!