separate results feedback page
This commit is contained in:
parent
764c8ef976
commit
876b372f42
2 changed files with 8 additions and 8 deletions
8
principles/ResultsFeedback.md
Normal file
8
principles/ResultsFeedback.md
Normal file
|
@ -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)
|
|
@ -44,11 +44,3 @@ as well as important advantages of the **declarative** paradigm, such as:
|
||||||
* no need to check nor remember the system state.
|
* no need to check nor remember the system state.
|
||||||
|
|
||||||
We call this "implarative".
|
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)
|
|
Loading…
Reference in a new issue