3 ms·
Immutability is quite nearly the opposite of useful here. The most common way for data to be wrong is at the interface boundary: it was entered wrong in the fir
by naniwaduni 7y ago
Immutability is quite nearly the opposite of useful here. The most common way for data to be wrong is at the interface boundary: it was entered wrong in the first place.
- drpyser 7y agoImmutability, the way I think the author means it, doesn't mean data can't be changed ever, in any way. It just means that modifications(e.g. corrections) cannot completely overwrite previous values without leaving any trace, but instead have to appear as amendments, visible alongside the previous versions of the data. If it was entered wrong, you can issue a correction, but a trace of the first, wrong value will stay available. That means nobody can just say something was never what it was, just that it changed(and then have to justify why).
- ryacko 7y agoAn interface should avoid unintentional mistakes. Easier to detect invalid signature or hash paired with other signature or hash versus an incorrect name or other ID.
- deleted 7y ago[deleted]