2 ms·
You might not have any observable effects until the day you do, at which point you may be faced with an arbitrarily large problem. What you are doing is passin
by mannykannot 9y ago
You might not have any observable effects until the day you do, at which point you may be faced with an arbitrarily large problem.
What you are doing is passing up on the opportunity of catching various errors (you are also passing up the opportunity for some optimizations, but that is probably a secondary issue.) In particular, you are passing up on some opportunities to catch inconsistencies in how different applications (or different parts of the same application) create and use data.
One argument made against putting these sort of rules in effect is that they constrain what application developers can do, but that is the wrong way to look at it: any such conflict is an indication of a misunderstanding (not necessarily on the part of the application developers) that has been caught before it can lead to bigger problems, such as a database full of irretrievably inconsistent or incomplete data.
When the problems finally do arise, it is often the case that some sort of workaround is the only practical solution. This, in my experience, is one of the common ways by which systems accrue gratuitous complexity, which in turn has at least two real-world consequences: an increased time to make changes, upgrades and extensions, and an increased frequency of errors, especially WTF-type errors (and probably also efficiency/performance hits.)
- gxs 9y agoI think OPs question was exactly asking the question of when these problems do arise, not how large they are when they do. I'd be curious to hear when they do, would be great if you had some real world examples.
- mannykannot 9y agoMy point is that you cannot know when problems will show up. If you do everything right, they will never happen, but why pass up an opportunity to reduce the risk?