I would then state that the system your module lives in needs better self documentation. It is achievable, even with large scale and highly sophisticated systems, to be entirely self documenting.
This also includes the test suite as self documentation, as mentioned by @dogweather above. Test structure is important, and titles of tests can reveal lots of information (especially when considering the larger test suite structure).
It often takes a lot of practice, discipline over time, and constantly thinking about the long term intentions of the component of the system youre working on. The more you focus on self documentation, the more natural it will feel. Soon you will regard all comments as an opportunity to better self document the underlying code, and have the current system be better named to reflect the biz logic therein. That “0-1%” rule is totally achievable with practice.
I think this would be much harder without code reviews, so having a 2nd person (or more!) read your code is helpful.
And of course Im referring to “comments in code”, or documentation that compiles/ships with your non public software. OSS, consumer-facing APIs, frameworks, and various forms of libraries or plugins certainly need human-facing documentation.