About

Who I am

Ten-plus years running cloud infrastructure for companies where downtime costs real money: media, healthtech, nationwide logistics. The actual job is Kubernetes, cloud architecture, DevOps pipelines, identity, and the security controls that have to hold even when everything else is on fire.

I co-founded Temika Cyber, a cyber security consultancy, and spend most of my time there on infrastructure and security. Increasingly that means the non-human side of the stack: the AI agents, service accounts, and machine identities that now outnumber people and mostly answer to no one. I have also spent more time than I expected building engineering teams, which turns out to be a different skill set entirely.

What this site is

Three things here: a short list of what I have built, a contact page, and the writing. The writing is where I put the explanations I had to figure out myself.

When a new CVE drops, a tool ships with a security gap nobody has documented yet, or AI infrastructure starts creating attack surfaces the vendor hasn't named, I try to write the piece I wanted to find. Security, infrastructure, AI systems: how they break, and how to build them so they don't.

On the writing

Everything here is published under my name. I link to primary sources so you can verify the claims yourself: vendor advisories, CVE records, specs, official docs. When I get something wrong, I correct it and say so. How the writing is produced and checked is on the Editorial Standards page.

Get in touch

Email at [email protected] or LinkedIn. If something here was useful, or wrong, I'd like to hear about it.