In a complicated legacy codebase, do you refactor or keep writing dirty hacks?
I’m working on a bug and know of a solution. One solution involves refactoring HUGE chunks of code (some of which I don’t understand but it depends on the code that I need to change, I think?) that could potentially break a lot of things, take significantly longer than a single sprint, and quite frankly is above my pay grade. It’s just fucking painful and soul crushing. On the other hand I could write a dirty hack to get things working, then cross it off my list and hope I never have to come back to that part of the codebase. I feel like in an ideal world it would be great to do the right thing but in practice people have shitting on this code for nearly two decades so who cares if I add more shit on top of it?