Make failure legible
A system is only as operable as its worst 3am page. I would rather ship a boring architecture with excellent telemetry than a clever one nobody can debug under pressure.
DevOps Engineer | Cloud & Data Infrastructure. I spend most of my time on the systems between a commit and a user — build pipelines, runtime platforms, databases and the telemetry that tells you when any of it is unhappy.
Résumé available on request — use the contact form.
Approach
A system is only as operable as its worst 3am page. I would rather ship a boring architecture with excellent telemetry than a clever one nobody can debug under pressure.
The first time you do something, do it by hand and write down what happened. The second time, automate it. Automating from a guess produces tooling that encodes the guess.
Small, reversible steps beat one large migration. Most of my database and pipeline work is designed so any single step can be undone without a restore.
Skills
Things I have used seriously enough to have opinions about.
Timeline
Edit these entries in src/site.config.ts. Nothing here is auto-generated, and no employment history has been invented on your behalf.
ADD PERIOD
Replace this entry in src/site.config.ts with your own role, dates and a short description of the systems you were responsible for.
Placeholder entry #1 — replace it in src/site.config.ts
ADD PERIOD
A second editable slot. Delete any entries you do not need — the timeline renders whatever is in this array.
Placeholder entry #2 — replace it in src/site.config.ts
Résumé
No public résumé is linked at the moment. Send a note through the contact form and I will reply with a current copy. To publish one permanently, set resumeUrl in src/site.config.ts — the download buttons appear automatically once it has a value.