I completely agree with you. The best documentation is the code itself, mostly without comments and good bunch of unit tests.
If you make any comments, they shouldn't be about the whats (the names should be clear enough to make such comments superfluous), but they should be about the whys, about intentions.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I completely agree with you. The best documentation is the code itself, mostly without comments and good bunch of unit tests.
If you make any comments, they shouldn't be about the whats (the names should be clear enough to make such comments superfluous), but they should be about the whys, about intentions.