Writing

Methods before slogans.

Notes about understanding software-intensive systems, preserving evidence, making technical judgment visible, and using automation without surrendering responsibility.

Professional practice

The first article captures a method developed through repeated encounters with unfamiliar, imperfectly documented software.

Software assurance

How I evaluate an unfamiliar software system

From artifact integrity and onboarding through representative execution, code analysis, risk-based review, and evidence-backed reporting.

Read the methodology →
Boundary

Public methods, private work

These articles describe reusable engineering approaches. They do not reproduce customer data, contractor findings, nonpublic technical baselines, or sensitive operational details.