Making agentic AI reliable in production.

Platform & SRE engineer. Nine years shipping cloud-native platforms across banking, defense, healthcare and blockchain — now building the infrastructure behind production AI.

More about me →
  1. Exit 0 Is Not Success for an Agent Job

    OpenAI's agent hacked Hugging Face, ran for days, and went unnoticed for a week. For anyone running scheduled agents the lesson is duller than the security story: a run where half the sources failed exits 0, writes a file the same size, and looks identical to a good one. Two cheap fixes from a cron job I actually run: make the agent report its own coverage in the artifact a human already reads, then let deterministic code decide whether it ships.

    Systems
    Read
  2. Capacity Planning for Agents: Measure Yield, Not Tokens

    Goldman says 24x token growth by 2030. Others say 240x once you count parallel agents. Both are demand forecasts you can't spend against. Take a curation pipeline that reports keeping 12 items from 37 swept: follow the funnel to the end and 641 candidates become 202 published items, 5 things worth acting on, and 3 anyone actually did. The metric that matters is cost per accepted change, and it sits on the wrong side of every agent's telemetry boundary.

    Systems
    Read
  3. Agent Memory Wants a Wiki, Not a Vector Store

    LangChain is reframing agent memory as a hyperlinked wiki, and a logging study found Claude Code ships ~33k tokens of overhead before your prompt even arrives. I've been running memory as a citation-linked markdown wiki for months, no embeddings anywhere in the pipeline. Here's what the setup looks like and where it beats top-k retrieval.

    Systems
    Read
  4. Agent Sprawl Is an Identity Problem, Not a Dashboard Problem

    Google's second State of AI Infrastructure report says 83% of orgs need to upgrade their infrastructure for agents. The number that actually matters is that nobody can see what their agents can touch — and a governance dashboard sitting on top of a wide-open credential is decoration. The fix is scoping, not monitoring.

    Systems
    Read
  5. The Sandbox Problem for AI Agents: Lambda MicroVMs and Where Untrusted Code Should Run

    An agent writes code you never reviewed and then runs it. The interesting question isn't the prompt — it's the blast radius. Lambda MicroVMs give each session a Firecracker VM that resumes from a snapshot in under a second, including a pattern where Anthropic runs the agent loop and you run the tool calls.

    Systems
    Read
  6. Choosing an AI Agent Pattern: A Decision Guide for Enterprise Teams

    Most teams reach for multi-agent orchestration too early. Here's how to pick the simplest pattern that does the job — from a single direct model call up to a manager-and-workers system.

    Systems
    Read
All projects →

2022

  • Polyglot Microservices Webshop

    A cloud-native webshop on Kubernetes — independent services in Swift, TypeScript, Java, Go and Python behind a single API gateway, fronted by an iOS storefront.

2021

  • API Gateways

    Companion code to the maintainability write-up — a worked API-gateway example that fronts backend services and offloads cross-cutting concerns.

2019

  • Kubernetes CI/CD Webhook

    A Kubernetes webhook consumer for CI/CD — a Helm chart that fires pipeline jobs to build images with Uber's Makisu and continuously deploy GitHub/GitLab projects via Helm.

2018

  • Heart Disease Prediction

    An ML model predicting heart disease on the UCI dataset — wrangling four cardiology sources into a binary classification, then comparing logistic regression and SVM at ~85% cross-validated accuracy.