From c8955dcc0758721b6280a4a1b72fd826971adb54 Mon Sep 17 00:00:00 2001 From: Morgan Date: Sun, 24 Jan 2021 12:20:33 +0100 Subject: [PATCH] additional principles --- PRINCIPLES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/PRINCIPLES.md b/PRINCIPLES.md index 7429065..e065ace 100644 --- a/PRINCIPLES.md +++ b/PRINCIPLES.md @@ -252,4 +252,5 @@ See also [Calm programming / Slow programming](README.md#calm-programming--slow- * Quality first. If you’re doing CI and for some reason the integration fails, that means the broken build becomes the highest priority to fix before continuing to add more features. System quality—not just velocity—is important. CI works in three simple stages: push, test, and fix. But despite this simplicity, CI might become challenging if only a few members of the team practice it. Consequently, CI also requires a change in culture and support from management. [source](https://stackify.com/what-is-cicd-whats-important-and-how-to-get-it-right/) * Refactoring can only truly begin once you've actually learned what a piece of code or some data structure did, the unique properties for which they were written or chosen. Anything else is setting yourself up for failure. [source](https://ferd.ca/lessons-learned-while-working-on-large-scale-server-software.html) * It also means that when building systems, you should not assume that operators will do things correctly. Expect failure from people. Try to think about tools you can give them to undo their mistakes, because they will happen sooner or later. Have some dread. Be understanding. Know things won't be perfect. [source](https://ferd.ca/lessons-learned-while-working-on-large-scale-server-software.html) +* Study your tools, see how you work, understand how you can improve it. Don't rush. Before you run, you have to learn to walk.