The Histories of Diagnostics, Observability, and Debugging
Description
Welcome to the Leanpub Launch video for The Histories of Diagnostics, Observability, and Debugging https://leanpub.com/histories by Dmitry Vostokov! 0:00 Dmitry introduces himself as a specialist in diagnostics, debugging, and observability 0:46 The 20-year journey of the memory dump analysis anthology reaching its 20th book 1:31 The origin of the book: a long-held dream to write a history of debugging 2:18 Using frontier LLMs to generate and verify historical content across disciplines 3:03 Expanding scope from software to hardware, electronics, medicine, and technical diagnostics 3:54 Adding sociology, humanities, social sciences, arts, security, economics, and management 4:47 Naming the book after Herodotus's Histories and the concept of multiple histories 5:34 Textual analysis and hermeneutics as a parallel to software debugging and version history 6:21 Defining observability: making systems transparent enough to find root causes 7:57 How the tools built for observability shape what can be observed, linking to semiotics About the Book A memory dump can preserve a damaged object after a program has stopped. Two copies of a manuscript can agree on a word because both preserve the same copying error. In each case, we work backwards from what survives. Which observations would help us distinguish one explanation from another? The Histories of Diagnostics, Observability, and Debugging brings together thirteen histories. We begin with software, hardware, medicine, machine learning and AI, and technical diagnostics. We then follow diagnostic practices through the natural, formal, social, and engineering sciences, the humanities, and the arts, before turning to writing and publishing and to management. Along the way, we consider which analysis patterns can travel between disciplines. Comparing two records, for example, requires us to ask how each was produced and whether their agreement provides independent evidence. The concluding chapter, When Diagnostic Evidence Changes Hands, follows a bridge inspector’s finding from a marked photograph to a field bulletin. A fine line identifying the joint for follow-up disappears during publication. Restoring the line corrects the bulletin. The joint still needs to be examined. What must travel with a diagnostic finding so that the next person can act on it? About the Author Dmitry Vostokov is an internationally recognized expert, speaker, educator, scientist, inventor, and author. He founded the pattern-oriented software diagnostics, forensics, and prognostics discipline (Systematic Software Diagnostics) and Software Diagnostics Institute. Vostokov has also authored over 50 books on software diagnostics, anomaly detection and analysis, software and memory forensics, root cause analysis and problem solving, memory dump analysis, debugging, software trace and log analysis, reverse engineering, and malware analysis. He has over 30 years of experience in software architecture, design, development, and maintenance in various industries, including leadership, technical, and people management roles. Dmitry founded OpenTask Iterative and Incremental Publishing and Software Diagnostics Technology and Services (former Memory Dump Analysis Services). In his spare time, he explores Software Narratology and Quantum Software Diagnostics. His interest areas are theoretical software diagnostics and its mathematical and computer science foundations, application of formal logic, semiotics, artificial intelligence, machine learning, and data mining to diagnostics and anomaly detection, software diagnostics engineering and diagnostics-driven development, diagnostics workflow and interaction. Recent interest areas also include functional programming, cloud native computing, monitoring, observability, visualization, security, automation, applications of category theory to software diagnostics, development and big data, and diagnostics of artificial intelligence. Follow the author here! https://x.com/DumpAnalysis Thank you for watching, please like and leave a comment, we'd love to hear from you! Please Subscribe and Follow! YouTube: https://www.youtube.com/leanpub X: https://x.com/leanpub Instagram: https://www.instagram.com/leanpub Facebook: https://www.facebook.com/leanpub Create Your Own Leanpub Book! You can create your own book anytime here: https://leanpub.com/create/book Here's the tutorial showing how to write and publish a Leanpub book in your browser (it's free!): https://help.leanpub.com/en/articles/2932527-getting-started-writing-a-book-in-leanpub-s-web-browser-writing-mode If you're a Leanpub author and you'd like to submit your own Launch video for us to publish, or if you'd like to record a Launch video with Len, please go here: https://leanpub.com/launch. #books #leanpublishing #selfpublishing #leanpub #writing #debugging #computinghistory #humanitieshistory #humanities #socialscience #engineering1 #businessandmanagement #writingandpublishing #finearts #softwareengineering #computerhardware #medicine #ai #machinelearning #softwarediagnostics #observability #debugging #rootcauseanalysis #memoryanalysis
