Post

The definition of DRY, from "The Pragmatic Programmer" > Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. It has never been about whether you repeat lines of code. Never.

Are we using the wrong term? Capital DRY literally says that. Is that part of the problem?

I mean I think it's a fact in retrospect that choosing a term that sounds self-explanatory seems to have a led to a lot of people deciding they know what it means without checking. There was certainly discussion of terminology; "Once and Only Once" was another popular phrasing.

I don't know if OaOO would have been better. I suppose this is argument in favor of "inscrutable" names of principles, like "The Law of Demeter" - you kind of HAVE to look them up instead of assuming you know.