Method
How I work.
My approach to investigating technical problems.
-
Document
Leave the next engineer with a better system than the one I inherited.
The methods
Written down, with proof.
The recurring approaches behind the case studies, each backed by at least one documented example.
-
How I communicate during incidents
Send the holding message before you know the cause, scope claims to what monitoring can actually support, and hand engineering a diagnosis instead of a mystery.
-
How I run a root-cause analysis
Separate the trigger from the cause, demand a mechanism rather than a correlation, and fix the class of failure, not just the instance that got caught.
-
How I troubleshoot
Characterize the failure before touching anything, build a known-good baseline, and eliminate hypotheses by comparison. This is the method behind the investigations on this site.
-
How I work with AI
AI generates the scaffolding. Deciding what correct looks like, and checking that the output meets it, stays human. An AI assistant is only as trustworthy as the content and guardrails underneath it.
Working principles
What colleagues can expect.
The technical process matters, but so does how the work is carried through with customers, engineering, and leadership.
-
Ownership
I stay with an issue from the initial signal through investigation, communication, resolution, and documentation rather than handing off ambiguity. The escalation investigation →
-
Reliability
I communicate commitments clearly, arrive prepared, respect timelines, and close loops so others are not left guessing. The migration continuity record →
-
Constructive candour
I raise risks early, give direct feedback professionally, and challenge weak assumptions without making collaboration adversarial.
-
Adaptability
I learn unfamiliar systems quickly, adjust to changing priorities, and remain useful when the original plan stops matching reality. The career timeline →
-
Investigation depth
I reproduce problems, compare known-good and failed cases, eliminate hypotheses, and avoid stopping at the first plausible explanation.
-
Professional collaboration
I communicate calmly and respectfully across customers, support, engineering, operations, and leadership, especially when the situation is uncertain.