Roedy said:
I have always used the phrase "comes out in the wash" for a
programming simplicity principle.
FWIW, the meaning you ascribe to "comes out in the wash" is not the one
I grew up with (I'm British). For me the phrase is usually "it'll come
out in the wash" or "it'll all come all out in the wash", and means
that we'll find out whether <something> is really a good idea when we
apply
it in the real world. (Compare "the proof of the pudding is in the
eating"). For instance:
A) "I've nailed up all those bookshelves. They seem pretty solid, but
books are /heavy/ do you think they'll stand the strain ?"
B) "Dunno. They /ought/ to. It'll come out in the wash."
or:
A) "The <X> party claims that it's all for environmental protection;
I bet they'll back off quick if they ever get into power."
Surely it also has a grander academic name. What is it?
Referring to your meaning of the phrase, I'd say it is either a
property of the algorithm that it does not require special cases
("elegant", "simple") or a property of the /expression/ of that
algorithm that it manages to bury the special cases in main-line code
("clever", "cunning", "brittle"). There are intermediate cases too, of
course.
Another phrase -- not academic -- that I hear used for code that turns
out to accommodate not-obviously-anticipated demands is "it just works"
(or, more ironically: "it Just Works(tm)").
-- chris