![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
Somewhat
May. 21st, 2009
02:38 pm - nngh
They say that survivor's guilt means that you survived.
The layoff hammer missed me by a hair today, but it's going to be pretty quiet around here.
Mar. 15th, 2006
03:47 pm - A question for my fellow code-monkeys out there
Hey all you code monkeys out there! It's an "is there a name for that thing where..." question.
Is there a name for that thing where, in object-oriented programming, you can't figure out for some operation that acts on objects A and B, whether the initial method belongs in A or in B? Like, person A is going to buy something from person B, and you can't really come up with a good argument for whether the entry point should be A.buyFrom(B) or B.sellTo(A).
I am making an argument tangentially relating to a case of this and I realized that I don't have a name for it and the explanation of this trivial thing is taking over the document as a result. But it's such a common occurance that it must have a name of its own.
(And yes, I know there are many modern programming methodologies and languages and design cults that avoid this problem, and object-oriented programming is a hideous throwback to our bloody stone-age history, &c. Not my point.)