3 ms·
I can do small bits progressively, but a major refactor has been shot down by leadership Why? Ask. Maybe it solves problems well enough and maintenance costs a
by anigbrowl 4y ago
I can do small bits progressively, but a major refactor has been shot down by leadership
Why? Ask. Maybe it solves problems well enough and maintenance costs are low enough that they'd rather you were contributing to Y instead of reworking X to be better for programmers but not have a noticeable impact on the bottom line. Understanding where that functionality fits into the business model will probably help you understand the development constraints better and worry less about the issue. It might also indicate that the management are being shortsighted or not really listening to feedback from their engineering people.
If you hear a negative comment from someone else, it's good that you realize it's about the problematic code rather than you. You could (again) ask how they'd approach the issue, given that you can't get resources to cover the cost of a refactor. Maybe they can team up to persuade management? Or maybe they can suggest a way to get it done faster. Maybe you can prototype the better version and then use that to change the suits' mind. Meantime, if your fellow team members don't have a full understanding and they are not the ones who had to land the plane, then you should discount the weight you assign to their approval.