I don't have a huge list of experience to pull from.
First thing, legacy code is a great place to see all those coding practices and patterns you've been taught having fallen flat on their face.
Second, you learn how to read code.
Third, you learn what is valuable to communicate.
First off, make sure there is a good test plan in place. This could mean writing new test coverage, but it may also mean relying on a QA department.
Have a plan to get small changes into production quickly.
Look to update the dependencies. Sometimes you can't take it to latest without major architectural changes. But you don't want to be caught unable to do proper development practices because the tool you need is too new.
Fear of breaking something is going to be a huge driver for management. If you aren't able to get support to cover the development appropriately to mitigate those risks, then maybe consider bowing out.
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 don't have a huge list of experience to pull from.
First thing, legacy code is a great place to see all those coding practices and patterns you've been taught having fallen flat on their face.
Second, you learn how to read code.
Third, you learn what is valuable to communicate.
First off, make sure there is a good test plan in place. This could mean writing new test coverage, but it may also mean relying on a QA department.
Have a plan to get small changes into production quickly.
Look to update the dependencies. Sometimes you can't take it to latest without major architectural changes. But you don't want to be caught unable to do proper development practices because the tool you need is too new.
Fear of breaking something is going to be a huge driver for management. If you aren't able to get support to cover the development appropriately to mitigate those risks, then maybe consider bowing out.