code-as-docs will never tell you why method or a module exist in the first place.
If I could wave a magic wand and make all the colleagues verbalise what they’re doing, I would.
In the meantime, I’ll take the downvotes for pointing out that it’s fundamentally caused by a cultural gap, not just “those who don’t get it yet, and those who do.”
The great thing about issue threads is that you can add more context to them later on - unlike commit messages which are frozen in time.
Many Github issue threads that I read are incomprehensible. The thread is not where the story is (it's in the memories of the people involved). Explaining is work. This is why they make kids write reports as assignments in school.