I think it's not so much about reading the code itself, but how it changed over time. How you refactored your way out of a mess, radically changed a particular feature or fixed a bug without causing ripples.
So even if your code looks shitty, someone realizing that it incrementally became less shitty as they move up the commit log can be pretty useful, IMO. It tells them about the dev's ability to adapt to change while maintaining a certain harmony in the code, sticking to patterns, standards etc.
Plus, people also like to look at how good your tests are; as in, do they logically cover a significant part of the app's functionality.
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 think it's not so much about reading the code itself, but how it changed over time. How you refactored your way out of a mess, radically changed a particular feature or fixed a bug without causing ripples.
So even if your code looks shitty, someone realizing that it incrementally became less shitty as they move up the commit log can be pretty useful, IMO. It tells them about the dev's ability to adapt to change while maintaining a certain harmony in the code, sticking to patterns, standards etc.
Plus, people also like to look at how good your tests are; as in, do they logically cover a significant part of the app's functionality.