More Related Content Similar to Philosophy of Software Diagnostics (20) More from Dmitry Vostokov (20) Philosophy of Software Diagnostics2. If want to be the best software diagnostician you
need to be a philosopher.
After Galen’s thoughts on medicine
© 2013 Software Diagnostics Services
3. Prerequisites
Interest in software diagnostics,
troubleshooting and debugging
Philosophical attitude and interest in
meta-questions
© 2013 Software Diagnostics Services
5. Software Diagnostics
A discipline studying abnormal
software structure and behavior in
software execution artifacts (such
as memory dumps, software and
network traces and logs) using
pattern-oriented analysis
methodologies.
© 2013 Software Diagnostics Services
6. Diagnostics Pattern
A common recurrent identifiable
problem together with a set of
recommendations and possible
solutions to apply in a specific
context.
© 2013 Software Diagnostics Services
8. Problem
Difficulty – problem 1641 business 1843 (colloq.)
core c1460-1652 prob 1934 (colloq.) hang-up
1959 (slang) problem 1874 sub-problem 1907
pseudo-problem 1911
Mathematics – prob 1864
Materials of topic of debate / discussion –
problem 1529 – 1646 (question, thesis, argument,
issue, consultation, debating point)
Enquiry, questioning – problem 1594 good
question 1918
© 2013 Software Diagnostics Services
9. Prob-lem(ma)
A prob-lemma is a pair:
An issue
~Understanding of an issue
Проблема (Problema, in Russian)
© 2013 Software Diagnostics Services
13. Da-sign
A pattern in the artefact for an issue that
has a concern for us
Understanding of an issue and a pattern
© 2013 Software Diagnostics Services
14. CARE
Da-sign as a meaning-pattern
Underlying meaning-structure for da-
signs
© 2013 Software Diagnostics Services
15. Hermeneutics
© 2013 Software Diagnostics Services
Software User
Interaction
Software
Artefacts
Software
Diagnostician
Understanding
Understanding
16. Remote Interaction
© 2013 Software Diagnostics Services
Software
User
Software
Diagnostician
Support Support
Software
Diagnostician
19. Sources of Interpretation
© 2013 Software Diagnostics Services
Problem descriptions
Human-software interaction
Interaction itself
Artefacts
21. Why Phenomenology?
© 2013 Software Diagnostics Services
Involves human side
About meaning and understanding
Includes feeling and mood
The best of Husserl and Heidegger
22. Patterns as Phenomena
© 2013 Software Diagnostics Services
Meaning-structures in meaningful
world of experience
Common meaning-structure
Leaving Human-Software dichotomy
outside: patterns of phenomena
23. Software Phenomenology
© 2013 Software Diagnostics Services
Only experience
Bracketing implementation [code]
“Free fantasy variation” (Husserl)
Free fantasy investigation
(software narratology)
Pattern discourse
Common meaning-structure in
Computer-world
24. Hermeneutics
Meeting and dialog narratives
Software problem narratives
Software execution narratives
Software trace and log patterns
© 2013 Software Diagnostics Services
31. Further Reading
Philosophy
“Martin Heidegger: The Possibility of A Russian Philosophy” by A. Dugin
(in Russian language)
“Introduction to Metaphysics” by Martin Heidegger
“Being and Time” by Martin Heidegger (blue book)
“Heidegger: A Guide for the Perplexed” by David Cerbone
“The Hermeneutics of Medicine and the Phenomenology of Health: Steps Towards
a Philosophy of Medical Practice” by Fredrik Svenaeus
Pattern-Oriented Software Diagnostics
Software Diagnostics Institute
Memory Dump Analysis Anthology: Volumes 1, 2, 3, 4, 5, 6, 7, 8, …
Volume 7 is in preparation (May-June, 2013)
Introduction to Pattern-Driven Software Diagnostics
Introduction to Systemic Software Diagnostics
Introduction to Pattern-Based Software Diagnostics
Introduction to Software Narratology
© 2013 Software Diagnostics Services
33. Q&A
Please send your feedback using the contact
form on DumpAnalysis.com
© 2013 Software Diagnostics Services
34. Thank you for attendance!
© 2013 Software Diagnostics Services