> We can't communicate if you hyper fixate on one tree when our discussion is about the forest. All I'm saying is you can't expect perfect code in impure syste

> We can't communicate if you hyper fixate on one tree when our discussion is about the forest. All I'm saying is you can't expect perfect code in impure systems. > You are not a mindless automata directed by your manager. I never said I was, but I also can't turn a ship on a dime. I'm asked to perform a task; I'm going to perform to the best of my abilities, but in impure systems the best you can do is patch the leaking part with code and do some basic refactoring. Any moment spent trying to simplify and fix the software will be rightfully considered a waste. Because a feature sold is better than performance gained (unless it's utterly abysmal). > The goal is to put all the puzzle pieces on the table, put the right ones next to each other and let them put the final pieces together. If they don't then they don't feel like they did anything. Again, in impure systems half the puzzle pieces have left, some other parts of other puzzles have been mixed, and it's the clock is running. The more you focus on cleaning code, the more you are falling behind feature wise. Up until a point that you can present to managers "Shit is very bad, we need to refactor."