Motivated by an article 7 Habits of Highly Effective Debuggers120 we would like to reflect on a distinction between diagnostics and problem solving as separate processes (although highly related). First, we reverse the precept from that article because stories such as software logs and traces are of primary importance to software diagnostics (and not only). And without diagnostics there is no effective debugging (treatment, problem solving, etc.).
The principle precept of diagnostics: stories not statistics secure certainty.