#DatabaseDevelopers

Ashley Rolfmore (leymoo)Also; if your previous technology choices made this hard... That means a wider discussion to fix it, and don’t let outside people pressure you into compromising on data intregity in systems that need auditing. The bad ones will throw your reputation away anyway if they pressure you to do bad work and it messes up later <a href="https://hachyderm.io/tags/databasedesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#databasedesign</a> <a href="https://hachyderm.io/tags/DatabaseDevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#DatabaseDevelopers</a> <a href="https://hachyderm.io/tags/systemDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemDesign</a> <a href="https://hachyderm.io/tags/Accountancy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accountancy</a> <a href="https://hachyderm.io/tags/Audit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Audit</a>

Ashley Rolfmore (leymoo)The nuance that seems to come up is parent records with child records - ie if you remove the association, the associated child audit entries disappear. Its easier to see the issue if you remove this type of record keeping to other situations- ie if a foster parent looks after a child, say the kid breaks a leg playing football while under the care of the carer, then the kid moves on…. You’d want to know that both the kid had the accident with the carer and that the carer looked after a kid that had an accident while with them. Both sets of information either end are needed. The accident shouldn’t disappear from the carer’s record. Yet you hear this from system designers or developers. <a href="https://hachyderm.io/tags/databasedesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#databasedesign</a> <a href="https://hachyderm.io/tags/DatabaseDevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#DatabaseDevelopers</a> <a href="https://hachyderm.io/tags/systemDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemDesign</a> <a href="https://hachyderm.io/tags/Accountancy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accountancy</a> <a href="https://hachyderm.io/tags/Audit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Audit</a>

Ashley Rolfmore (leymoo)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. 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. <a href="https://hachyderm.io/tags/databasedesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#databasedesign</a> <a href="https://hachyderm.io/tags/DatabaseDevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#DatabaseDevelopers</a> <a href="https://hachyderm.io/tags/systemDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemDesign</a> <a href="https://hachyderm.io/tags/Accountancy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accountancy</a> <a href="https://hachyderm.io/tags/Audit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Audit</a>

Recent searches

Search options

Administered by:

Server stats:

#databasedevelopers