[qsort]

I think it very much depends on what problems you're trying to solve and whether or not proper data types have been defined.

If your primary data structure is

  Map<Integer, List<String>>

we have a huge problem.

On the other hand, if your primary data structure is

  Map<CustomerId, List<Purchase>>

Then I'd rather see that than IPurchaseMappingByCustomerIdAbstractFactory or whatever other abomination OO priests will conjure. Generally speaking, generic structures are simpler and they allow for easier transformations.

[marcosdumay]

The article doesn't explain, but links into a deeper one. The author really means you should use Map<Integer, List<String>>.

He also seems to be unaware that you can have generic code with specific types.

[weavejester]

You can still use types, as long as they don't encapsulate the data. Admittedly this is hard to do in some languages.