The Importance of Being Technical

CARE: Crash Analysis Report Environment

DATA (Dump Analysis + Trace Analysis) Facebook group
Please join the community of memory (dump) and trace analysis engineers. This group promotes scientific methods and memory dump-based worldview.

Twitter @ DumpAnalysis
You can now follow portal and blog news at DumpAnalysis on Twitter

LinkedIn Group Dr. Watson Enthusiasts
All about Dr. Watson errors and more. Get news, excerpts and progress reports about the forthcoming book The Science of Dr. Watson: An Illustrated History of Debugging (ISBN 978-1906717070)

2010 (0x7DA) - The Year of Dump Analysis
2011 (0x7DB) - 2020 (0x7E4) The Debugging Decade

To paraphrase ”The Importance of Being Earnest“ I have made a Euclidean rigid motion on a plane by coming back from management line back to engineering line: my new title at Citrix Systems is Principal Dev Analysis Engineer. In the past before embarking on a blogger’s and writer’s career I wanted to become a Manager (and eventually became the one after being a Team Lead) and even had plans to enroll into one of business schools to get an MBA but now engineering path seems more natural to me at these times.

- Dmitry Vostokov @ DumpAnalysis.org -

           

Announcements

Coming Soon:

Debugging Notebook: Essential Concepts, WinDbg Commands and Tools

Crash Dump Analysis for System Administrators and Support Engineers

New Magazines:

Debugged! MZ/PE: MagaZine for/from Practicing Engineers


New Books:

Memory Dump Analysis Anthology, Volume 3

First Fault Software Problem Solving: A Guide for Engineers, Managers and Users

x64 Windows Debugging: Practical Foundations

Also available:

Windows Debugging: Practical Foundations

DLL List Landscape: The Art from Computer Memory Space

Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov

WinDbg: A Reference Poster and Learning Cards

Memory Dump Analysis Anthology, Volume 2

Memory Dump Analysis Anthology, Volume 1

New Children's Book:

Baby Turing

6 Responses to “The Importance of Being Technical”

  1. SR Says:

    Hi,
    What made you not to go to business school ?:) I am also working in technical side for a decade and i was thinking of joining business school. Now after reading your blog post i am demotivated :)
    -SR

  2. Dmitry Vostokov Says:

    If you are interested in internals of what made me not to go to business school you should wait for:

    Crash Dump: A Software Engineering Autobiography (ISBN: 978-1906717193)

    Planned for 2015 but could be earlier or later, depends on the course of history :-)

    Thanks,
    Dmitry

  3. Marc Sherman Says:

    Hello,

    What is the role of “Dev Analysis Engineer”?

    thanks,
    Marc

  4. Dmitry Vostokov Says:

    Main responsibility is to analyze memory dumps and traces from customer environments and provide recommendations. We also sometimes design and write support tools if we feel an nostalgic urge to do some coding or help support and escalation engineers to get right kind of data for our analysis. Ideally this is a role for a software engineer with low-level programming skills who doesn’t want to code full time anymore and wants to analyze and sometimes read code.

  5. Management Bits and Tips » Blog Archive » Flattening My Management Says:

    […] The Importance of Being Technical […]

  6. Crash Dump Analysis » Blog Archive » Trace Analysis Patterns (Part 1) Says:

    […] back to engineering I decided to expand the domain of my research and start the new series of posts called Trace […]

Leave a Reply