Ashley Rolfmore (leymoo)<p>I’m starting to think that anyone who designs or builds systems that handle data should do a basic bookkeeping course that covers how double entry works. </p><p>The accountants managed to work out for us since the 13th Century that if you move money from A to B, both A and B need an audit entry describing the movement each way. Write only - nothing is removed. Yet I don’t see an equivalent teaching in the various system design books, despite this concept being fundamental to any system that needs (financial and non-financial) auditing capabilities. </p><p><a href="https://hachyderm.io/tags/databasedesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>databasedesign</span></a> <a href="https://hachyderm.io/tags/DatabaseDevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DatabaseDevelopers</span></a> <a href="https://hachyderm.io/tags/systemDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemDesign</span></a> <a href="https://hachyderm.io/tags/Accountancy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Accountancy</span></a> <a href="https://hachyderm.io/tags/Audit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Audit</span></a></p>