The uber coder could have batted that out in an afternoon, but instead spent a week ensuring that histogrammer behind the report was multi-core aware and could scale to billions of data points without dragging the system to its knees.
That is all good except that it may be totally useless. The solution may be scalable for millions of data BUT if the application never needs to handle more than a few thousands of data, then the solution is just over engineering.
The ubbercoder should have implemented a good, simple, correct solution that fits the data that the application must actually deal with. Instead, he just wasted time playing with himself.
There are limits...