> I've taken to a rash practice of just tearing out tightly coupled, untestable, duplicated and poorly designed code by the roots. Hello me, from a parallel un

> I've taken to a rash practice of just tearing out tightly coupled, untestable, duplicated and poorly designed code by the roots. Hello me, from a parallel universe! You've basically described the project I'm currently assigned to and the situation I'm in as well, and I share your enthusiasm for "weeding" out obvious turds and warts from the codebase. Unfortunately I've reached a new kind of roadblock when it comes to improving and refactoring the project: I've picked all the low-hanging fruit, and now if I tug at any of the remaining lose ends the whole thing will unravel. Basically the remaining pain points are architectural ones (that will hurt us at scale) and that require attention but at the same time are large enough that management won't approve the necessary resources to work on them. Honestly I almost feel as if I've fucked myself over by making those improvements: the project is now mediocre as a whole, but just good enough so that nobody really cares about improvements any more. Had I just let the ship sink, maybe something better would have come out of this whole mess in the end. Not sure what the lesson here really is! :|