Recently while working in our HR system I came across some interesting OO design.

&someobject.ShopForEmployees();
....
....
&someobject.CopyShoppingCartToRowset(&RS_Employees); 

I would expect this kind of terminology from an HR person (employees being just commodities that can be thrown in a shopping cart), but what developer with any self respect would write up code like this? They, after all, are just an employee.

Besides the method naming, the code had a lot of problems and didn't work as documented. That I expected, but would have been easier to take if the naming wasn't so offensive.