From 20bbba0cc8c8a515df4c79ef3d84f21e4c9ddc11 Mon Sep 17 00:00:00 2001 From: Chris Walters Date: Wed, 29 Sep 2021 09:48:34 +0100 Subject: [PATCH] initial thoughts on statements around data processing principles --- principles.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/principles.md b/principles.md index af7ce90b..3f2420a4 100644 --- a/principles.md +++ b/principles.md @@ -13,6 +13,7 @@ Our principles guide the way we work and interact with each other. They are base 5. [Deliver as fast as possible](#5-deliver-as-fast-as-possible) 6. [Respect for people](#6-respect-for-people) 7. [Optimise the whole](#7-optimise-the-whole) +8. [Separation of code vs processing](#8-separation-of-code-and-data) # Details @@ -147,3 +148,7 @@ We need to figure out how to deliver software as fast as possible. This reduces **Use feedback loops** to avoid negative global effects from local optimisations. **Balance autonomy and conformity.** Teams use the right tool for the job, within reason: unchecked proliferation of a wide variety of tools impacts the overall effectiveness of the organisation. + +## 8. Separation of code and data + +**Prevent accidentally committing data** Ideally processing of sensitive data should happen on a machine without permission to commit to the code repository. Alternatively, all data processing must occur outside of the code repository to prevent data files being accidentally committed to source control. Solutions should be architected such that data files are not moved into the source code. and .gitignore should be used to prevent log files from being committed to the repository.