Technical debt is struggle for everyone. I have (sadly) some experience on working with old code-base.
What I feel works best (professionally speaking) is to address the issue steps by steps. The smaller the steps, the better. Pareto principle style !
Maybe start with code formatting as it has little chance to take time or break something.
Then code your feature. If you have some time left, start to think of refactoring.
I sometimes feel like you, but often, I make change that won't be merged because :
It break some weird use-case
Take too long to be reviewed
Just too risky
Of course, you should try to improve. We all have down time, use them to clean your old piece of code.
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.
Hi Poof,
Technical debt is struggle for everyone. I have (sadly) some experience on working with old code-base.
What I feel works best (professionally speaking) is to address the issue steps by steps. The smaller the steps, the better. Pareto principle style !
Maybe start with code formatting as it has little chance to take time or break something.
Then code your feature. If you have some time left, start to think of refactoring.
I sometimes feel like you, but often, I make change that won't be merged because :
Of course, you should try to improve. We all have down time, use them to clean your old piece of code.