I'd start by saying each of the following are "means to an end", and not "ends to a mean".
The actual "end" is building value thru code quicker/more-efficiently for end users. Doing so requires you to be able to do things "fast" and more reliably, which in turns leads to investments in coding patterns, re-using code, documenting, testing and the like.
However, when taken in the context that documentation/testing/modular code is just a "means to an end" you actually need to consider that documentation/testing/modular code is actually somewhat "in the way" of progress. If your code works perfectly, you don't need tests. If its self documenting then you don't need docs. If you aren't re-using anything, then it doesn't need to be reusable. If its already simple, then you don't need it to be modular.
Of course getting to such a state might be plainly impossible in all facets, but keeping the context in mind can help reduce the investment in these realms as they are just "means to an end".
Finally, reducing how much time/effort put into these aspects could help get you to the real "end". Utilizing tools/patterns/approaches that integrate these aspects with as minimal amount of work should always be the goal.
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'd start by saying each of the following are "means to an end", and not "ends to a mean".
The actual "end" is building value thru code quicker/more-efficiently for end users. Doing so requires you to be able to do things "fast" and more reliably, which in turns leads to investments in coding patterns, re-using code, documenting, testing and the like.
However, when taken in the context that documentation/testing/modular code is just a "means to an end" you actually need to consider that documentation/testing/modular code is actually somewhat "in the way" of progress. If your code works perfectly, you don't need tests. If its self documenting then you don't need docs. If you aren't re-using anything, then it doesn't need to be reusable. If its already simple, then you don't need it to be modular.
Of course getting to such a state might be plainly impossible in all facets, but keeping the context in mind can help reduce the investment in these realms as they are just "means to an end".
Finally, reducing how much time/effort put into these aspects could help get you to the real "end". Utilizing tools/patterns/approaches that integrate these aspects with as minimal amount of work should always be the goal.