Every Field Note on this site is signed Captain O. That is what people call me, so it is the name I answer to here. This page is who that is, and what the name is worth.
I did not come from computer science. I came from the cockpit. I trained as a helicopter pilot, and somewhere in that training I decided the runway I actually wanted was in the cloud. I taught myself, I broke in, and I never looked back. Nine years in enterprise IT later, six of them entirely on Azure, I work as a Senior Azure Cloud & DevSecOps engineer and as a Cloud InfoSec Program Manager.
The checklist habit comes from flying. A pilot does not trust memory before take-off; a pilot reads the card. That is the discipline I bring to the classes and to the notes: a claim is either checked against the source or it is not on the page.
It means I set the brief, I decided what the piece had to get right, and I checked what it says against Microsoft Learn and against what I have run myself. Where a note draws on my own incidents, migrations and mistakes, it says so. Where it is teaching a service I would not run in production without checking a limit first, it names the limit and the page that states it. If a note is wrong, that is mine to fix, and the changelog on this site is public.
The notes lean toward the things I actually do: Azure identity and governance, tenant-to-tenant migrations, infrastructure as code, pipelines, and the security posture around all of it. They lean away from head terms Microsoft documents better than anyone can, because pretending otherwise is a waste of your time.
The forty-two classes of the CAMPUX Cloud Engineering Bootcamp, reverse-engineered from real job postings rather than an exam outline. The public labs library, fourteen labs with the CLI and the infrastructure-as-code side by side, open on GitHub. A deployable retail capstone that runs the same container on App Service and on AKS. And Keel, a secure Azure infrastructure-as-code framework, which lives on its own now.
Professional history is on LinkedIn, code is on GitHub, and the consultancy side of the work is at victor.thomsup.com. Learners write to me through the community board; that is the fastest way to get a correction in front of me.