I'd say that one of the first steps to do is to introduce tests. General ones at first, more specific later as you advance in refactoring.
If a part of the code is not easily testable, it's a good candidate for refactoring.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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 say that one of the first steps to do is to introduce tests. General ones at first, more specific later as you advance in refactoring.
If a part of the code is not easily testable, it's a good candidate for refactoring.