Yea, this frustrates me endlessly working in a code base that has the philosophy of no comments is better than bad comments, and as such code should be self des

Yea, this frustrates me endlessly working in a code base that has the philosophy of no comments is better than bad comments, and as such code should be self describing with no comments. "Self documenting" code only describes what is happening, doesn't explain why the code exists, what problems are being tackled, bugs fixed, etc. Makes it very easy to lose behaviours, because it's easy to delete or change behaviour when we don't know why it exists. I sort of think it's common to accidentally comment what is happening, those comments to get out of sync with the code and be otherwise unhelpful, which leads to this overreaction towards self documenting code and having policies limiting comments.