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.
Exactly. Often this information is not actually present in the code itself which is exactly why I would want documentation in the first place, given that I can always read the code myself if needed.
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.