From 876b372f42ef94ad520920c4dab8e6f1b6514a37 Mon Sep 17 00:00:00 2001 From: az Date: Fri, 2 Jul 2021 15:17:46 +0200 Subject: [PATCH] separate results feedback page --- principles/ResultsFeedback.md | 8 ++++++++ principles/declarative-vs-imperative.md | 8 -------- 2 files changed, 8 insertions(+), 8 deletions(-) create mode 100644 principles/ResultsFeedback.md diff --git a/principles/ResultsFeedback.md b/principles/ResultsFeedback.md new file mode 100644 index 0000000..671286b --- /dev/null +++ b/principles/ResultsFeedback.md @@ -0,0 +1,8 @@ +# Clear execution and error feedback + +While we always hope for success, we all know too well that things can go wrong with software. +To be able to solve potential problems it is important to get clear information e.g. about the steps performed and even more important about where it might gone wrong and especially why. +Preferably potential solutions should be named. +So, while for successful executions it is nice to have, in case of errors it is essential to get a clear results overview. + +![](/resources/images/results-overview.png) \ No newline at end of file diff --git a/principles/declarative-vs-imperative.md b/principles/declarative-vs-imperative.md index 00d4269..757cdbe 100644 --- a/principles/declarative-vs-imperative.md +++ b/principles/declarative-vs-imperative.md @@ -44,11 +44,3 @@ as well as important advantages of the **declarative** paradigm, such as: * no need to check nor remember the system state. We call this "implarative". - -## Clear results overview - -With provisioning you hope everything goes fine but of course also errors can occur. -To be able to solve potential problems it is important to get clear information what are the steps performed and where did it go wrong and why. -So, while for successful executions it is nice to have, in case of errors it is essential to get a clear results overview. - -![](/resources/images/results-overview.png) \ No newline at end of file