> I have the joy of refactoring thousands of lines of code just so I can build the new features the 'right' way. Maybe don't do that. Build what you CAN the 'r

> I have the joy of refactoring thousands of lines of code just so I can build the new features the 'right' way. Maybe don't do that. Build what you CAN the 'right' way, accept some shitty code, and most importantly - don't try to kill all the shitty code on your own as a side objective. Take a step back. Look at what is required of you personally. If you can make a case of rewriting the shitty parts, then do that. Presumably if the old bugs are catching up and wastes a lot of time for you and your team, and pisses of the customers, then it it won't be any problems to make the case for rewriting the worst parts. That means that other things have to be prioritized lower. If you can't sell a refactorization, maybe because it's not worth it - as in no economical benefits, maybe you need to adjust your expectations. Shit happens, also in code. You are not paid to write code "the right way". You are paid to write whatever that brings in the money. If you can't sell it although there is a clear economical benefit, then find another job. Good luck.