People who get upset if you touch their code.
I think in your other comment you missed the fact that there was already an ongoing debate about this particular part of the code, and it wasn't going anywhere. In such a case a demonstration that the other method is faster is more compelling than more fruitless debate. Speculations on other reasons why the code should've used 2 processes is useless, as it is clear from the article that this change made it possible to get things done faster, no need to argue with that.
"People who get upset if you touch their code" which is what i mean when i said that some people treat their code as their baby.
I wrote it before the debate began, it just got posted after it, that is not in my control.
The speculation was to point out that he didn't managed the situation properly, he just dismissed the current implementation as idiotic and proceed to change it. But you missed my point too. Which is why in some scenarios run faster might not be the first priority.
With "the debate" I referred to what is mentioned in the article of the two departments who disagreed about the best strategy.
I don't quite follow you. In the article it's made quite clear that people wanted the code to run faster because then they could get more work done. Yes there are conceivable scenarios in which faster code is not better, but the article made clear that it wasn't the case, so I think the speculation didn't add anything.
