Makes sense because LLMs are quite good at translating between natural languages.

Anyway, we're reaching the point where documentation can be generated by LLMs and this is great news for developers.

saagarjha 5 hours ago | parent | next [-]

Documentation is one place where humans should have input. If an LLM can generate documentation, why would I want you to generate it when I can do so myself (probably with a better, newer model)?

	▲	simonw 4 hours ago \| parent \| next [-]
		I definitely want documentation that a project expert has reviewed. I've found LLMs are fantastic at writing documentation about how something works, but they have a nasty tendency to take guesses at WHY - you'll get occasional sentences like "This improves the efficiency of the system". I don't want invented rationales for changes, I want to know the actual reason a developer decided that the code should work that way.
	▲	ACCount37 4 hours ago \| parent \| prev \| next [-]
		That's great if those humans are around to have that input. Not so much when you have a lot of code from 6 years ago, built around an obscure SDK, and you have to figure out how it works, and the documentation is both incredibly sparse and in Chinese.
	▲	amelius 3 hours ago \| parent \| prev [-]
		Because it takes time and effort to write documentation. If people __can__ actually read undocumented code with the help of LLMs, why do you need human-written documentation really?

▲

james_marks 6 hours ago | parent | prev | next [-]

I stumbled across a fun trick this week. After making some API changes, I had CC “write a note to the FE team with the changes”.

I then pasted this to another CC instance running the FE app, and it made the counter part.

Yes, I could have CC running against both repos and sometimes do, but I often run separate instances when tasks are complex.

▲

monsieurbanana 6 hours ago | parent | prev [-]

Maybe documentation meant for other llms to ingest. Their documentation is like their code, it might work, but I don't want to have to be the one to read it.

Although of course if you don't vibe document but instead just use them as a tool, with significant human input, then yes go ahead.

	▲	dunham 5 hours ago \| parent [-]
		Although with code it's implementing functions that don't exist yet and with documentation, it's describing functions that don't exist yet.