Add debugging output as task

Signed-off-by: Matthias Beyer <mail@beyermatthias.de>

1 files changed, 14 insertions, 0 deletions

diff --git a/content/blog/2018-12-14-call-for-participation-3.md b/content/blog/2018-12-14-call-for-participation-3.md
index ad65797..9840444 100644
--- a/content/blog/2018-12-14-call-for-participation-3.md
+++ b/content/blog/2018-12-14-call-for-participation-3.md
@@ -27,6 +27,20 @@ Contributions (patches, questions, issues/bug reports) can be filed via the
 
 <hr>
 
+## Debugging output
+
+**Complexity: low, Effort: low**
+
+The imag codebase contains a lot of `debug!()` statements. But it is not enough.
+Sometimes even, the codebase has `debug!()` statements where it should have
+`trace!()` statements.
+
+The general rule is: Use `debug!()` for telling what is done, use `trace!()` for
+show details, variables, what exact functions are called, etc.
+
+There cannot be enough `trace!()` statements in the codebase!
+
+
 ## Replace is-match with matches
 
 **Complexity: low, Effort: low**