Re:A rare topic (Score 1)

I have actually seen this quite a bit in my own company. The question becomes why change something that isn't broken?

Well the only answer that I have found is that it uses hours that need to be assigned to salary employees. I work on a simulator that uses very sophisticated algorithms for some of its models computation. It is amusing to see an algorithm that worked nearly 10 years ago flawlessly, get changed because some programmer sitting at a desk decided that he didn't like how the code looked.

If its not broken, keep your fingers out of it!