3 ms·
> I have to assume there's industry wide misunderstanding on this term? The "misunderstanding" is at least as prevalent as the original, yes. I wasn't trying t
by dllthomas 2y ago
> I have to assume there's industry wide misunderstanding on this term?
The "misunderstanding" is at least as prevalent as the original, yes. I wasn't trying to say the original is "correct" - language is determined by usage - just wondering which you were discussing.
> To avoid the confusion, it seems like DRY would be better named something like "Single source of truth".
It could probably do with a better name, but "single source of truth" is usually about the information operated on by the program, rather than information embodied in the program.
- mewpmewp2 2y agoYou mean it's databases rather than what is in code? If so, then that's also news to me. I'd have thought that e.g. something like input validation code that can be reused both in backend and client would go under single source of truth. Which I would always prefer not to be repeated, but frequently hard to do unless you have same language in backend and frontend or codegen.
- dllthomas 2y agoWith a sufficiently broad definition of "database", yeah, that's my understanding.