Boundaries
I set ownership before implementation and keep dependencies pointing in one direction. Shared capabilities stay behind explicit contracts, so teams can use them without inheriting the systems or decisions that produce them.
Platforms that stay useful as they grow.
I’m a senior platform engineer in Sydney. I build cloud platforms that let teams work independently while ownership stays clear and security, cost and operational state remain under control.
Enablement
I build supported paths teams can use without waiting on the platform team. Routine work inherits security controls and operational signals instead of assembling them again.
Defaults
I start with managed services and proven primitives, then standardise the parts teams would otherwise rebuild. Custom tooling begins only when a named constraint justifies the extra cost and long-term ownership.
Operations
I keep operating state visible: who owns the system, what it publishes, which controls are active and where it is failing. Recorded state lets the next engineer operate or recover it without reconstructing the platform from memory.
Selected writing
Making IaC boring
A five-part series on re-cutting a live IaC platform around ownership, typed contracts and pre-apply checks.
Read the series