Silence is not
the same as health.

Systems that run without anyone watching tend to fail quietly. I build them, work out how to tell when they have stopped, and write up what I find.

Scheduled agent · last 24 runsevery 15 min
did work ran, nothing to do did not run

Built

All projects →

Recent findings

All writing →

What I work on

Infrastructure and platform work

Cloud, networks, databases, deployment, the on-call rota. Twenty years of it, including the unglamorous parts: cost and capacity, and the migrations nobody wants to own.

AI agents in production

Scheduled jobs and AI agents that act without a person watching. Blast radius, recovery, and telling the difference between quiet and stopped.

LLM evals and cost control

How you find out a model output got worse after somebody else changed something, and what it costs per completed task rather than per token.

AI governance, written by the engineer

AI registers, DPIAs for live systems, EU AI Act Article 50 obligations. Most people in this market are lawyers who cannot read a config file. I work on both sides.

Who

Twenty yearsthe last few, mostly AI

Twenty years in infrastructure. Cloud, networks, databases, deployment, and being the person who gets called when it stops. Most of that has been keeping things running that other people depend on.

For the last few years a lot of it has been AI systems, mainly because those are the ones now running unattended. The problem underneath has not changed: knowing whether the thing is actually working, and finding out before somebody else does.

I write up what I find, usually because something looked fine and was not.

Get in touch

If something you depend on runs without anyone watching it, and you are not certain what would tell you it had stopped, that is the conversation I enjoy most.

hello@dmooney.engineer

Infrastructure, cloud and platform work as well as AI: what I can help with →

Reading