Good code documentation describes why something is done, and no just **what ** or how.
To answer why you have to understand the context, and often, you have to be there when the code was written and went through the various iterations.
LLMs might be able to explain what is done, with some margin of error, but why something is done, I would be very surprised.
buddascrayon@lemmy.world 11 months ago
I can honestly see a use case for this. But without backing it up with some form of technical understanding, I think you’re just asking for trouble.
dermanus@lemmy.ca 11 months ago
100%, we’re doing human and automated reviews on the code changes, and the code explanation is just the first step of several.