Insights
Technical & Industry Writing
Opinions and analysis on cloud architecture, platform engineering, migration strategy, AI in DevOps, and leading engineering teams.
You Don't Own a Kubernetes Platform Until You Own the Layer Beneath It
Running self-managed Talos Kubernetes on Nutanix, with no cloud provider under it, changed how I design platforms on managed clouds too. Here's what the layer beneath teaches you.
Idle Capacity Is the Most Expensive Thing on Your Platform
I built my first capacity tooling in 2015, bursting HPC jobs to the cloud when the on-prem queue backed up. A decade later, on much bigger fleets, the lesson is unchanged: idle capacity and queue wait are the same number seen from two sides, and both should be on the dashboard next to latency.
Give the Agent the Keyboard, Keep the Approval
I've rolled out AI tooling across a delivery team and I'm building an agentic workflow that drafts Terraform and opens pull requests. The rule that's held up: agents may author, humans must approve, and the review bar doesn't move.
Compliance Is a Design Input, Not a Review Gate
I've designed HIPAA-scoped platforms, led an ISO audit to completion, and run a security remediation programme on a trading platform. The pattern that holds: if compliance shows up as a review at the end, you've already lost the argument with the auditor.
Ten Years of Designing on Other People's Constraints
Consulting means you never get the greenfield you'd draw on a whiteboard. Fixed windows, shared databases, no managed control plane, a team that has to run it after you leave. I've come to think the constraint is the design.
Onboarding 100 Apps Onto One Pipeline Is a Governance Problem
The CI/CD part took weeks. Getting a hundred application teams to accept one standard, with image governance and deployment controls they couldn't opt out of, took the rest of the engagement. That's the actual work.
A Noisy Pager Gets Worse With an LLM on Top
AI-assisted incident response is arriving fast. It inherits whatever alert quality you already have. Fix the paging first, automate the deterministic responses second, and only then let a model near the triage.
Reliability You Can't Rehearse Isn't Reliability
Ten years, every migration I've led, zero unplanned downtime. The reason is boring: every risky change had a rollback we'd actually run, and a set of controls that made the safe path the easy path.
Cloud Abstraction Layers Fail When They Hide the Wrong Things
I've moved workloads between AliCloud, AWS, Azure, GCP, and bare metal. Every abstraction layer I've met made the same mistake: it hid the cloud primitives and exposed the workflow, when it should have done the opposite.
BYOC Is a Landing-Zone Problem Wearing a Product Hat
Bring-your-own-cloud deployments look like a product feature. Underneath, they're the same landing-zone discipline I've built for migrations for years: account structure, identity, network boundaries, and a Terraform model you can run in someone else's tenant.
The Operating Model Is the Product
I've built landing zones in weeks. The programmes that stalled afterwards didn't stall on the cloud. They stalled because no one had decided who owns what, who approves what, and where the evidence lives.
Zero Downtime Is a Constraint, Not a Goal
Most teams treat zero downtime as something to aim for. After leading migrations at 4.5M req/sec, I've come to see it differently — it's a design constraint that shapes every architectural decision from day one.
Cloud Migrations Are Org Problems First
I've led migrations at companies ranging from 50-person startups to platforms processing millions of requests per second. The technical challenges were rarely what threatened delivery. It was always something else.