Great share here! definitely one of the most common situations for a developer is to come across legacy code.
I think that a good practice to follow to eventually help others devs to deal with legacy code is "modularize your code" - keep the code encapsulated and abstracted according to their functionality can help to understand and refactorize the code in an easier way than if everything is in the same bowl since always is easier understand small pieces of code instead of trying to see the whole tree.
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.
Great share here! definitely one of the most common situations for a developer is to come across legacy code.
I think that a good practice to follow to eventually help others devs to deal with legacy code is "modularize your code" - keep the code encapsulated and abstracted according to their functionality can help to understand and refactorize the code in an easier way than if everything is in the same bowl since always is easier understand small pieces of code instead of trying to see the whole tree.