Depends on how old the codebase is and how the development process lookes like. I'm willing to improve and refactor a code-reviewed, tested, active codebase - but maintaining a 12-year-old codebase without code reviews and version control has been a real struggle for me.
I only see two ways of avoiding such a state:
Continuous refactoring in short cycles (feature branches can prevent this, though)
Splitting up the codebase into standalone microservices that are re-writable within 2 weeks.
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.
Depends on how old the codebase is and how the development process lookes like. I'm willing to improve and refactor a code-reviewed, tested, active codebase - but maintaining a 12-year-old codebase without code reviews and version control has been a real struggle for me.
I only see two ways of avoiding such a state: