Definitely seen this first hand as well, as well as seen change happen!
While I agree you should not attempt significant rewrites right away, and spend time to develop your knowledge of system...
don't just sit back and wait. That won't help solve the problem.
1. Be up front about your opinions and rally the group around the long-term goal to improve code quality. Do it in a positive manner where it's clear that you want to make an impact and help make changes for the better! (not just complaints)
2. Explain your reasoning clearly (testing, code quality, engineer happiness, etc) and ask for input / get buy-in. Open up the discussion.
3. Bring this feedback up consistently as an important part of your experience at this company (in 1-1's, and other team meetings)
Good ways to do this are when discussing OKRs, retrospectives, etc.
Believe that YOU have the ability to spark a change and develop real pride amongst the team!
If you don't feel this is possible, this is not the right place for you.
While I agree you should not attempt significant rewrites right away, and spend time to develop your knowledge of system... don't just sit back and wait. That won't help solve the problem.
1. Be up front about your opinions and rally the group around the long-term goal to improve code quality. Do it in a positive manner where it's clear that you want to make an impact and help make changes for the better! (not just complaints) 2. Explain your reasoning clearly (testing, code quality, engineer happiness, etc) and ask for input / get buy-in. Open up the discussion. 3. Bring this feedback up consistently as an important part of your experience at this company (in 1-1's, and other team meetings) Good ways to do this are when discussing OKRs, retrospectives, etc.
Believe that YOU have the ability to spark a change and develop real pride amongst the team! If you don't feel this is possible, this is not the right place for you.