One thing I advocate for in refactoring is not to refactor in order to reduce duplication or make code more readable, or anything of that sort. Instead, I propose that one should refactor when making a needed change starts to get hard. If some additional logic we wish to introduce doesn't fit, then we refactor first so that the new behaviour can just slide into place. This way things like readability and reduced duplication become a byproduct of making the code easier to work with on tangible pieces of 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.
One thing I advocate for in refactoring is not to refactor in order to reduce duplication or make code more readable, or anything of that sort. Instead, I propose that one should refactor when making a needed change starts to get hard. If some additional logic we wish to introduce doesn't fit, then we refactor first so that the new behaviour can just slide into place. This way things like readability and reduced duplication become a byproduct of making the code easier to work with on tangible pieces of functionality.